Hybrid-Chain API · V2

Find the API.
Build the workflow.

Connect wallets, payments, identity, data and public evidence through one versioned API. Start with an application, then explore the requests, permissions and responses for each operation.

46application guides
529production-listed routes
3implemented · awaiting deployment
330planned · not callable

Browse by application

Start with what you’re building.

Each module brings together its workflow, prerequisites and endpoint reference. Expand a category to explore its applications.

Operate15 applications
Build7 applications
Trust & Data5 applications

Hybrid ID

Identity & Access: accounts, sign-in, verification and privacy

58 production listed of 70 documented
Public Network5 applications
Administration14 applications

Endpoint directory

Find the operation you need.

Search a path, action or capability. Availability is shown for every result; authentication and runtime policy still apply.

Filter by service owner
529 matching endpoints · showing 40

Authentication

Identity sessions and federation

GET
Get account closure request/api/v2/account-closure-requests/{request_uuid}
POST
Cancel account closure request/api/v2/account-closure-requests/{request_uuid}/cancellations
GET
Get login policy/api/v2/admin/identity/login-policy
PUT
Update login policy/api/v2/admin/identity/login-policy
POST
Begin federated authorization/api/v2/auth/federation/{provider}/authorizations
POST
Exchange federated authorization/api/v2/auth/federation/{provider}/exchanges
POST
Refresh session/api/v2/auth/session-refreshes
POST
Exchange workload assertion/api/v2/auth/workload-token-exchanges
GET
Get contact projection/api/v2/me/contact
POST
Request email change/api/v2/me/contact/email-change-requests
POST
Confirm email change/api/v2/me/contact/email-change-requests/confirm
POST
Request phone change/api/v2/me/contact/phone-change-requests
POST
Confirm phone change/api/v2/me/contact/phone-change-requests/confirm
GET
Get preferences/api/v2/me/preferences
PUT
Update preferences/api/v2/me/preferences
GET
Get privacy settings/api/v2/me/privacy
PUT
Update privacy settings/api/v2/me/privacy
GET
Get core profile/api/v2/me/profile
PATCH
Update core profile/api/v2/me/profile
GET
Get verification summary/api/v2/me/verification-summary
GET
Get workspace preferences/api/v2/me/workspaces/{workspace_uuid}/preferences
PUT
Update workspace preferences/api/v2/me/workspaces/{workspace_uuid}/preferences

User Profile Data

POST
Activate account/api/v2/account-activations
GET
List linked bank accounts/api/v2/funding/bank-accounts
GET
Get referral summary/api/v2/growth/referrals
GET
Get wallet balances/api/v2/ledger/accounts/{account_id}/balances
GET
Get current profile/api/v2/me
PATCH
Update current profile/api/v2/me
GET
List authentication events/api/v2/me/authentication-events
GET
Get effective capabilities/api/v2/me/capabilities
PUT
Change password/api/v2/me/password
GET
Get symbol watchlist/api/v2/me/watchlist

Need a machine-readable list? Open the complete production contract. How availability is recorded.

For developers and agents

Build from the live contract.

Import the OpenAPI document into your SDK generator, agent tool registry or API client. It describes deployed routes, exact request shapes, authentication, scopes and response models.

Download OpenAPI JSON Explorer integration guide

Integration essentials

Know what you can call.

The directory defaults to production-listed routes. Preparation references remain available through the availability filter and are clearly marked.

Production listed

Included in the recorded production OpenAPI. Verify the live contract, required scope and runtime availability before calling.

Awaiting deployment

Implemented in source, but not in the recorded production contract. Prepare your integration; do not send requests yet.

Planned

A non-executable design reference. Do not call the endpoint or register it as an executable agent tool.

Reference version and availability details

Availability badges reflect the production OpenAPI snapshot recorded . They are not a real-time service health check.

862 public V2 operations are documented. 532 are implemented in source: 529 production listed and 3 awaiting deployment. 330 are planned. Base snapshot checksum: 14599fbf0e2136508b12580d8b27380c7715ae755cd5660102576d01efe935b0.

Market data access does not imply order entry is enabled. HTTP 202 indicates acceptance, not execution or settlement. For permissions, signing and retry rules, use the individual endpoint reference.

Separately verified POST /api/v2/data-vault/files on 2026-10-20: pinned contract and source checksums. Other recorded contract versions are preserved.

Working with an existing V1 integration? Open the V1 reference