Skip to main content
Your coverage is the set of publisher domains you sell and the properties claimed under them. Each domain carries an authorization verdict that comes from the publisher’s own adagents.json. Apostra re-reads those files on a schedule. When you have just fixed a publisher’s file, or a publisher has just published one, you can ask for a re-read now instead of waiting.

​
Read your coverage

search({ "kind": "coverage" }) lists your declared domains with each one’s authorization status and reason. get({ "kind": "coverage" }) returns the roster with the properties under each domain.

​
Re-check a publisher now

Name the declared domains in refresh on save_coverage:
For each domain, Apostra reads the publisher’s adagents.json and format catalog again and returns a refreshed list. Each item carries: The response also carries the authorization state for every domain you re-checked, so one call answers “is this publisher authorized now” without a second read.

​
Limits

  • Only domains you have declared can be re-checked. A domain you have not declared is reported in failures as NOT_FOUND, and nothing is re-checked for it.
  • A re-check counts against the same 20-edit limit as add, remove, declareProperties and removeProperties, because each one fetches from the publisher.
  • A single call spends at most 45 seconds on re-checks. A domain the call did not reach is reported in failures as SERVICE_UNAVAILABLE. Send it again in a new call.
  • refresh cannot be combined with domains, which replaces your whole set, and a domain cannot be in both remove and refresh.
  • A re-check can run in the same call as add, after it, so you can declare a domain and check it at once.
  • Seller readiness reads whether publisher authorization is blocking go-live.
  • Errors explains the per-item failures and their codes.