Partner API Environments
Use the dedicated Partner API layer with environment-specific partner keys.
CryptoSwift provides a secondary Partner API layer for partners that need to create tenants, manage their partner profile, or exchange Travel Rule network messages. These endpoints use the same API roots as the Client API, but they require a dedicated Partner API key in the X-Partner-Api-Key header.
Use X-Partner-Api-Key only for Partner API endpoints under /partners/*. Regular client-level API calls still use the client x-api-key header.
Environments
| Environment | API root | Partner API documentation | Dashboard |
|---|---|---|---|
| Test | https://api-dev.cryptoswift.eu/ | https://api-dev.cryptoswift.eu/docs/partner/ | https://dashboard-dev.cryptoswift.eu/ |
| Production | https://api.cryptoswift.eu/ | https://api.cryptoswift.eu/docs/partner/ | https://dashboard.cryptoswift.eu/ |
Make sure you use the correct Partner API key for the environment you are accessing. Using a test key in production, or a production key in test, will cause authentication errors.
Authentication Pattern
curl --location 'https://api-dev.cryptoswift.eu/partners/me' \ --header 'X-Partner-Api-Key: <partner-api-key>'
Partner API keys are issued separately from client API keys. Store them server-side, keep test and production values separate, and avoid logging them in proxy middleware or webhook handlers.