Changelog and versioning

The Developer API has a major version in the URL (/api/v1) and a dated API version that identifies the exact contract. This page shows where to find both, how to fetch the machine-readable spec, and lists the releases.

Where to read the API version

The dated version appears in four places: the X-Dakoty-Api-Version header on every API response, the field data.api_version in GET /me, the field api_version in every webhook envelope, and info.version in the OpenAPI spec. The current version is 2026-10-01. Log it with your requests, so that you can tell which contract a payload followed when you investigate a problem.

curl -sSI https://api.dakoty.com/api/v1/public/me \
  -H "Authorization: Bearer $DAKOTY_API_KEY" | grep -i x-dakoty-api-version

Write tolerant clients

Treat the contract as open for additions. Ignore response fields and webhook fields you do not know, do not depend on the order of keys or list items unless a sort parameter promises it, and handle event types you did not subscribe to without failing. Rely only on documented fields, stable error code values and HTTP statuses. The Dakoty team has not yet published a formal deprecation period, so check this page before you plan around a removal.

Download the OpenAPI spec

The spec is OpenAPI 3.1 and is the source of truth for endpoints, schemas, scopes and webhook events. It is public, needs no key, and is served with open CORS so that browser tools can load it. Use it to generate a client or import the API into a tool such as Postman. The API reference renders the same file live. Slovak texts are stored in the x-sk-* fields.

curl -sS -o public-v1.yaml https://api.dakoty.com/api/v1/openapi/public-v1.yaml
curl -sS -o public-v1.json https://api.dakoty.com/api/v1/openapi/public-v1.json

What release 2026-10-01 adds

This is the first release of the Developer API v1. It adds the following.

• Resources with list, get, create and update where it applies: companies and contacts, clients, leads (including archive and move), activities (including complete), tasks, invoices, bookings (including cancel) and orders (list).
• Lookup lists for users, lead origins, pipelines, lost reasons, activity types, tags, custom fields, projects, booking services and booking staff.
• Cursor pagination with created_after and updated_since, see Pagination and sync.
• Idempotency-Key for POST requests, see Idempotency.
• Webhooks signed with Standard Webhooks and a nine-attempt retry schedule, see Webhooks.
• REST hooks for Make, Zapier and n8n, see REST hooks.
• Scopes per resource and the rule that GET /orders is available to v1 keys only, see Authentication and scopes.

How to follow changes

Compare the info.version of the downloaded spec with the one you built against, and diff the two files when it differs. New releases are added to this page with their date. Questions and bug reports about the API go to Dakoty support.