GET
List posting problems
Organization space Accounting module For: Accountant · Permission: posting_incidents.list Conditions
  • The accounting module must be included in the plan of the organization.
  • In the organization space the caller needs an accounting access grant on the book named in the URL.
  • Only incidents of the selected book are listed.
  • from and to must be dates in the form YYYY-MM-DD, and to must not be before from.
  • Only organization and company books have incidents; there is no client-space route.
Part of Record and correct entries.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

book
string
required

Identifier of the accounting book (a 27-character KSUID): the organization itself or one of its companies. The caller must hold an accounting access grant on it.

Query Parameters

per_page
integer | null

Number of items per page.

Required range: 1 <= x <= 100
cursor
string | null

Position in the list. Pass the meta.next_cursor or meta.prev_cursor value of the previous page; leave it out to get the first page.

sort_by
enum<string> | null

Field the list is sorted by.

Available options:
occurred_at,
created_at
sort_order
enum<string> | null

asc for ascending order, desc for descending order.

Available options:
asc,
desc
from
string<date> | null

Start of the date range, YYYY-MM-DD: only incidents that occurred on or after this day.

to
string<date> | null

End of the date range, YYYY-MM-DD: only incidents that occurred on or before this day. Must not be before from.

source_type
string | null

Only incidents of this source type (text, at most 100 characters), for example the kind of record that triggered the refused posting.

Maximum string length: 100
operation
string | null

Only incidents of this posting operation (text, at most 100 characters), for example postManualEntry.

Maximum string length: 100
response
enum<string>
default:resource

Response mode. Default resource; none answers 204 No Content.

Available options:
resource
fields
string

Comma-separated JSON keys of the root resource (id is always rendered). Available: id, owner_type, source_type, source_id, source_event, operation, reason, payload_digest, occurred_at, actor_id, actor_type, created_at.

include
string

Comma-separated include paths, each optionally followed by its fields in parentheses: units(id,sku),units.uomUnit(id,name). Max depth 6, max 40 paths. Available: .

Response

Resource.

data
PostingIncidentResource · object[]
required

Items of this page.

meta
object
required

Pagination details.