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 malformeddomainoridToken; or the email claim in theid_tokendoes not match the claimed domain (the error context includesaaoEmailDomain). 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 domain found for this account. Save the domain first withPATCH /api/v2/accounts/{customerId}/domainor via the account settings panel.500 INTERNAL_ERROR— theid_tokencould 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 the Scope3 team will follow up with you at the email address you provided.
curl
Parameters
Response
Returns202 Accepted:
Errors
400 VALIDATION_ERROR— missing or malformed fields.401 UNAUTHORIZED— missing or invalid bearer token.
Related
Update account domain
PATCH /accounts/:customerId/domain — save the domain before verifyingAccount tasks
All account operations