> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Re-checking a publisher in your coverage

> How a seller account asks Apostra to re-read a declared publisher's adagents.json and format catalog now, and what comes back.

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`:

```json theme={null}
{ "refresh": ["vox.com"] }
```

For each domain, Apostra reads the publisher's `adagents.json` and format catalog again and returns a
`refreshed` list. Each item carries:

| Field | Meaning |
| - | - |
| `domain` | The domain that was re-checked, as Apostra stores it. |
| `adagentsStatus` | Whether the publisher's file was found and read. |
| `authorizationStatus` | Whether the publisher authorizes you now. |
| `authorizationReason` | Why, when the status is not `authorized`. |
| `identityStatus` | Whether the publisher's properties and collections were read in full. |
| `formatStatus` | Whether the publisher's format catalog was read in full. |
| `propertyCount`, `formatCount` | How many properties and formats the publisher declares. |
| `pushedToManagedAgent` | Whether the result was sent on to your managed sales agent. |

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.

## Related

* [Seller readiness](https://docs.apostra.com/v3/seller-readiness.md) reads whether publisher authorization is blocking go-live.
* [Errors](https://docs.apostra.com/v3/errors.md) explains the per-item `failures` and their codes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.