List failed accounting postings
GET
Returns business events that could not be posted to the ledger automatically, paginated with 0-based page and size (default 20). Filter by status (PENDING or RESOLVED); the response also includes the total pending count.
BearerAuthheader
AuthorizationBearer <JWT>status?stringOnly exceptions in this status: PENDING (still failing) or RESOLVED. Omit for all.
Value in
"PENDING""RESOLVED"page?integerPage number, starting at 0. See Paging.
Format
int32Default
0size?integerNumber of records per page.
Format
int32Default
20X-TenantID*stringYour merchant's tenant code — the value typed in the Domain field on the iotoms login screen. See Concepts.
OK
*/*- response
status*stringOutcome of the call: SUCCESS when the request was processed; otherwise an error status.
message*stringShort human-readable message describing the outcome, e.g. which record was saved or why the call failed.
data?One page of posting exceptions, newest first, plus the total pending count.
Example Request
curl -X GET 'https://beta.iotoms.com/api/v1/accounting/posting-exceptions' \ -H 'X-TenantID: your-tenant-code'Example Response
{ "status": "string", "message": "string", "data": { "content": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "sourceSystem": "string", "externalId": "string", "eventType": "string", "reasonCode": "string", "reasonDetail": "string", "status": "PENDING", "effectiveAt": "2019-08-24", "amounts": { "property1": 0, "property2": 0 }, "memo": "string", "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z", "resolvedAt": "2019-08-24T14:15:22Z", "resolvedEntryId": "e05c7998-6fd9-42d8-a16b-15fdd5bb9807" } ], "page": 0, "size": 0, "totalElements": 0, "totalPages": 0, "pendingCount": 0 }}