> ## 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. # List organization advertisers > Read and manage owned advertiser lifecycles plus explicitly delegated advertisers `GET /api/v2/organization/advertisers` Returns one advertiser roster across the Buyer Accounts authorized for the authenticated organization context, plus exact advertisers from accepted, unexpired organization grants. Use this endpoint when an organization needs a stable, account-spanning view; use [List advertisers](/v2/buyer/advertisers/tasks/list-advertisers) for the paginated Buyer Account list. The roster is a projection over existing advertiser records, durable lifecycle state, and authenticated relationships. It does not copy advertisers or campaigns, and matching names, domains, email domains, CRM records, signup paths, providers, or Partner status never merge records or grant access. Advertiser-scoped credentials cannot call this organization endpoint. ## Request ```bash curl theme={null} curl "https://api.interchange.io/api/v2/organization/advertisers" \ -H "Authorization: Bearer $SCOPE3_API_KEY" ``` ## Response ```json theme={null} { "data": { "entries": [ { "rosterEntryId": "owned:advertiser:12345", "advertiserId": "12345", "displayName": "Acme Corp", "relationshipClass": "owned", "operatorRelationship": "organization", "operatingMode": "managed", "sandbox": false, "system": false, "binding": { "provenance": "compatibility_account", "state": "resolved", "reason": null }, "backing": { "kind": "compatibility_account", "accountId": 101, "advertiserId": "12345" }, "delegation": null, "capabilities": { "read": true, "advertiserManagement": "available", "campaignManagement": "available", "relationshipManagement": "available" }, "readiness": { "state": "ready" } } ], "unresolvedCounterpartyRelationships": [], "lifecycles": [ { "lifecycleId": "901", "displayName": "Acme Corp", "provisioningMode": "managed", "state": "ready", "advertiserId": "12345", "targetAccountId": 101, "managementCapability": "available", "joinLink": null, "failure": null, "createdAt": "2026-08-27T05:30:00.000Z", "updatedAt": "2026-08-27T05:30:00.000Z" } ], "page": { "limit": 500, "truncated": false }, "deliveredRelationshipClasses": ["owned"] }, "error": null } ``` The endpoint always emits owned relationships. `operatingMode` is persisted explicitly; it is never inferred from a name, domain, CRM record, signup path, provider, or operator. `operatorRelationship` is separate: an active confined seller-buyer sponsorship projects `client`, even if presentation changes to `managed`. The shared contract reserves delegated and counterparty relationships, and emits delegated entries only from an explicit authorized grant binding. Owned advertisers otherwise behave as before: a plain owned advertiser is `managed` by the organization, and an advertiser backed by the confined seller-buyer sponsorship is `self_serve`, with `operatorRelationship: "client"`. An accepted, unexpired [organization advertiser grant](/v2/buyer/advertisers/tasks/manage-organization-advertiser-grants) adds only its exact advertiser IDs as `relationshipClass: "delegated"`. The entry's `delegation` object names the opaque grant reference, owner organization, reviewed capabilities, and expiry. Its `backing` object uses `kind: "authorized_relationship"` and never returns the owner's account ID. Revoked and expired entries disappear from the roster. Delegated entries are part of the limited beta for organization advertiser grants. They appear only while the Organization has an active beta entitlement and server-side beta exposure enabled by Scope3. Each delegated roster read rechecks an accepted, unexpired grant for the exact advertiser and `advertiser.read` capability. Disabling beta exposure or removing the entitlement hides delegated entries without deleting grant history. Counterparty AdCP relationship reconciliation is dark prerequisite infrastructure. No customer or internal account is enrolled by this slice, and the public API does not make counterparty entries or repair available until later activation work separately enables both the fail-closed customer flag and runtime entitlement. Once that activation exists, only the complete authenticated tuple--BrandRef domain, optional brand ID, explicit country scope, operator domain, optional operator unit, fixed currency, and sandbox--can resolve one of those entries. The seller-local `account_id` and arrival path remain provenance only. Different operators, operator units, currencies, sandbox dispositions, or explicit operating modes stay distinct even when every other identity field is identical. Incomplete, conflicting, stale, or revoked counterparty evidence remains visible in `unresolvedCounterpartyRelationships` with `operatorRelationship: "unresolved"` and no advertiser or campaign management capability. Resolved `entries` always keep their existing non-null `advertiserId` contract. `self_serve` is stored only when an administrator explicitly chooses it; it is never inferred from the account's arrival path or operator. Management capability is relative to the caller and backing account. It is `available`, `account_switch_required`, or `unavailable`. Readiness is `ready`, `pending`, `suspended`, `revoked`, `disabled`, or `incomplete`; incomplete and conflicting bindings remain visible but cannot be managed. Pending and suspended self-service entries are also read-only for advertiser and Campaign management until their sponsorship becomes active, while authorized administrators can still manage the relationship. Counterparty advertiser and Campaign management remains unavailable; a roster relationship never widens the buyer's field-level grant. The legacy Storefront `api_call` wrapper may dispatch the read-only `list_organization_advertisers` operation as V2 persona plumbing. It is not the typed `/mcp/v3` API, it does not expose repair, and while this capability is dark it cannot make counterparty entries appear without the same flag and entitlement gates. ## Repair an incoming relationship After the later activation package authorizes counterparty reconciliation, an entitled, directly authenticated Seller-admin can append an identity repair revision through direct REST with `PUT /api/v2/organization/advertisers/{relationshipRef}/reconciliation`. The repair operation is not exposed through MCP or the legacy Storefront `api_call` wrapper. The `relationshipRef` comes from `unresolvedCounterpartyRelationships[].backing.relationshipRef`. ```json theme={null} { "advertiserId": "12345", "identity": { "brand": { "domain": "acme.example", "id": null, "countries": ["GB", "US"] }, "operator": { "domain": "agency.example", "unitId": "uk-buying" }, "fixedCurrency": "GBP", "sandbox": false }, "operatingMode": "managed" } ``` Countries must be unique and sorted. Repair succeeds only when the current active grant, buyer operator identity, advertiser BrandRef, fixed currency, and sandbox disposition all match exactly. It appends a revision without changing advertiser-owned fields. The active runtime entitlement is locked and rechecked in the same transaction as the binding write, so a concurrent revocation serializes before or after repair instead of interleaving with it. Changed, revoked, ambiguous, or cross-tenant evidence returns an error and leaves the prior rows intact. The response contains at most 500 resolved entries and at most 500 unresolved counterparty relationships. If `data.page.truncated` is `true`, at least one authorized roster collection has more rows than this response can return. ## Use in Interchange Organization members can open the Advertisers page in Interchange to review the same authorized roster without switching between account-scoped advertiser lists. Self-serve clients' campaigns open from their Advertisers tab row. Each row shows relationship class, operator relationship, managed/self-serve mode, binding and readiness state, safe provenance, grant state when present, lifecycle status, and the Campaigns action currently allowed for that relationship. `system` is `true` only when Scope3 operates that advertiser through an active reviewer sandbox grant or active protected compliance-canary registration. A System advertiser is visible for context and its marker takes precedence over the other seller classes in the UI, which exposes no row mutation affordance. The roster capability fields state which API actions are currently available. The marker is provisioning provenance, not a display-name convention. Rows backed by delegated grants or counterparty relationships stay capability-limited. The page does not expose another organization's accounts, members, billing, unrelated advertisers, future advertisers, or compatibility topology; lifecycle changes, grant state, and counterparty reconciliation still use the same APIs documented here and recheck authority at execution. The Interchange page does not render or expose reusable signup links. Targeted invitation is deferred and is not part of this page. Creating advertisers or sending invitations is outside this documented surface until that separate flow ships. Lifecycle state is `invited`, `provisioning`, `ready`, `failed`, or `revoked`. A failed self-service lifecycle includes a stable recovery code for support and operator diagnostics, but this page does not document a customer retry flow. Each lifecycle carries a `managementCapability` field (`available` or `unavailable`) that reflects whether the authenticated organization context can act on that specific lifecycle. It is `available` when the caller is a human administrator with an active organization-advertiser-lifecycle entitlement. Use this field — rather than the linked roster entry's `relationshipManagement` — to gate revocation actions, including historical unclaimed self-serve lifecycles whose `advertiserId` is null (such lifecycles remain administratively revocable even after their join link is retired). ## Change presentation `PATCH /api/v2/organization/advertisers/{advertiserId}/operating-mode` changes only the explicit `operatingMode`. It never reparents a backing Buyer Account, creates a sponsorship, or grants cross-organization access. A `self_serve` advertiser without a valid sponsorship remains incomplete and unavailable. ```json theme={null} { "operatingMode": "self_serve" } ``` ## Revoke self-serve access `POST /api/v2/organization/advertisers/lifecycles/{lifecycleId}/revoke` terminally revokes the invitation and suspends the confined sponsorship. The advertiser, Campaigns, and billing history remain stored. ```json theme={null} { "reason": "Client relationship ended" } ``` ## Errors * `401 UNAUTHORIZED` — authentication is missing or invalid. * `403 ACCESS_DENIED` — an advertiser-scoped credential requested the roster, the authenticated Buyer Account could not be resolved, a mode or revoke mutation lacks administrator authority, a mode or revoke mutation lacks an active organization-advertiser-lifecycle entitlement (the `relationshipManagement` capability is `unavailable` or has expired), or a repair caller lacks Media Company type, dark-gate access, entitlement, direct-human Seller-admin authority, or exact-resource authority. * `409 CONFLICT` — lifecycle capacity is exhausted, lifecycle access is already revoked, or repair evidence is incomplete, stale, revoked, ambiguous, or does not match the complete tuple. See [Errors](/v2/reference/errors) for the full error contract. ## Related Read the paginated Buyer Account list Roster semantics, fields, and lifecycle Invite, accept, reject, or revoke exact access