Purpose
The authentication and scope model the API must have before the intelligence surface publishes for external integrations.What is required before this publishes
- API-key or OAuth client-credentials auth.
- Scopes, at minimum:
readwritedestructivebilling/comms-impacting, for operations that spend money or message candidates (phone calls, AI interviews, invite sends)
- Per-key rate limits and quotas across every published endpoint.
- Per-organization data-access controls enforced at the API gateway for every published operation.
- GraphQL versioning and a deprecation policy.
- DPA and legal sign-off for any operation returning candidate PII (reports, transcripts, recordings).
Scope-gated operations
Operations that spend money, message candidates, change decisions or delete data each require their own scope. The full scope map is published with the API when it goes live.The Career Page capability is exempt. It is
public and unauthenticated by design.
Tracking
Progress against this checklist is tracked internally. This checklist applies to the partner API.FAQs
Can we integrate with the API today?
Can we integrate with the API today?
Not as a partner API client. API-key or OAuth client-credentials auth is Upcoming. For assistant access, see Connected Agent Access.
What scopes will exist?
What scopes will exist?
At minimum
read, write, destructive, and billing/comms-impacting, plus
decisions:write for decision overrides.Why are some operations scope-gated?
Why are some operations scope-gated?
Because they spend money, message candidates, or change the hiring audit trail. Those are never in the default read tier.
Is anything public without auth?
Is anything public without auth?
Yes, the Career Page. Partner API operations require partner credentials.
Related
- API Introduction. MCP setup and the proposed partner API.

