Sakhaa Center

Capture API authentication

Create, store, test, rotate, deactivate, and replace Capture API credentials.

For
Integration developers and company admins
Owner
Integration engineering
Outcome
Authenticate one server-side client and complete a safe API information request.
Last verified
2026-08-30
Next review
2026-11-28
Status
supported

Every request requires the client key and one-time client secret. Create one client for one external integration and keep the secret on a server.

Create and store the client

  1. Create one API client for one external integration.
  2. Copy the secret once and store it in the server-side secret store.
  3. Record the client owner, source mapping, rate limit, and rotation date.
  4. Do not place either credential in browser code or a mobile application.

Test authentication

  • A successful response confirms the client and shows its supported capture information.
  • A 401 response means the key, secret, active state, or client scope is not accepted.
curl 'https://crm.sakhaa.ai/api/v1/capture/info' \
  -H 'X-API-Key: YOUR_API_KEY' \
  -H 'X-API-Secret: YOUR_API_SECRET'

Rotate or deactivate

  1. Create or regenerate the replacement secret during an approved maintenance window.
  2. Update the server-side integration and test the information endpoint.
  3. Stop or replace the old client only after the new path is healthy.
  4. Deactivate the client before deletion and confirm the replacement intake path.

Capture API

Create customer records through the supported external capture contract.

Capture API request examples

Capture one synthetic person with cURL, JavaScript, or Python.

On this page

Create and store the clientTest authenticationRotate or deactivate