List the rule versions of one attribution

get

https://api.doit.com/attribute/v1/attribution-center/sets/{attributionSetId}/versions

Returns the saved rule versions of one attribution, newest first, one page at a time.
Drafts are included; discarded versions are not. Use it to see how an attribution's rules
changed over time.

Paging: send limit; when the response has nextCursor, send it back as after for the
next page. No nextCursor means the last page.

Authenticate with Authorization: Bearer <token>. Omit X-Tenant-Id when the credential
resolves to one customer. When the credential can act on several customers, send
X-Tenant-Id: <tenant-id> to select one.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

attributionSetId

string

required

length ≥ 1

The attributionSetId of an attribution from listAttributeAttributionSets.

Query Params

limit

integer

1 to 200

Defaults to 100

Items per page, from 1 to 200. Defaults to 100.

after

string

The nextCursor of the previous page. Omit it for the first page.

Headers

X-Tenant-Id

string

Customer (tenant) ID for the request. This is separate from authentication: you still pass your personal or service account API token in the Authorization header (Bearer <token>). See Get Started.

When to omit (most callers): If your personal or service account token belongs to a single customer, omit this header. The API resolves that customer from the token.

When to send: If your credential can access more than one customer, set X-Tenant-Id to the customer ID you want to act on. A service account can select an active direct or nested descendant of its home customer; the endpoint's normal permissions, entitlements, and resource-ownership checks still apply. A service-account target outside that customer subtree returns 403 Forbidden. Prefer this header over the legacy customerContext query parameter, which only applies to legacy API keys and is ignored by personal and service account tokens.

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

Credentials

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

application/problem+json

200OK - One page of rule versions.

401Unauthorized - The Authorization: Bearer <token> header is missing, the token is not valid, or the person behind the token has no email address. Code: unauthorized.

409Conflict - The customer is not set up in Attribute yet (attribute_customer_not_provisioned) or its Attribute setup needs a fix by DoiT (attribute_tenant_reconciliation_required). Retrying does not help; contact DoiT support.

500Internal Server Error - Unexpected error in the Attribute service (upstream_error). Retry with backoff.

502Bad Gateway - A service behind the gateway did not answer: token check (auth_unavailable) or the Attribute service (upstream_unavailable), or the Attribute service refused the gateway (upstream_error). Retry with backoff.

503Service Unavailable - The Attribute integration is turned off (integration_disabled), the token check is unavailable (auth_unavailable), or the permission check is unavailable (authorization_unavailable). Retry later.