Skip to main content
When your sales agent or inventory source finishes an async task, such as create_media_buy, update_media_buy, sync_creatives or sync_accounts, it sends the result back to Apostra as a callback. We refuse a callback that fails a check, and the response we send is deliberately generic (for example 401 with no cause), so a sender cannot use it to probe the verifier. You do not have to guess the cause. The owner of the agent can read what we recorded, including the specific reason.

Read the results

Call get with kind: "agent", the agent’s id, and include: ["webhookDeliveries"]. The object carries webhookDeliveries:
A member of the account that owns the agent, or Apostra support staff who name that account, can read this: it admits the same accounts and people as reading the agent itself. An agent’s results never appear in another organization’s reads. The read covers the Inventory Sources that belong to your own organization’s accounts; an agent that serves publishers in other organizations shows only the callbacks for your own sources.

Open the Webhooks page

In an MCP host such as Claude or ChatGPT, ask for your agent’s webhook results, or call open_agent_webhooks_page with the agent’s agentId. It opens a page that lists the same results, newest first, with each refusal’s reason. The tool only reads: opening the page changes nothing, and the page shows exactly what the get read above returns for you. It is available in Seller and Agents accounts, to the same people who can read the agent.

What the read does not show

  • At most 500 sources. A read searches an agent’s first 500 Inventory Sources by id. When the agent has more, sourcesTruncated is true and the results do not include the rest, whatever hasMore says.
  • One entry per minute for a repeated refusal. We store at most one refusal a minute for the same source, operation and reason, and repeats counts the ones that followed. A sender that retries a refused callback in a tight loop reads as one entry with a count.
  • Not every callback route. Results cover the callbacks your agent sends to Apostra for your Inventory Sources: refusals, accepted media-buy callbacks, creative-sync callbacks, and delivery reports we refused. An accepted delivery report is not listed, because a source sends one per media buy per reporting period and they would bury everything else. A callback your agent sends to the callback URL we gave it as a sales agent, and an accepted sync_accounts callback, are counted but not recorded here.
  • Callbacks we could not tie to a source. A callback for a source we cannot identify has nothing to attach to, so it does not appear.

Refusal reasons

Each refusal carries one of these codes. The first column is the reasonCode. A callback that fails with task_id_missing or task_not_pending is acknowledged with a success status, because there is nothing for the sender to retry. It still reads as refused here, because we did not apply it.

Accepted callbacks

An accepted entry means we applied the callback. It says nothing about the status the callback reported: a seller’s task can fail and its callback still be accepted.

Delivery reports

A media_buy_delivery report is a callback too, and we check its body against the AdCP schema. We record every one we receive from an authenticated sender: when we received it, what we answered, the wire format, the AdCP releases we checked it against, whether every row was recorded, and the first failing field. We keep those records for up to 90 days: they are deleted after 90 days, and earlier if the Inventory Source they belong to is deleted. A report we refused (400, 413 or 503) appears in the webhook results, with the failing field where there is one, so you do not have to guess what to fix. A delivery webhook does not say which release it follows, so we accept an envelope that matches any release from AdCP 3.1 onward, and answer 400 only when it matches none of them. Send the AdCP envelope. From AdCP 3.1, a delivery report is an MCP webhook envelope with task_type: "media_buy_delivery" and the report under result, matching media-buy/media-buy-delivery-webhook-result.json for your release. Every row in media_buy_deliveries needs by_package. Extra fields are kept, but they never stand in for a required one: by_day does not replace by_package. AdCP 3.0 reports must match the 3.0 schema. In AdCP 3.0 the report itself was the body, with media_buy_deliveries at the top level and no envelope. We still accept that format when it matches the AdCP 3.0 delivery report schema, so your reporting keeps working while you move. Until 1 December 2026 we also accept a 3.0 report that does not match the 3.0 schema, and record what we found wrong. From 1 December 2026 we answer 400 to it, as we do to an envelope that does not match its schema, naming the first failing field. Move to the envelope, ideally on AdCP 3.2 with Reliable Reporting. How we answer:

Webhook signing readiness

The results also feed the webhook_signing check in Getting ready for AdCP 4.0. An agent that declares RFC 9421 webhook signing fails that check when, in the last 7 days, we refused at least 3 of its callbacks because their signatures did not verify (webhook_signature_invalid with signatureScheme rfc9421, repeats included). It clears when fewer than 3 remain in that window.