API and webhooks changelog

What counts as breaking

Within v1 we may add things: new endpoints, optional parameters, fields in responses and payloads, events and headers. Build your integration to ignore fields it doesn't know. We won't remove or rename fields, change their types or meaning, or make optional parameters required — that would be a new version.

Fields and objects your admins add or remove in Setup change your workspace's own payloads; that is your data, not an API change.

October 2026 — v1 webhooks

• Webhooks for record created, updated and deleted events, per object or all objects, with bulk events for actions changing more than 20 records. See the webhooks guide.
• Signed with X-XPI-Signature (HMAC-SHA256 of the raw body); sentAt in the body for replay protection.
• Retries after 1 min, 5 min, 30 min, 2 h and 12 h; automatic switch-off after 20 failed attempts in a row and 24 hours without a success.
• Webhooks added to the OpenAPI file.

September 2026 — v1 REST API

• List, get, create/upsert, update and delete records at /api/v1/{object}, with API keys (read only or read & write, all or chosen objects). See the API reference.
• POST upserts change only the fields sent.