Contact SalesStart Free

Authentication

Create a Developer API key, store it safely, and send it with each public API request.

Last updated: July 2, 2026

Summary

Public integrations use a Developer API key created inside your Sanka workspace. Copy the key once when you create it, store it in your integration or secret manager, and send it with each request.What you create in Sanka is an API key. In HTTP requests, send that key in the standard Authorization header as a Bearer value. In examples, replace <api_key> with the key you copied from Sanka.

Create an API key

  1. Open Developers → API in your workspace.
  2. Choose Create Access Token.
  3. Enter a name that identifies the integration or environment.
  4. Choose the permission level you need.
  5. Copy the key immediately. For security reasons, it is shown only once.
  6. Store it in your integration or secret manager.
  7. If the key is exposed, shared with the wrong environment, or no longer needed, delete it and create a new key.

Use the key

Bash
Authorization: Bearer <api_key>
Use the same header for Object API endpoints such as /v2/public/companies and /v2/public/orders, AI API endpoints such as /v2/enrich and /v2/score, and Data API endpoints such as /v2/prospect/companies.

Permissions

  • Regular access is read-only. Use it for integrations that only list or retrieve records.
  • Full access is write-capable. Use it when the integration creates, updates, deletes, or calls Data APIs that perform work.

Verify the key

Developer API keys are issued for a single workspace. Use GET /v2/public/auth/whoami to confirm which workspace and permission level the key resolves to:
cURL
curl "https://api.sanka.com/v2/public/auth/whoami" \
  -H "Authorization: Bearer <api_key>"
PreviousSanka API QuickstartNextBase URL