returns LedgerJournalEntryList
Paginated journal — entries with their line items, newest first.
The entry-centric read. transactions lists transactions and hangs
entries off them, so it cannot show an entry with no parent; the
schedule engine and event handlers create exactly those, which is
why everything the close posts is absent from that list. Here an
entry stands on its own and transactionId is projected, null for a
standalone one.
Filter by provenance (schedule_derived for what the close
posted), type (adjusting / closing), status, or a parent
transactionId.
| Name | Type | Description |
|---|---|---|
| startDate | Date | Start of the entry-date window (inclusive). |
| endDate | Date | End of the entry-date window (inclusive). |
| status | String | Filter by entry status, e.g. draft or posted. |
| type | String | Filter by entry type: adjusting or closing. |
| provenance | String | Filter by what created the entry; schedule_derived is what the close posted. |
| transactionId | String | Filter to entries under one parent transaction. |
| limit | Int | Maximum rows to return, 1-1000. Omit to use this field's own default; out of range raises INVALID_PAGINATION. |
| offset | Int | Rows to skip before returning, 0 or greater. Out of range raises INVALID_PAGINATION. |
Paginated journal listing — entries with their line items expanded. Pagination counts *entries*, not line-item rows.
| Field | Type | Description |
|---|---|---|
| entries | [LedgerJournalEntry!]! | — |
| pagination | PaginationInfo! | — |
{ journalEntries }curl -X POST "https://api.robosystems.ai/extensions/$GRAPH_ID/graphql" \
-H "X-API-Key: $ROBOSYSTEMS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "{ journalEntries }"}'