v1

latestOpenAPI 3.0.12026-07-141671231.8 MB

Changelogs

Get ledger entry category change events

Returns the list of changes based on the provided start_date. If no start_date is provided it returns the oldest set of recorded changes. Changes for the last 4 weeks are retained. The items will be returned using processed_at in ASC order (oldest first).

A ledger entry category change indicates that a category was added to or removed from a ledger entry (e.g. a customer invoice, a supplier invoice). Use ledger_entry.id and ledger_entry.type to identify the underlying resource to refetch.

ℹ️ This endpoint requires one of the following scopes: ledger_entries:readonly, ledger_entries:all

get/api/external/v2/changelogs/ledger_entries_categories

Query parameters

cursorstring

Example:MjAyNS0wMS0wOVQwODoyNDozOC44MTI0NTha

Cursor for pagination. Use this to fetch the next set of results. The cursor is an opaque string returned in the previous response's metadata. Leave empty for the first request.

limitinteger

Number of items to return per request. Defaults to 20 if not specified. Must be between 1 and 1000.

start_datestring date-time

Filter the changes based on the event date. The date should follow RFC3339 format. If no date is provided, the oldest changes will be returned. Changes for the last 4 weeks are retained, thus providing a start_date older than that will result in a 422 response. Providing both start_date and cursor parameters will result in a 400 response.

Response

A list of ledger entry category changes

has_moreboolean required

Indicates whether additional results are available beyond this set. Use this flag to determine if another request is needed.

next_cursorstring nullable required

Cursor to retrieve the next set of results. Include this value in the cursor parameter of your next request to fetch subsequent items. A null next_cursor in the response indicates no further results.

Example response

{
  "has_more": true,
  "next_cursor": "MjAyNS0wMS0wOVQwODoyNDozOC44MTI0NTha"
}