Partner API
A keyed, versioned API for firms and platforms that need to read client holdings — within the grants each client made.
The partner API lets a firm, an institution or another application read Storehouses records programmatically. It is the pull-based counterpart to Integrations.
Keys
Portal → API → Create key. A key is a bearer token (sk_live_…) shown once. Keys are scoped to the firm and inherit the firm's client grants; a key can be further restricted to read-only and to particular capabilities. Revoke a key and it stops immediately.
Authorization: Bearer sk_live_…
X-Storehouses-Version: 2026-03-01Versioning
Every request names a date version. We add fields and endpoints without changing a version; when a change would alter what an existing version returns, we publish a new date and keep the old one working. Your integration never breaks because ours moved.
What a key can read
Only what the clients granted the firm, filtered by privacy tier:
| Tier | What | Available to a key |
|---|---|---|
| P3 — reference | Registry IDs, categories, public metadata | Always |
| P2 — summary | Counts and totals by category and collection | With the client's grant |
| P1 — permissioned | Per-asset records, values, documents | With the client's explicit grant for that capability |
| P0 — encrypted | Private notes, exact serials and the other encrypted fields | Never through the API |
Endpoints
Accounts, assets, collections, locations, valuations, documents and audit events, each with list and get operations, plus webhooks for changes. The OpenAPI specification is the contract; request it from your account manager, who will also set up a sandbox key against a test account.
Rate limits and audit
Keys are rate-limited per firm. Every request is logged against the key and visible in the firm's audit logs and the client's audit trail as viewed · partner.