Authentication
CRM API calls use a Bearer key. The portal uses a cookie. Webhooks use HMAC.
API key
http
POST https://api.bytix.ai/v1/orders
Authorization: Bearer pk_...
Content-Type: application/json- Every CRM endpoint requires this header: POST /v1/orders, POST /v1/orders/info, POST /v1/payouts, POST /v1/payouts/info, POST /v1/payout-wallets, GET /v1/payout-wallets, GET /v1/balance, and GET /v1/coins.
- Send
Bearerplus the full key. A key without the scheme is also accepted, but prefer Bearer. - Keys are hashed at rest and shown once on create or reset. The portal keeps a prefix for identification.
- Two active keys is the limit. Revoke a prefix from Settings → Developer before creating another, or reset all active keys at once. A revoked key cannot be restored.
Portal
The dashboard uses its own session. That session cannot call /v1. Only an active workspace accepts API keys. Do not send a dashboard session on an API request.
Webhooks
Incoming notifications are signed with HMAC-SHA256 of the JSON body we POST. They are not authenticated with your pk_ key. See Webhooks.