API availability and future waves

See what the public Capture API supports now and what remains a candidate for later review.

For: Integration developers and company administrators
Owner: Integration engineering
Outcome: Choose an integration path that matches the supported public contract.
Last verified: 2026-09-02
Next review: 2026-11-30
Status: Supported public contract

This page separates the public contract available today from ideas that may be reviewed later. Candidate waves are not available endpoints. They are not commitments or delivery promises.

Supported now

The current public contract supports the operations listed in the API reference. The reference is generated from the approved OpenAPI document. Internal signed-in CRM routes are not part of this contract.

Read the active API client with GET /info.
Capture one person with POST /person.
Capture a batch of people with POST /persons/bulk.

Use the generated reference pages for the exact request, response, authentication, and retry rules.

Candidate future waves

These groups are planning candidates only. Do not build an integration against them.

Wave A: Webhooks

Possible future review: outbound event delivery, signing, replay protection, and delivery status. No public webhook endpoint is available in the current contract.

Wave B: People and accounts

Possible future review: broader person lookup, account relationships, and controlled updates. The current contract only captures or updates a person through the supported capture operations.

Wave C: Deals, pipelines, activities, and tasks

Possible future review: pipeline records, deal stages, activities, and task workflows. These are internal product areas today. They are not public API resources.

Wave D: Administration, export, and reporting

Possible future review: client administration, data export, and reporting access. This is intentionally the last candidate wave because it needs stronger permission, privacy, and retention controls.

How to use this page

Integrate only with an operation marked as supported in the published OpenAPI contract.
Start with a local mock or synthetic test client.
Treat a missing operation as unavailable, even if a signed-in CRM page can perform a similar task.
Ask Sakhaa support to confirm the contract before planning around a candidate wave.