Versioning and changelog

The API is /api/v1. Within it we only make additive changes, which your integration must tolerate:

• new endpoints, optional request fields, response fields, headers and error codes;
• new event types (subscribe to the ones you handle, ignore the rest) and new fields in event data.

We never remove or rename a field, change its type or make an optional field required in v1. A breaking change ships as /api/v2, or for events as a new type (opportunity.updated.v2) beside the old one, announced here at least six months before the old one goes, with Deprecation and Sunset headers on the old endpoint.

Changelog

1.1.0 (October 2026)

• Idempotency-Key, external_reference, test and warnings on POST /api/v1/leads; the 202 returns lead_id and status_url.
• Problem details on every error; rate limits with RateLimit headers.
• Read endpoints: lead status, opportunities, appointments.
• Integration events: the events feed and Standard Webhooks.
• Scopes leads_read, opportunities_read, events_read; Test API clients.