Skip to main content
Reliable Reporting registration is available for staging validation. Apostra does not send registration requests in production yet.
In staging, Reliable Reporting registration connects each active seller account and its media buys to the reporting feeds that the seller advertises through AdCP. Apostra keeps this registration current automatically. Sellers do not need to ask a buyer to register each media buy by hand.

​
What Apostra sends

During the staging preview, when a seller advertises AdCP 3.2 Reliable Reporting support, Apostra calls the seller’s sync_accounts task for each active account. The request contains the account ID, the exact media-buy scope, the selected reporting offering, and an idempotency key. Apostra sends a new configuration version when that scope changes. The seller must treat an identical idempotency key as the same request. A retry must not create a second destination, grant, or reporting configuration.

​
Registration lifecycle

The seller returns one lifecycle state for every requested configuration: Apostra periodically reads non-final registrations until the seller reports ready or inactive. It records action_required separately from ordinary setup waits and raises it for operational follow-up.

​
Return a useful setup action

For pending_setup or action_required, return either a structured setup object or a structured issue. A setup object contains:
  • a closed action: grant_access, activate_recipient, authorize_provider, or repair_access;
  • a short message that tells the operator what to complete;
  • an optional HTTPS setup URL and expiry.
The setup URL is a human entry point, not a bearer credential. Do not put tokens, signed credentials, or user information in it. Apostra does not fetch or execute the URL. After the operator completes the action, return ready from the account status read so registration can finish.

​
Changing the media-buy scope

Apostra creates a new immutable configuration generation when media buys join or leave an account’s active route set. The accepted generation becomes the current registration only after the seller reports it as ready. This prevents a delayed response for an earlier generation from replacing the current scope. For the reporting records and health states that follow registration, see Reliable Reporting.