How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Visma Expense Claim API

The ExpenseClaim API from Visma — 5 operation(s) for expenseclaim.

Visma Expense Claim API is one of 193 APIs that Visma publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include ExpenseClaim. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, rate-limit docs, and a support channel.

This API exposes 8 operations across 5 paths, and defines 48 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.finance.visma.net.

8 operations 5 paths 48 schemas 1 DELETE2 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.finance.visma.net
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Visma Expense Claim API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (interactiveapi) using the authorizationCode flow, exposing 5 scopes.

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 1 DELETE, 2 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

ExpenseClaim 8
GET
/v1/expenseClaim/{expenseClaimNbr}
Get a specific Expense Claim
ExpenseClaim_GetExpenseClaimByexpenseClaimNbr 2 params → 200202
PUT
/v1/expenseClaim/{expenseClaimNbr}
Update a specific ExpenseClaim
ExpenseClaim_PutByexpenseClaimNbr 3 params body → 204412202
DELETE
/v1/expenseClaim/{expenseClaimNbr}
Deletes a specific ExpenseClaim
ExpenseClaim_DeleteByexpenseClaimNbr 2 params → 204202
GET
/v1/expenseClaim
Get a range of Expense Claims, a filter needs to be specified.
ExpenseClaim_GetAll 13 params → 200202
POST
/v1/expenseClaim
Create an ExpenseClaim
ExpenseClaim_CreateExpenseClaim 1 param body → 201202
POST
/v1/expenseClaim/{expenseClaim}/action/hold
Put ExpenseClaim on hold
ExpenseClaim_PutExpenseClaimOnHoldByexpenseClaim 3 params → 200412202
POST
/v1/expenseClaim/{expenseClaim}/action/submit
Submit Expense Claim operation
ExpenseClaim_SubmitExpenseClaimByexpenseClaim 3 params → 200412202
POST
/v1/expenseClaim/{expenseClaim}/action/approval
Send Expense Claim to approval
ExpenseClaim_SendExpenseClaimToApprovalByexpenseClaim 3 params → 200412202

Schemas 48

The contract defines 48 schemas that model the data the API accepts and returns. The most detailed are ExpenseClaimDetailDto (30 properties), ExpenseClaimDto (20 properties), ExpenseClaimDetailUpdateDto (19 properties), ExpenseClaimUpdateDto (7 properties). Each schema is shown below with its type and property counts.

refNbrInExpenseClaimDetailUpdateDto
object
The identifier of the transaction.
1 property
projectInExpenseClaimDetailUpdateDto
object
The project or customer contract associated with the expense claim, if the work performed was for a project or contract. Project Task The task associated with…
1 property
customerInExpenseClaimDetailDto
object
Customer The identifier of the customer associated with the expense.
2 properties
invoiceableInExpenseClaimDetailUpdateDto
object
The currency of the expense receipt. However, if you enter a claim line directly, the currency value is read-only and matching the claim currency.
1 property
claimedByInExpenseClaimDto
object
Mandatory field: The top part Claimed by The employee who is claiming the expenses. If the claim is released, an Accounts Payable bill will be generated to thi…
3 properties
expenseAccountInExpenseClaimDetailDto
object
Mandatory field: Expense account The expense account to which the system should record the part of the expense to be paid back to the employee.
6 properties
employeePartInExpenseClaimDetailUpdateDto
object
The part of the total amount that will not be paid back to the employee. The percentage depends on the company policy.
1 property
AttachmentDto
object
3 properties
ExpenseClaimDetailUpdateDto
object
19 properties
locationInExpenseClaimDto
object
The top part Location The company location associated with the claim.
2 properties
unitCostInExpenseClaimDetailUpdateDto
object
The cost of a unit of the item.
1 property
expenseItemInExpenseClaimDetailUpdateDto
object
The expense identifier, if an expense of this type is listed as an inventory nonstock item.
1 property
locationInExpenseClaimDetailUpdateDto
object
The identifier of the customer location associated with the expense.
1 property
ExpenseClaimDetailDto
object
30 properties
uomInExpenseClaimDetailUpdateDto
object
The unit of measure in which the quantity is shown.
1 property
salesAccountInExpenseClaimDetailDto
object
Sales account The sales account to which the system should record the part of the amount to charge the customer for. This is applicable only when a customer ha…
6 properties
expenseItemInExpenseClaimDetailDto
object
Mandatory field: Expense item The expense identifier, if an expense of this type is listed as an inventory nonstock item.
2 properties
projectTaskInExpenseClaimDetailUpdateDto
object
The task associated with the contract or project.
1 property
ExpenseClaimDto
object
This class represents a Expense Claim in ExpenseClaimController. Used for getting data.
20 properties
claimDetailIdInExpenseClaimDetailUpdateDto
object
Identifies the expense claim detail line to update
1 property
branchInExpenseClaimDetailUpdateDto
object
The branch that will reimburse the expenses to the employee.
1 property
SegmentUpdateDto
object
2 properties
descriptionInExpenseClaimDetailUpdateDto
object
A description of the transaction.
1 property
taxCategoryInExpenseClaimDetailDto
object
VAT category The VAT category associated with the expense item.
2 properties
locationInExpenseClaimDetailDto
object
Location The identifier of the customer location associated with the expense.
2 properties
dateInExpenseClaimDetailUpdateDto
object
The date when the expense was incurred.
1 property
ExpenseClaimUpdateDto
object
7 properties
expenseAccountInExpenseClaimDetailUpdateDto
object
The expense account to which the system should record the part of the expense to be paid back to the employee.
1 property
dateInExpenseClaimUpdateDto
object
The date when the claim was entered.
1 property
customerInExpenseClaimDetailUpdateDto
object
The identifier of the customer associated with the expense.
1 property
SendExpenseClaimToApprovalActionResultDto
object
3 properties
BackgroundApiAcceptedDto
object
2 properties
locationInExpenseClaimUpdateDto
object
The company location associated with the claim.
1 property
projectInExpenseClaimDetailDto
object
Mandatory field: Project The project or customer contract associated with the expense claim, if the work performed was for a project or contract. Project Task…
3 properties
departmentInExpenseClaimDto
object
Mandatory field: The top part Department ID The department associated with the expense claim.
2 properties
taxCategoryInExpenseClaimDetailUpdateDto
object
The tax category associated with the expense item.
1 property
SubmitExpenseClaimActionResultDto
object
3 properties
descriptionInExpenseClaimUpdateDto
object
A description of the claim.
1 property
MetadataDto
object
2 properties
PutExpenseClaimOnHoldActionResultDto
object
3 properties
customerInExpenseClaimDto
object
The top part Customer The applicable customer.
2 properties
salesSubaccountInExpenseClaimDetailDto
object
Sales sub. The corresponding subaccount the system uses to record the amount to charge the customer for. This is applicable only when a customer has been speci…
3 properties
expenseSubaccountInExpenseClaimDetailDto
object
MAndatory field: Expense sub. The corresponding subaccount the system uses to record the part of the expense to be paid back to the employee.
3 properties
branchInExpenseClaimDetailDto
object
Mandatory field: Branch The branch that will reimburse the expenses to the employee.
2 properties
claimedByInExpenseClaimUpdateDto
object
The employee who is claiming the expenses. If the claim is released, an Accounts Payable bill will be generated to this employee.
1 property
projectTaskInExpenseClaimDetailDto
object
Project task The task associated with the contract or project.
3 properties
quantityInExpenseClaimDetailUpdateDto
object
The quantity of this expense item.
1 property
customerInExpenseClaimUpdateDto
object
The applicable customer.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

visma-expenseclaim-api-openapi.yml Raw ↑

Other APIs Visma publishes across the network.

Visma Business NXT GraphQL API
Visma Account API
Visma Accounts API
Visma Agreements API
Visma Allocation Periods API
Visma Approval API
Visma App Store Activation Status API
Visma Article Account Codings API
Visma Article Labels API
Visma Articles API
Visma Attachment API
Visma Attachment Links API
Where this information came from

This is an independent, third-party profile of Visma Expense Claim API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.