Get Main Client (identity + catalog configuration + funding token whitelist)
Returns the calling client’s business legal name, display name, callback URLs, the catalog configuration sourced from the client’s default LinkConfiguration (or null when none exists), and the inherited funding token whitelist. The funding token whitelist is READ-ONLY on this surface — it is sourced from the client’s funding configuration. See PRG-2682 / Lane C-3 for the dedicated write path.
Authorizations
Authorization header using the Bearer scheme. Example: "Authorization: Bearer {Value}"
Response
Client info returned
ok, serverFailure, permissionDenied, badRequest, notFound, conflict, tooManyRequest, locked, unavailableForLegalReasons A message generated by the API
User-friendly display message that can be presented to the end user
An error grouping hash from string components and caller information. Used by bugsnag on FE for correct error grouping
Opaque team code for error routing. Resolved from exception origin or caller file path via CODEOWNERS. Format: 2-character code (e.g., "7K", "M2"). Use for alerting/routing, not display.
Strictly-typed error type that is explaining the reason of an unsuccessful status of the operation. All possible error types are available in the documentation.
The client information returned by GET /admin/api/v1/client. Combines basic client identity
(business legal name, display name, callback URLs) with the catalog configuration sourced from the
client's default LinkConfiguration and the inherited funding token whitelist. The funding token
whitelist is read-only on this surface — see Lane C-3 (PRG-2682) for the dedicated write path.