Authentication
Public API calls use HTTP Bearer tokens. Vestonix issues vsk_test_ secrets for Sandbox and vsk_live_ secrets for live merchants. There is no client-side environment switch — the credential itself selects the deployment it can reach.
Bearer authentication
Request
curl "https://sandbox-api.vestonix.io/v1/balances" \
-H "Authorization: Bearer vsk_test_YOUR_KEY"Test vs live
| Prefix | Use |
|---|---|
vsk_test_ | Sandbox only. No real money. |
vsk_live_ | Live merchants after Vestonix approval. Never use on Sandbox examples. |
Secret handling
- The raw secret is returned once on create and on rotate.
- Vestonix stores a hash. It cannot retrieve the secret later.
- Rotate issues a new secret. Revoke-previous stops the old one.
- Revoke invalidates the client immediately.
Scopes
Keys are issued with explicit scopes. Grant only what the integration needs. Public scopes currently include:
payments:readpayments:writequotes:readquotes:writebeneficiaries:readbeneficiaries:writebalances:readwebhooks:readwebhooks:writecustomers:readcustomers:writepayment_requests:readpayment_requests:writepayment_links:readpayment_links:writerefunds:readrefunds:writetransactions:read
quotes:* and beneficiaries:* are the names to use in new integrations. Older aliases for the same capabilities still work on the server.
Dashboard sessions and staff Control Center login are not public API authentication. Do not send merchant cookies to these endpoints from an integration.