Get an existing journal.
Description
This endpoint retrieves existing journals from the financial accounting administration by utilizing the journal code. The journal codes are standard available in the Bloxs application and get be configured to some extend. A journal is an umbrella for multiple journal posts.
If the user does not know the correct journal code, the filter can be used to retrieve all available codes.
Use Case
The user wants to retrieve a specific journal in order to display to which ledger account it is related.
Request fields
The request contains the following fields:
| Field | Description |
|---|---|
| code | Journal code. In some cases, it can be entered manually. |
Response fields
The 200 response contains the fields in the table below. For the GET operation it gives a up-to-date insight in the data that is currently registered in Bloxs.
| Field | Description |
|---|---|
| code | Code for the compaction. |
| name | Name of the compaction. |
| ledgerAccountCode | Ledger account code. |
| specificForOwnerReference | If the general ledger account is restricted to a single user within Bloxs, the reference of that relation is entered here. It can contain only one reference or remain empty. This is the same value as 'specificForOwnerReference' in the ledger account if they are linked. |
| lastModified | Timestamp of the last modification within Bloxs (determined by Bloxs). |
Please enter a valid token
The internal identifier of the model (i.e. Reference, Code, Name, depends on model).
OK
The requested journal was not found.