API reference

The reference documents each endpoint of the Wandura Delivery API: parameters, fields, examples, headers and errors, generated from the OpenAPI description. The rules shared by every endpoint — authentication, pagination, ticket lifetime, freshness, retries, rate limits, versioning — are on Canonical API behaviour.

Base URL#

https://www.wandura.ai

Always www.wandura.ai. The bare domain answers 308 to www, and some HTTP clients drop the body or headers of a POST when they follow a redirect.

Endpoints#

Any other path under /api/delivery/v1/ answers 404 not_found; a real path with the wrong method answers 405.

Machine-readable contract: the OpenAPI 3 description of every endpoint above is published at https://docs.wandura.ai/developers/openapi/delivery-v1.json. Use it to generate a client or to validate your integration. It changes only additively within /v1.

Server-to-server only#

Call these endpoints from your backend, never from a browser or an app: they send no CORS headers, and a key inside a client can be extracted. See Security.

Requests and responses#

• Bodies are JSON. Send Content-Type: application/json on POST.
• Film, episode, creative and video IDs are UUID strings.
• Times are ISO 8601 UTC strings (expires_at), except in the creatives feed, which uses Unix epoch seconds.
• Every response carries Wandura-Version and Wandura-API-Status: beta.
• Ignore fields, values and error codes you do not recognise: see Versioning and API evolution.

Where the shared rules live#

Beta#

The API is in beta. During the beta Wandura may still change behaviour inside /v1, under the beta rule; every change is in the changelog.