Skip to main content
GET
List verification subjects

Authorizations

Authorization
string
header
required

OAuth 2.0 client_credentials grant (RFC 6749 §4.4) bound to a DPoP keypair (RFC 9449).

Flow (every authenticated /v1 call requires both an access token AND a fresh per-request DPoP proof):

  1. Register a credential via the merchant portal. Anton issues a client_id (ant_oc_<env>_<32hex>) and a client_secret (ant_ocs_<env>_<48hex>, shown ONCE). The portal generates an ES256 or Ed25519 DPoP keypair in your browser; you store the private half.
  2. Mint an access token: POST /oauth/token with Authorization: Basic <client_id:client_secret> and Content-Type: application/x-www-form-urlencoded. Body: grant_type=client_credentials. A DPoP header carrying a proof signed for the token endpoint is required (no ath claim on this proof).
  3. Use the token: send Authorization: DPoP <access_token> plus a fresh DPoP: <proof> header on every /v1 request. The proof JWT MUST carry htm (request method), htu (request URL, no query/fragment), iat (within ±60s), jti (unique within 5 min), and ath (SHA-256 of the access token, base64url).

Tokens expire in 1 hour in production / staging and 8 hours in sandbox. There are no refresh tokens — call /oauth/token again with your secret. Anton's public signing key is published at /.well-known/jwks.json.

OpenAPI 3.0 has no native DPoP scheme; this declaration plus dpopHeader together convey both the access-token Authorization and the per-request proof header.

DPoP
string
header
required

Per-request DPoP proof JWT (RFC 9449). MUST accompany the Authorization: DPoP <access_token> header on every protected operation. The proof is signed by the merchant's private DPoP key and carries htm, htu, iat, jti, and ath claims.

Query Parameters

type
enum<string>

Filter by subject type.

Available options:
person,
business
status
enum<string>

Filter by the subject's current verification status. Verification attempt lifecycle status.

  • created — attempt exists, link minted, nothing delivered yet (manual delivery, or email unavailable)
  • sent — hosted link delivered to the subject by email
  • in_progress — the subject opened the flow
  • processing — submitted; provider checks running
  • awaiting_owners — business only: the business case is done, owner (UBO) flows outstanding
  • review — flagged for manual review
  • approved — verified (terminal)
  • declined — failed verification (terminal)
  • expired — the link or inquiry lapsed unused (terminal)
  • revoked — cancelled by the merchant (terminal)
Available options:
created,
sent,
in_progress,
processing,
awaiting_owners,
review,
approved,
declined,
expired,
revoked
limit
integer
default:20

Items per page. Maximum 100.

Required range: 1 <= x <= 100
cursor
string

Opaque cursor returned by a previous list response. Omit for the first page.

Response

Page of verification subjects.

data
object[]
required
has_more
boolean
required
next_cursor
string
required

Opaque cursor. Empty string on the last page.