Revenue API
//
Search journal entries (f...
Purpose
Same result as GET /journal-entries, but the filter, sort and page criteria are sent in the request body. Use it for long filters that would exceed URL length limits or for multi-value IN filters.
When to use
- Your filter is too long for a URL, or you need multi-value
IN/NOT INfilters. - You prefer to send search criteria as JSON (for example from a reporting tool) rather than as query parameters.
Notes
- Body filter
fieldNamevalues are passed through as-is and must be one of:id,name,description,reversalStatus,categoryCode,exRateType,periodId,status,reversalPeriodId,hashTotal,sobName,sobId,functionalCurrency,createdBy,createdDate,updatedBy,updatedDate,approverName. valuesmust contain at least one element for every operator (includingIS NULL/IS NOT NULL).- Filters on
periodId/reversalPeriodIdcompare against the period name (for exampleSEP-2026). pageNumberdefaults to 1 andpageSizeto 20 when omitted;pageSizeabove 40 is reduced to 40.- Use
IN/NOT INfor text comparisons; other operators compare values as-is and are intended for numeric and date fields.
Security
OneIdOAuth
Records per page. Defaults to 20; values above 40 are reduced to 40. Not applied by export endpoints, which return all rows.
Example:20
- Zuora Revenue API (base URL)https://one.zuora.com/revenue/services/v1/journal-entries/query
{ "pageNumber": 1, "pageSize": 20, "filters": [ { … }, { … } ], "ordering": { "fieldName": "createdDate", "orderBy": "DESC" } }
Page of journal entries
Total number of records that match the query across all pages.
Example:1
Response
{ "pageNumber": 1, "pageSize": 20, "totalRecords": 2, "result": [ { … }, { … } ] }