Get journals filtered and paged

Prev Next
Post
/api/v1/finance/journals/filter

Get a paged list of existing journals, optionally filtered to the given parameters.

Description

This endpoint retrieves a paged list of existing journal codes and names from the financial accounting administration, filtered to the given parameters. A journal is an umbrella for multiple journal posts.

Use Case

The user wants to call the GET journal operation, however does not know which code to use for the specific journal. By using the filter operation and leaving 'code' and 'name' empty the user can retrieve the list of available codes.  

Request fields

The request contains the following fields:

FieldDescription
pageSizeThe maximum number of pages to be returned per request. The default number is 100 and the maximum is 1.000. If more results are returned than specified in the PageSize, the remaining pages are dropped based on the reference (number).
pageNumberThis allows the requesting party to specify which of the pages they want to receive.
columnNameThe data field based on which sorting is applied. For example, if the results are sorted based on code, columnName will contain the value 'code'.
orderBased on this value, the property defined in 'columnName' is either sorted ascending (a-z) or descending (z-a).
codeJournal code.
nameName of the journal. In some cases, it can be entered manually. If an IBAN number is provided, Bloxs will automatically use the IBAN as the default value.
lastModified.fromThe last modified date. This defines the lower border of the range.
lastModified.toThe last modified date. This defines the upper border of the range. 

Response fields

The 200 response contains the fields in the table below. Please note that the response can contain multiple instances of journals. For the GET operation it gives a up-to-date insight in the data that is currently registered in Bloxs.

FieldDescription
pageSizeThe maximum number of pages to be returned per request. The default number is 100 and the maximum is 1.000. If more results are returned than specified in the PageSize, the remaining pages are dropped based on the reference (number).
pageNumberThis allows the requesting party to specify which of the pages they want to receive.
columnNameThe data field based on which sorting is applied. For example, if the results are sorted based on compaction code, columnName will contain the value 'compaction code'.
orderBased on this value, the property defined in 'columnName' is either sorted ascending (a-z) or descending (z-a).
codeJournal code.
nameJournal name.
lastModifiedTimestamp of the last modification within Bloxs (determined by Bloxs).
Security
HTTP
Type Bearer

Please enter a valid token

Body parameters
Expand All
object
paging
object (PagingInfo)
pageSize
integer (int32) | null
Minimum1
Maximum1000
pageNumber
integer (int32) | null
Minimum1
Maximum9999
sorting
object (SortingInfo)
columnName
string | null
order
integer (int32)
Valid values[ 0, 1 ]
filter
object (JournalSearchRequestFilter)
code
string | null
name
string | null
lastModified
object (CompareFilterModelDateTime)
from
string (date-time) | null
to
string (date-time) | null
Responses
200

OK

Expand All
object
paging
object (PagingInfo)
pageSize
integer (int32) | null
Minimum1
Maximum1000
pageNumber
integer (int32) | null
Minimum1
Maximum9999
sorting
object (SortingInfo)
columnName
string | null
order
integer (int32)
Valid values[ 0, 1 ]
journals
Array of object (JournalSearchResultFilter) | null
object
code
string | null
name
string | null
lastModified
string (date-time)