Visma e-conomic OpenAPI

Name: Visma e-conomic OpenAPI API
Brand: Visma e-conomic OpenAPI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey98 EndpointsREST

For Agents

Read and write activities, employees, mileage entries, project activities, and project customers in a Visma e-conomic agreement so apps can sync expenses, time, and costing data into the books.

Connect the Visma e-conomic OpenAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Visma e-conomic OpenAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Visma e-conomic OpenAPI API.

List, retrieve, create, and update activities used to categorise project work

Query allowed activities for a context and count or page through activities

Retrieve cost types and cost type groups for use on time and expense entries

Manage employees and employee groups, including create, update, delete, count, and paged list

GET STARTED

Start building with Visma e-conomic OpenAPI API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Visma e-conomic OpenAPI, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the Visma e-conomic OpenAPI, keeping it validated and agent-ready. Visma e-conomic is a Nordic cloud accounting platform whose v20 REST API exposes activities, activity groups, cost types, employees and employee groups, mileage entries and prices, project activities, and project customers. Built for ISVs integrating expense, project costing, and time-tracking flows into e-conomic books, the API is paginated by /paged endpoints and authenticated with a per-agreement grant token plus an app secret token.

Use Cases

Patterns agents use Visma e-conomic OpenAPI API for, with concrete tasks.

★ Mileage Expense Sync from a Mobile App

A field-services mobile app captures driver trips and posts them to e-conomic via POST /mileages with the employee number, date, and distance. Once a manager reviews the batch, POST /mileages/approve marks them approved so the postings flow into the agreement's books without manual re-entry.

POST /mileages with employee number, distance, and date for each captured trip, then POST /mileages/approve with the list of mileage IDs

Employee Master Data Sync from HR

An HR system pushes new hires and group changes into e-conomic via POST /employees and PUT /employees, and uses /employeegroups to keep the group taxonomy aligned. /employees/paged gives the HR sync job a stable cursor for the reverse direction so pulled records can reconcile against the source.

POST /employees with the new hire's number, name, and employee group, then GET /employees/paged on the next sync to verify the record exists

Project Cost Tracking

A project management app creates project activities via POST /project-activities and reads project customers via /project-customers/paged so timesheets in the source app map onto e-conomic's project structure. Activity groups and cost types pulled from /activitygroups and /costtypes drive the dropdowns the user sees when classifying time entries.

GET /activitygroups and /costtypes to build the classification list, then POST /project-activities to register new billable activities for a project

Agent-Driven Bookkeeping via Jentic

An AI assistant for a Nordic SMB asks Jentic to 'create a mileage entry in e-conomic' and gets the POST /mileages operation. It supplies the driver's employee number and distance, and the entry lands in the agreement's books - the agreement grant token and app secret token never enter the agent context.

Use Jentic to search 'create a mileage entry in e-conomic', load the POST /mileages operation, and execute it with the employee number and trip distance

Key Endpoints

98 endpoints — jentic publishes the only available openapi specification for the visma e-conomic openapi, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/mileages

Create a single mileage entry

POST

/mileages/approve

Approve a list of mileage entries

POST

/employees

Create an employee

POST

/employeegroups

Create an employee group

POST

/project-activities

Create a project activity

GET

/activities/allowed

Retrieve allowed activities

GET

/employees/paged

Retrieve a page of employees

GET

/project-customers/paged

Retrieve a page of project customers

POST

/mileages

Create a single mileage entry

POST

/mileages/approve

Approve a list of mileage entries

POST

/employees

Create an employee

POST

/employeegroups

Create an employee group

POST

/project-activities

Create a project activity

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The X-AppSecretToken and X-AgreementGrantToken are stored encrypted in the Jentic vault. Agents receive a scoped execution token; both raw tokens never appear in agent context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a mileage entry' or 'list project customers') and Jentic returns the matching e-conomic operation with its input schema and pagination shape.

Time to first call

Direct integration: 3-5 days to wire up dual-token auth, paged retrieval for 9 resource types, and approval flows. Through Jentic: under 1 hour - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Dynosend API

Email customers transactional invoice or receipt notifications driven by e-conomic events

Pick Dynosend to send the email side-effect once an entry is posted in e-conomic

Complementary

dYdX Indexer API

Bring trading PnL data alongside e-conomic accounting for crypto-trading businesses

Use dYdX to source realised trading PnL, then post into e-conomic via mileage/activity-style entries

Complementary

E-goi Marketing API

Multi-channel marketing campaigns pointed at customer segments synced from e-conomic project customers

Use E-goi when the customer list pulled from e-conomic needs to drive email or SMS marketing campaigns

FAQs

Specific to using Visma e-conomic OpenAPI API through Jentic.

Why is there no official OpenAPI spec for the Visma e-conomic API?

Visma e-conomic does not publish an OpenAPI specification covering this v20 surface. Jentic generates and maintains this spec so that AI agents and developers can call the Visma e-conomic OpenAPI via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Visma e-conomic OpenAPI use?

Every request requires two API keys passed as headers: 'X-AppSecretToken' identifies the integration and 'X-AgreementGrantToken' identifies the e-conomic agreement (tenant) the call acts on. Through Jentic, both are stored encrypted in the vault and injected per-call rather than handed to the agent.

Can I create mileage entries with the Visma e-conomic API?

Yes. POST /mileages creates a mileage entry, PUT /mileages updates one, DELETE /mileages/{number} removes it, and POST /mileages/approve marks a batch approved. Pricing for the entries is read from /mileageprices and /mileageprices/{number}.

What are the rate limits for the Visma e-conomic OpenAPI?

The OpenAPI spec does not declare numeric rate limits. Visma e-conomic applies tenant-level fair-use throttling - high-volume integrations should use the /paged endpoints (e.g. /employees/paged, /mileages/paged) rather than repeatedly calling the unpaged list.

How do I post a mileage entry through Jentic?

Run pip install jentic, search for 'create a mileage entry in e-conomic', load the operation for POST /mileages, then execute it with the employee number, date, and distance. Jentic injects both the X-AppSecretToken and X-AgreementGrantToken headers automatically.

Can I page through employees instead of pulling them all at once?

Yes. GET /employees/paged returns a page-based response and GET /employees/count returns the total count, so a sync job can iterate pages rather than fetching the unpaged /employees list. The same paged + count pattern applies to mileages, activities, project activities, and project customers.