Access and environments

Public without credentials

• OAuth authorization-server metadata
• OAuth protected-resource metadata
• OpenAPI 3.1 document
• A2A Agent Card

Requires a registered OAuth client

OAuth authorization, token exchange, Agent Action API, MCP and A2A execution require a client registered by Fullness with exact HTTPS redirect URIs and reviewed scopes.

Requires an approved B2B partner

Credit, Credit Products and Financial Passport routes use a separate partner API key. They additionally require an enabled environment, accepted DPA, allowed jurisdiction, contracted purpose and the private-beta feature flag. Start with partner access.

Requires a signed-in Fullness workspace owner

Grant management, webhook endpoint management and sandbox provisioning are management operations. They use the authenticated Fullness application boundary and a selected workspace; an external OAuth access token is not a management credential.

Request access

Send the integration name, company, use case, required data, requested tools, callback URLs, intended environments and a security contact.