VeristageDevelopers
Distribution

List recent distribution runs

GET/distribution/queue

The linked user's recent distribution runs, most recent first, scoped to their usergroup (a run is visible when the user can read the collection it distributes). Requires the read scope and distribution access (dm or dv).

Authorization

apiKey
X-Api-Key<token>

Issued to you when your integration is provisioned. Determines which catalogue resources are visible and which AI tools are available.

In: header

Query Parameters

limit?integer

Page size (max 100).

Range1 <= value <= 100
Default25
offset?integer
Range0 <= value
Default0
status?string

Optional status filter. Accepts either the numeric status code (e.g. 2) or the raw status string (e.g. complete). An unknown numeric code returns 400.

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/distribution/queue"
{  "data": {    "items": [      {        "queueRef": 555,        "destinationRef": 7,        "status": 0,        "statusLabel": "complete",        "createdAt": "2026-07-15 10:00:00"      }    ],    "total": 3,    "limit": 25,    "offset": 0  }}
{  "success": false,  "status": "fail",  "message": "string",  "error": {    "message": "API key is required",    "code": "NO_API_KEY"  }}

{  "success": false,  "status": "fail",  "message": "API key is required",  "error": {    "code": "NO_API_KEY",    "message": "API key is required"  }}

{  "success": false,  "status": "fail",  "message": "This API key does not have the 'write' scope",  "error": {    "code": "INSUFFICIENT_SCOPE",    "message": "This API key does not have the 'write' scope"  }}

Get the status of a distribution run GET

Status of one queued run. Ownership is enforced via the run's collection (usergroup scope); a run the linked user doesn't own — or one that doesn't exist — returns **404**. Requires the `read` scope and distribution access (`dm` or `dv`).

Queue a distribution run POST

Queues a distribution run for the linked user. Provide **exactly one** of `collectionRef` or `resourceRefs`: - `collectionRef` — distribute an existing collection (project). The collection must be visible to the linked user. - `resourceRefs` — distribute an ad-hoc set of resources. A collection is created to hold them (the queue distributes collections), then queued. Resources the linked user cannot see are dropped; if none remain, the call returns 404. Not-found and no-access both collapse to **404** so the surface can't be used to probe refs in other usergroups. Requires the `write` scope and the linked user's `dm` (distribution management) permission. ### Idempotency Pass an `Idempotency-Key` header (a unique random string per logical queue, e.g. a UUID) to make retries safe. The first successful response with a given key is cached for 24 hours; replays return the same body byte-for-byte with `Idempotent-Replayed: true`. Reusing the key with a different request body returns 422 `IDEMPOTENCY_KEY_CONFLICT`.