Klipy API v2 is here. It is a bigger, safer, and better-documented way to read and write your CRM over REST, and it is the version to build on going forward. v1 still runs but is now deprecated.
What changed
v1 covered three objects. v2 covers eleven: contacts, companies, deals, pipelines, tasks, notes, segments, and interactions (read and write), plus read access to meetings, recordings, and bookings. You can also manage the relationships between them: link contacts and companies to a deal, attach records to a note, or associate a meeting with a deal or company.
v2 is built for automation you do not have to babysit:
- Hashed API keys you create and rotate in Settings then API. Only a hashed digest is stored, so a leaked database never exposes a working key. A key can be organization-wide or scoped to a single user.
- Least-privilege scopes, so you grant each key exactly the access it needs and there is no all-powerful master key.
- Idempotency keys. Send an
Idempotency-Keyon any create or update and a timed-out retry will never double-write, which solves the most common cause of messy CRM data. - Batch operations. Create up to 100 records in a single call, with a per-item status for every one.
- Clear errors. An invalid request comes back as a
422with adetails[]array pointing at the exact field that failed and why.
Who it's for
This is for developers and technical teams building integrations, syncs, or automations on top of Klipy. If you moved data with v1 or held off because it only reached three objects, v2 opens the whole CRM with the safety features production systems need.
How to use it
Generate a key in Settings then API, pick its scope, and open the v2 docs to get started. The documentation includes a v1-to-v2 migration guide and a full OpenAPI spec, and Klipy serves a live spec at /api/v2/openapi.json so the docs can never drift from the real API. v1 is deprecated but still runs, so nothing breaks today; new resources, security, and fixes land in v2, so plan your migration at your own pace.
