Search parties as admin
Changed onDelegated Aura access tokens require parties:read; missing scope returns 403 FORBIDDEN. Searches Party records for authenticated administrators.
query performs a case-insensitive substring search across Party name, phone, and email. name, phone, and email restrict the substring match to one contact/name field. created and updated accept inclusive RFC3339 ranges using min and max query members.
Results use deterministic cursor pagination. The default sort is name ascending; override it by providing both sort and order. Valid sort fields are name, email, phone, created, and updated; Party ID is always the final deterministic tie-breaker. Page sizes are clamped to 1–100, with a default of 21. The returned ListingSource ID searchAfter cursor is omitted on the terminal page and should be sent with the same filters and sort. Responses always use Cache-Control: no-store because contact data is returned.
Request
- Base URL: https://api.stage.aura-historia.com
- URL: https://api.stage.aura-historia.com/api/v1/admin/parties
- Auth: one of:
- HTTP bearer
- HTTP bearer
Query parameters
Optional case-insensitive substring query across Party name, phone, and email.
Optional case-insensitive substring filter for the Party name.
Optional case-insensitive substring filter for the Party phone number.
Optional case-insensitive substring filter for the Party email address.
Optional inclusive lower bound for the Party creation timestamp (RFC3339).
Optional inclusive upper bound for the Party creation timestamp (RFC3339).
Optional inclusive lower bound for the Party update timestamp (RFC3339).
Optional inclusive upper bound for the Party update timestamp (RFC3339).
Fields available for sorting admin Party-search results. Party ID is always used as a deterministic tie-breaker; absent contact values sort last.
Sort field. Valid values are name, email, phone, created, and updated. The default is name ascending.
Sort direction for sort. Provide both sort and order to override the default.
Opaque Party ID cursor returned by the previous page. It is omitted when no next page exists.
Number of Party summaries requested per page. The server clamps values to the inclusive range 1–100.
Response
Party summaries returned successfully.
Example response
{
"size": 21,
"searchAfter": "pty_71m2jxjctefykb6crqka16yf6z",
"total": 42
}Changes
- breaking
the
response property's min was decreased from1.00to0.00for the response status
- breaking
- breaking
the
//response's property format changed fromuuidto no format for status - breaking
the
response's property format changed fromuuidto no format for status - breaking
removed the required property
/from the response with the status - breaking
removed the required property
/from the response with the status - breaking
removed the required property
/from the response with the status - breaking
removed the required property
/from the response with the status - breaking
removed the required property
/from the response with the status - info
for the
queryrequest parametersearchAfter, the format was generalized fromuuidto no format - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status
- breaking