The Developers tab is where you manage the credentials and event integrations that connect your backend to CoinVoyage. From here you can generate your API key pair, rotate credentials when needed, and configure webhook endpoints to receive real-time payment events.Documentation Index
Fetch the complete documentation index at: https://coinvoyage-3c99945b.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
API keys
CoinVoyage issues two credentials for your integration:- Public API key — Used client-side to identify your organization when initializing the SDK.
- Secret — Used server-side to authenticate requests to the CoinVoyage API.
Creating an API key
Open the Developers tab
Generate a key pair
Click Generate API Key. CoinVoyage creates a public key and a secret for your organization.
Rotating API keys
If your secret is compromised, or as part of routine credential hygiene, you can rotate your API key pair from the Developers tab.Confirm the rotation
Confirm the action. CoinVoyage invalidates the existing credentials and generates a new public key and secret.
Rotating your API key immediately invalidates the previous secret. Make sure your updated credentials are deployed before rotating to avoid downtime.
Webhook endpoints
Webhooks allow CoinVoyage to notify your backend in real time when payment events occur, such as a payment confirmation or a dispute. You can register one or more endpoint URLs and subscribe to the specific events you care about.Adding a webhook endpoint
Open the Webhooks section
In the Developers tab, scroll to the Webhooks section and click Add Endpoint.
Select events to subscribe to
Choose the event types you want to receive — for example, payment confirmations or dispute notifications.
Security best practices
- Keep your secret server-side. Never include your API secret in frontend code, browser bundles, or mobile apps.
- Use environment variables. Store credentials in your deployment environment rather than hardcoding them in your codebase.
- Rotate immediately if compromised. If you suspect your secret has been exposed, rotate your API key pair right away and update your integration with the new credentials.
- Validate webhook signatures. Always verify the signature on incoming webhook payloads before acting on the event data.