Klipy's public API just grew up. API v2 is a bigger, safer, and far better-documented way to read and write your CRM - and it is the version to build on going forward.
The whole CRM, not a slice
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.
Built for automation you do not have to babysit
- Hashed API keys. Create and rotate them in Settings → 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. Grant each key exactly the access it needs - 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. The most common cause of messy CRM data, solved. - 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.
Migrate from v1 at your own pace
v1 is now deprecated. It still runs, so nothing breaks today - but new resources, security, and fixes land in v2, so plan your migration. The documentation includes a v1-to-v2 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.
Generate a key in Settings → API and open the v2 docs to get started.