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 Journal Transaction V2 API

The JournalTransactionV2 API from Visma — 5 operation(s) for journaltransactionv2.

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

Tagged areas include JournalTransactionV2. 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 7 operations across 5 paths, and defines 21 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.

7 operations 5 paths 21 schemas 2 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 Journal Transaction V2 API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (interactiveapi) using the authorizationCode flow, exposing 5 scopes.

Paths & Operations 7

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

JournalTransactionV2 7
GET
/v2/journaltransaction/{journalTransactionNumber}
Get a specific Journal Transaction
JournalTransactionV2_GetSpecificJournalTransactionsByjournalTransactionNumber 2 params → 200202
PUT
/v2/journaltransaction/{journalTransactionNumber}
Update a Journal Transaction
JournalTransactionV2_PutByjournalTransactionNumber 3 params body → 204412202
GET
/v2/journaltransaction
Get a range of Journal Transactions - ScreenId=GL301000.
JournalTransactionV2_GetAllJournalTransactions 9 params → 200202
POST
/v2/journaltransaction
Create a Journal Transaction
JournalTransactionV2_Post 1 param body → 201202
POST
/v2/journaltransaction/{journalTransactionNumber}/action/release
Release journal transaction operation
JournalTransactionV2_ReleaseJournalTransactionByjournalTransactionNumber 3 params → 412202
POST
/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment
Creates an attachment and associates it with an journalTransaction.
JournalTransactionV2_AddHeaderAttachmentBymodulejournalTransactionNumber 3 params → 201202
POST
/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber}/attachment
Creates an attachment and associates it with a certain journalTransaction line.
JournalTransactionV2_AddLineAttachmentBymodulejournalTransactionNumberlineNumber 4 params → 201202

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are JournalTransactionDto (32 properties), JournalTransactionLineDto (23 properties), JournalTransactionUpdateDto (17 properties), JournalTransactionLineUpdateDto (16 properties). Each schema is shown below with its type and property counts.

JournalTransactionUpdateDto
object
This class represents a journal transaction in JournalTransactionController. Used for creating/updating data.
17 properties
projectTaskInJournalTransactionLineDto
object
The table Project task The particular task of the project with which this batch is associated.
3 properties
projectInJournalTransactionLineDto
object
The table Project The project with which this batch is associated, or the code indicating that this batch is not associated with any project.
3 properties
JournalTransactionDto
object
This class represents a journal transaction in JournalTransactionController. Used by getting data.
32 properties
AttachmentDto
object
3 properties
DtoValueOfString
object
1 property
vatCodeInJournalTransactionLineDto
object
The table VAT code The VAT code based on which the taxable amount is calculated.
2 properties
SegmentUpdateDto
object
2 properties
postPeriodInJournalTransactionUpdateDto
object
The financial period to which the transactions recorded in the document should be posted. Use the format MMYYYY.
1 property
JournalTransactionLineUpdateDto
object
16 properties
DtoValueOfDecimal
object
1 property
BackgroundApiAcceptedDto
object
2 properties
SegmentDto
object
4 properties
subaccountInJournalTransactionLineDto
object
Mandatory field: The table Subaccount The subaccount used with the account to detail a journal entry.
9 properties
JournalTransactionLineDto
object
23 properties
DtoValueOfDateTime
object
1 property
DtoValueOfInt32
object
1 property
MetadataDto
object
2 properties
vatInJournalTransactionLineDto
object
The table VAT ID The VAT used to calculate the VAT amount.
2 properties
DtoValueOfBoolean
object
1 property
financialPeriodInJournalTransactionUpdateDto
object
The financial period to which the transactions recorded in the document should be posted. Use the format YYYYMM.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

visma-journaltransactionv2-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 Journal Transaction V2 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.