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

# Recover a billing-readiness assertion

> Find the assertion id needed to revoke billing readiness for an account you've already activated

`GET /api/v2/storefront/account-mappings/relationships/{relationshipId}/ready-to-invoice`

The assert response is the only place `assertionId` appears once an account
has activated — the account itself no longer carries it, and an activated
account leaves the review queue's `billingGate` too. If you lost that
response, or you're looking at an account long after it activated and need
to [revoke](/v2/storefront/buyer-account-mapping/tasks/revoke-ready-to-invoice)
its billing readiness, use this endpoint to recover the id.

Returns every currently **active** assertion for the relationship — at most
one per `operator`/`advertiser` party. It does not return revoked or
superseded history; that's an audit-trail concern covered by the
relationship's own event history, not this recovery surface.

## Request

<CodeGroup>
  ```bash curl theme={null}
  curl https://api.interchange.io/api/v2/storefront/account-mappings/relationships/512/ready-to-invoice \
    -H "Authorization: Bearer $SCOPE3_API_KEY"
  ```
</CodeGroup>

## Parameters

| Field            | Type          | Required | Notes                                                                                               |
| ---------------- | ------------- | -------- | --------------------------------------------------------------------------------------------------- |
| `relationshipId` | string (path) | Yes      | The account relationship id, from `GET /account-mappings` or the `accountId`'s owning relationship. |

## Response

`200 OK` with every currently-active assertion for the relationship:

```json theme={null}
{
  "assertions": [
    {
      "id": "331",
      "relationshipId": "512",
      "invoiceParty": "operator",
      "billingEntity": { "legal_name": "Acme Media Ltd" },
      "authority": "erp",
      "evidence": { "reference": "ERP-88213" },
      "state": "active",
      "validFrom": "2026-08-29T20:25:04.000Z",
      "validUntil": null,
      "supersedesId": null,
      "createdAt": "2026-08-29T20:25:04.000Z",
      "createdBy": "ops@example-seller.com"
    }
  ]
}
```

An account whose billing was never asserted, or whose only assertion was
revoked, returns `{ "assertions": [] }` — not an error.

## Errors

* `401 UNAUTHORIZED` — missing or invalid API key.
* `404 NOT_FOUND` — no account relationship with this id under your storefront.

See [Errors](/v2/reference/errors) for the full error contract.

## Related

<CardGroup cols={2}>
  <Card title="Assert billing readiness" href="/v2/storefront/buyer-account-mapping/tasks/ready-to-invoice" icon="file-invoice-dollar">
    Confirm a direct-billed buyer is billable
  </Card>

  <Card title="Revoke billing readiness" href="/v2/storefront/buyer-account-mapping/tasks/revoke-ready-to-invoice" icon="ban">
    Withdraw a confirmation that stopped being true
  </Card>
</CardGroup>
