Skip to main content
Real buyer operations require proof that your organization controls its confirmed operator domain. This is separate from choosing the operator domain and whether the account represents the whole operator or one operating unit. An account administrator confirms that identity in Buyer Setup or with PATCH /api/v2/buyer/readiness/operator. An active account member with an email address at the exact operator domain proves it automatically. For a child account, an active member of its parent account also counts. Signing in to a different account does not prove the claim. A Scope3 SuperAdmin can instead review and approve the exact saved buyer operator domain. That approval does not change sign-in access, account membership, the account’s registered login domain, or the operator’s scope. AAO sign-in is another way to provide proof. Use it when you have an AAO account with a verified email at the operator domain. The manual review path below lets the Apostra team follow up when neither account membership nor AAO sign-in fits. These paths add proof without changing the account scope, operating-unit ID, organization membership, or billing company.

​
Verify via AAO

POST /api/v2/buyer/readiness/operator/verify Verifies the operator domain by checking the email claim in an AdCP Alliance Organization (AAO) identity token. Use this path when your work email domain matches the domain you’re claiming. The caller must have already completed the AAO OAuth flow (using openid email scopes). Pass the resulting id_token alongside the domain to verify. The server verifies the JWT signature against AAO’s public keys and compares the email domain to the claimed operator domain. On a match, the domain is marked verified for the account.
curl

​
Parameters

​
Response

​
Errors

  • 400 VALIDATION_ERROR — missing or malformed domain or idToken; or the email claim in the id_token does not match the claimed domain (the error context includes aaoEmailDomain). Use the manual review path if your email is from a different organization.
  • 401 UNAUTHORIZED — missing or invalid bearer token.
  • 404 NOT_FOUND — no saved operator identity exists for this account. Confirm it first with PATCH /api/v2/buyer/readiness/operator or in Buyer Setup.
  • 500 INTERNAL_ERROR — the id_token could not be verified (invalid signature, expired, or AAO metadata unavailable). Retry the OAuth flow.

​
Request manual review

POST /api/v2/buyer/readiness/operator/verify-request Submits a manual verification request. Use this path when you’re an agency or consultant claiming a client domain that doesn’t match your work email. Your request has been recorded. A member of Apostra team will follow up with you at the email address you provided.
curl

​
Parameters

​
Response

Returns 202 Accepted:

​
Errors

  • 400 VALIDATION_ERROR — missing or malformed fields.
  • 401 UNAUTHORIZED — missing or invalid bearer token.

Buyer setup and go-live

Confirm the operator domain, account scope, and stable operating-unit ID before proving control of the operator domain.

Account tasks

All account operations