Returns a cursor-paginated list of the transaction queries the publisher has raised, across all advertisers, within one date range of at most 31 days: on transactionDate, enquiryDate or validationDate, using the matching Gte (inclusive) and Lt (exclusive) parameters. Exactly one complete date range is required; no range, one bound only or more than one range is rejected with 400. Use it to follow up on the queries you raised and to see which were approved or declined, and why. Ordered by the date of the supplied range, descending, unless sort is given; id is always the final tiebreaker, so the order is stable across pages. Send the same filters and sort with every pageToken: a token only continues the listing that returned it. nextPageToken is omitted on the last page and never leads to an empty page. A pageToken that cannot be decoded is rejected with 400. Read-only, with no side effects.
The caller must belong to the publisher account and hold at least the Viewer role on it; otherwise the request is rejected with 403.
Personal Access Token, sent as Authorization: Bearer <token>.
Identifier of the publisher account.
Matches queries whose transactionDate (when the sale took place) is at or after this time, in UTC (inclusive). Send with transactionDateLt. Only one date range can be sent per request; otherwise the request is rejected with 400.
Matches queries whose transactionDate (when the sale took place) is before this time, in UTC (exclusive). Send with transactionDateGte; must be after it and at most 31 days later. Only one date range can be sent per request; otherwise the request is rejected with 400.
Matches queries whose enquiryDate (when the query was raised) is at or after this time, in UTC (inclusive). Send with enquiryDateLt. Only one date range can be sent per request; otherwise the request is rejected with 400.
Matches queries whose enquiryDate (when the query was raised) is before this time, in UTC (exclusive). Send with enquiryDateGte; must be after it and at most 31 days later. Only one date range can be sent per request; otherwise the request is rejected with 400.
Matches queries whose validationDate (when the query was approved or declined) is at or after this time, in UTC (inclusive). Send with validationDateLt. Pending queries have no validationDate, so never match. Only one date range can be sent per request; otherwise the request is rejected with 400.
Matches queries whose validationDate (when the query was approved or declined) is before this time, in UTC (exclusive). Send with validationDateGte; must be after it and at most 31 days later. Only one date range can be sent per request; otherwise the request is rejected with 400.
Filter by status. Supply multiple values comma-separated to match any of them, e.g. status=PENDING,DECLINED. Each status may appear once, so at most 3 values. All statuses are returned when omitted.
Restrict results to one or more advertisers. Supply multiple values comma-separated, e.g. advertiserId=1001,1002. At most 50 values.
Restrict results to one or more click references, matched exactly. Supply multiple values comma-separated. At most 50 values.
Field to sort by, following the JSON:API convention. Prefix it with - for descending order. Only one field may be given: each date, with id as the tiebreaker, already gives a complete order. When omitted, results are ordered by the date of the supplied date range, descending. id is always appended as the final tiebreaker, so the order is stable across pages. Queries with no validationDate are placed last when sorting by it. An unsupported field, or more than one field, is rejected with 400 and code INVALID_SORT.
Maximum number of results to return.
Opaque cursor token returned as nextPageToken by a previous response, used to retrieve the next page of results. Omit it to retrieve the first page.
A page of the publisher's transaction queries. An empty results array means no query matches the filters; this is not an error.
{
"results": [
{
"id": "8812345",
"enquiryId": "100245",
"advertiserId": "1001",
"publisherId": "45678",
"type": "UNTRACKED",
"status": "PENDING",
"orderRef": "ORD-2026-000123",
"clickRef": "summer-banner-01",
"saleAmount": {
"amount": "125.50",
"currency": "GBP"
},
"commission": {
"amount": "6.28",
"currency": "GBP"
},
"description": "Customer completed checkout on the app; no tracking fired.",
"transactionDate": "2026-09-12T14:03:00Z",
"enquiryDate": "2026-09-20T08:15:42Z"
},
{
"id": "8812301",
"enquiryId": "100231",
"advertiserId": "1002",
"publisherId": "45678",
"type": "INCORRECT",
"status": "DECLINED",
"orderRef": "ORD-2026-000098",
"saleAmount": {
"amount": "80.00",
"currency": "EUR"
},
"commission": {
"amount": "4.00",
"currency": "EUR"
},
"declineReason": "Order was cancelled and refunded.",
"transactionId": "3401234567",
"transactionDate": "2026-09-10T09:41:00Z",
"enquiryDate": "2026-09-15T16:20:05Z",
"validationDate": "2026-09-18T11:02:00Z"
}
],
"nextPageToken": "opaque-next-page-token"
}Opaque token for the next page. Omitted on the last page.
The results in this page.
Bad Request
{
"type": "https://help.awin.com/apis/error",
"title": "Bad Request",
"status": 400,
"detail": "Required parameters are missing from the request",
"code": "VALIDATION_FAILED",
"errors": [
{
"pointer": "/name",
"detail": "must be 100 characters or fewer"
}
]
}A URI reference identifying the problem type. APIs SHOULD define a stable, dereferenceable URI per domain-specific problem type.
A short, human-readable summary of the problem type. Stable across occurrences; does not change from occurrence to occurrence.
The HTTP status code, repeated here for convenience.
A human-readable explanation specific to this occurrence. Intended for the developer, not the end user — do not parse it.
A URI reference identifying this specific occurrence, typically the request path.
A stable, machine-readable error code. It does not change when detail is reworded, so clients branch on code, never on detail.
One entry per field that failed validation.
A human-readable explanation of this field's failure.
Unauthorized
{
"type": "https://help.awin.com/apis/error",
"title": "Unauthorized",
"status": 401,
"detail": "No valid credentials were supplied with the request",
"code": "UNAUTHORIZED"
}Problem details for an HTTP API error, as defined by RFC 9457. Served as application/problem+json.
A URI reference identifying the problem type. APIs SHOULD define a stable, dereferenceable URI per domain-specific problem type.
A short, human-readable summary of the problem type. Stable across occurrences; does not change from occurrence to occurrence.
The HTTP status code, repeated here for convenience.
A human-readable explanation specific to this occurrence. Intended for the developer, not the end user — do not parse it.
A URI reference identifying this specific occurrence, typically the request path.
A stable, machine-readable error code. It does not change when detail is reworded, so clients branch on code, never on detail.
Forbidden
{
"type": "https://help.awin.com/apis/error",
"title": "Forbidden",
"status": 403,
"detail": "You do not have the correct privileges to access this resource",
"code": "FORBIDDEN"
}Problem details for an HTTP API error, as defined by RFC 9457. Served as application/problem+json.
A URI reference identifying the problem type. APIs SHOULD define a stable, dereferenceable URI per domain-specific problem type.
A short, human-readable summary of the problem type. Stable across occurrences; does not change from occurrence to occurrence.
The HTTP status code, repeated here for convenience.
A human-readable explanation specific to this occurrence. Intended for the developer, not the end user — do not parse it.
A URI reference identifying this specific occurrence, typically the request path.
A stable, machine-readable error code. It does not change when detail is reworded, so clients branch on code, never on detail.
Too Many Requests
{
"type": "https://help.awin.com/apis/error",
"title": "User rate limit exceeded",
"status": 429,
"detail": "You have exceeded your rate limit across the public API. Retry after the number of seconds in the Retry-After header",
"code": "USER_RATE_LIMIT_EXCEEDED"
}{
"type": "https://help.awin.com/apis/error",
"title": "Route rate limit exceeded",
"status": 429,
"detail": "This endpoint is receiving more requests than it can accept right now. Retry after the number of seconds in the Retry-After header",
"code": "ROUTE_RATE_LIMIT_EXCEEDED"
}{
"type": "https://help.awin.com/apis/error",
"title": "Too Many Requests",
"status": 429,
"detail": "Rate limit exceeded",
"code": "TOO_MANY_REQUESTS"
}Problem details for an HTTP API error, as defined by RFC 9457. Served as application/problem+json.
A URI reference identifying the problem type. APIs SHOULD define a stable, dereferenceable URI per domain-specific problem type.
A short, human-readable summary of the problem type. Stable across occurrences; does not change from occurrence to occurrence.
The HTTP status code, repeated here for convenience.
A human-readable explanation specific to this occurrence. Intended for the developer, not the end user — do not parse it.
A URI reference identifying this specific occurrence, typically the request path.
A stable, machine-readable error code. It does not change when detail is reworded, so clients branch on code, never on detail.
Internal Server Error
{
"type": "https://help.awin.com/apis/error",
"title": "Internal Server Error",
"status": 500,
"detail": "An unexpected error occurred",
"code": "INTERNAL_ERROR"
}Problem details for an HTTP API error, as defined by RFC 9457. Served as application/problem+json.
A URI reference identifying the problem type. APIs SHOULD define a stable, dereferenceable URI per domain-specific problem type.
A short, human-readable summary of the problem type. Stable across occurrences; does not change from occurrence to occurrence.
The HTTP status code, repeated here for convenience.
A human-readable explanation specific to this occurrence. Intended for the developer, not the end user — do not parse it.
A URI reference identifying this specific occurrence, typically the request path.
A stable, machine-readable error code. It does not change when detail is reworded, so clients branch on code, never on detail.
Service Unavailable
{
"type": "https://help.awin.com/apis/error",
"title": "Service Unavailable",
"status": 503,
"detail": "The service is temporarily unavailable",
"code": "SERVICE_UNAVAILABLE"
}Problem details for an HTTP API error, as defined by RFC 9457. Served as application/problem+json.
A URI reference identifying the problem type. APIs SHOULD define a stable, dereferenceable URI per domain-specific problem type.
A short, human-readable summary of the problem type. Stable across occurrences; does not change from occurrence to occurrence.
The HTTP status code, repeated here for convenience.
A human-readable explanation specific to this occurrence. Intended for the developer, not the end user — do not parse it.
A URI reference identifying this specific occurrence, typically the request path.
A stable, machine-readable error code. It does not change when detail is reworded, so clients branch on code, never on detail.