A predictable model for the entire operation.
Before calling endpoints, understand how account, resources, states, and events relate to each other. The same model applies to REST, MCP and CLI.
Resources and identity
Each key belongs to a single account. IDs are opaque, stable and only make sense within that account; never derive meaning from the prefix or size.
The root of offers, audience, store, integrations and revenue.
The product found or created before any publication.
A traceable attempt to distribute an offer to a destination.
The person and service history in DU Inbox.
The versionable flow that reacts to events and performs actions.
Reconcilable evidence of commission and payment.
States and transitions
Asynchronous operations return the current state, not a promise of immediate completion. Follow the timeline or subscribe to the corresponding event.
The appeal has been accepted and given an ID.
The dedicated queue performs the task outside of the HTTP request.
The result, trials and error are available for audit.
Missing dates, values and fields
IDsOpaque strings like off_..., pub_... and conv_...DatesISO 8601 in UTC, for example 2026-08-31T18:20:00.000ZMoneyDecimal number accompanied by currency in ISO 4217Optional fieldsThey can be omitted; null represents known absenceBooleansUse true or false, never 0, 1 or textConsistency and side effects
CRUD and configuration reflect recording committed to the same account.
Publishing, importing, syncing, and execution can continue after the response.
The webhook is enqueued only after the change has been persisted.
Destructive endpoints are marked in the reference and are never inferred by an update.