Organization Links
Organization links enable two organizations to share access to vaults. When linked, one organization can "surface" specific vaults for the partner to see and use in transactions. This supports B2B integrations, custody partnerships, and multi-org treasury structures.
What are Organization Links?
An organization link represents:
- Partnership — Two organizations agree to share vault visibility
- Surfaced Vaults — Vaults one org exposes to the partner
- Bidirectional — Each org can surface vaults to the other
Link Lifecycle
Common Use Cases
B2B Treasury
- Partner A surfaces treasury vaults for Partner B
- Partner B can send transactions to Partner A's vaults
- Enables shared custody or settlement flows
Custody Partnerships
- Custodian surfaces client vaults to authorized parties
- Clients see only their own surfaced vaults
Best Practices
| Practice | Description |
|---|---|
| Minimal surfacing | Surface only vaults the partner needs |
| Review regularly | Audit surfaced vaults periodically |
| Revoke when done | Revoke links when partnerships end |
Related Topics
- Organizations — Organization context
- Vaults — Vaults that can be surfaced
API Reference
For complete API documentation including endpoints, request/response examples, and code samples:
- List organization links —
GET /api/v1/organization/links - Accept organization link —
POST /api/v1/organization/links/accept - Initiate organization link —
POST /api/v1/organization/links/initiate - List my surfaced vaults —
GET /api/v1/organization/links/{linkId}/my-surfaced-vaults - List partner's surfaced vaults (auto-resolved) —
GET /api/v1/organization/links/{linkId}/partner-resolved-surfaced-vaults - Revoke organization link —
PATCH /api/v1/organization/links/{linkId}/revoke - List partner's surfaced vaults —
GET /api/v1/organization/links/{linkId}/surfaced-vaults - Update surfaced vaults —
PUT /api/v1/organization/links/{linkId}/surfaced-vaults
Organization Links
Organization links enable two organizations to share access to vaults. When linked, one organization can "surface" specific vaults for the partner to see and use in transactions. This supports B2B integrations, custody partnerships, and multi-org treasury structures.
What are Organization Links?
An organization link represents:
- Partnership — Two organizations agree to share vault visibility
- Surfaced Vaults — Vaults one org exposes to the partner
- Bidirectional — Each org can surface vaults to the other
Link Lifecycle
Common Use Cases
B2B Treasury
- Partner A surfaces treasury vaults for Partner B
- Partner B can send transactions to Partner A's vaults
- Enables shared custody or settlement flows
Custody Partnerships
- Custodian surfaces client vaults to authorized parties
- Clients see only their own surfaced vaults
Best Practices
| Practice | Description |
|---|---|
| Minimal surfacing | Surface only vaults the partner needs |
| Review regularly | Audit surfaced vaults periodically |
| Revoke when done | Revoke links when partnerships end |
Related Topics
- Organizations — Organization context
- Vaults — Vaults that can be surfaced
API Reference
For complete API documentation including endpoints, request/response examples, and code samples:
- List organization links —
GET /api/v1/organization/links - Accept organization link —
POST /api/v1/organization/links/accept - Initiate organization link —
POST /api/v1/organization/links/initiate - List my surfaced vaults —
GET /api/v1/organization/links/{linkId}/my-surfaced-vaults - List partner's surfaced vaults (auto-resolved) —
GET /api/v1/organization/links/{linkId}/partner-resolved-surfaced-vaults - Revoke organization link —
PATCH /api/v1/organization/links/{linkId}/revoke - List partner's surfaced vaults —
GET /api/v1/organization/links/{linkId}/surfaced-vaults - Update surfaced vaults —
PUT /api/v1/organization/links/{linkId}/surfaced-vaults