Onboarding is done manually by the Proof team. There is no self-service registration.
What you send to Proof
Contact the Proof team and provide the following:
| Field | Description |
|---|
| Company / product name | For partner record and identification |
| Website domain or mobile app bundle ID | Used for request origin whitelisting. Requests from other origins will be rejected. |
| Contact email | For credential delivery and support |
| Off-ramp required | Whether your users need sell (USDT → fiat) functionality. Disabled by default, enabled on request. |
What Proof sends back
| Item | Description |
|---|
partner_id | Your unique partner identifier |
client_token | Bearer token for all Proof Proxy API requests |
| API base URL | https://domain |
Keep client_token secret. It is tied to your registered domain or bundle ID. To rotate your token, contact the Proof team.
Authentication
All requests to Proof Proxy API must include:
Authorization: Bearer <client_token>
Origin header against your registered domain. Requests from unregistered origins are rejected with 403 Forbidden.
Token Rotation
To rotate your client_token, contact the Proof team. The old token will remain valid for a grace period during the transition. 
