API Reference
Authentication
Create, store, test, rotate, and deactivate Capture API credentials.
- For
- Integration developers and company administrators
- Owner
- Integration engineering
- Outcome
- Authenticate one server-side client and complete a safe information request.
- Last verified
- 2026-09-01
- Next review
- 2026-11-30
- Status
- Supported public contract
Every request requires two headers:
| Header | Purpose |
|---|---|
X-API-Key | Identifies the API client. |
X-API-Secret | Proves access to that client. The secret is shown once. |
Test the client
curl 'https://crm.sakhaa.ai/api/v1/capture/info' \
-H 'X-API-Key: YOUR_API_KEY' \
-H 'X-API-Secret: YOUR_API_SECRET'Keep both values in a server-side secret store. Do not send them to documentation analytics, log files, browser storage, or customer support messages.
Rotate safely
- Create or regenerate the replacement secret during an approved maintenance window.
- Update the server-side integration.
- Test
GET /info. - Stop the old client only after the replacement path is healthy.