API changelog

One version number for the whole API (info.version in the OpenAPI file, also returned by GET /v1/health). Changes inside /v1 are additive; see the versioning and deprecation policy in the API reference. Every change to the OpenAPI files gets an entry here in the same change. Versions before 1.2.0 were not recorded.

Format: Added / Changed / Deprecated / Removed.

1.4.0 (2026-11-17)

Added

  • Atomic zone changes: POST /v1/zones/{zone}/batch applies deletes, patches, puts and posts of one zone in one transaction, with a dry_run and a comment. A failed batch lists every failed operation and changes nothing.
  • RRsets: GET /v1/zones/{zone}/rrsets and GET, PUT, DELETE /v1/zones/{zone}/rrsets/{name}/{type} read and replace all values of a name and type at once.
  • dry_run: true on record create, update and bulk requests, and POST /v1/zones/{zone}/validate to check up to 500 records against a zone without writing.
  • Registrar data: GET /v1/domains/{domain} returns what the registrar knows about a domain registered through us (status, dates, nameservers, transfer lock, WHOIS privacy, and for .pl the holder and DNSSEC records at the registry). Needs the domains:read scope.
  • Transfer lock: PUT /v1/domains/{domain}/transfer-lock switches the registrar lock of a domain. It needs a signed-in session of the account owner; an API key gets 403 JWT_REQUIRED. TLDs without a registrar lock answer 409 TRANSFER_LOCK_NOT_SUPPORTED.
  • API keys: POST /v1/account/api-keys/{id}/rotate issues a new secret and keeps the old one working for a grace period, GET /v1/account/api-keys/{id}/usage shows how a key was used over the last 30 days, and the owner is reminded by e-mail before a key expires.
  • Webhooks: POST /v1/webhooks/{id}/deliveries/{delivery_id}/redeliver and GET /v1/webhooks/{id}/deliveries/{delivery_id}, a zones filter, data.before, data.after and data.actor in events, and the new events zone.batch_applied and rrset.updated. The delivery policy (5 attempts, 10 s timeout) is part of the reference.
  • Rate limits: GET /v1/account/limits shows what is left in each bucket. Changes, reads, zone imports, bulk requests and domain checks have separate buckets, and every 429 names its bucket. The RateLimit and RateLimit-Policy headers are sent next to X-RateLimit-*.
  • Lists: include=total, a Link: rel="next" header, and cursor pagination on the payment lists.
  • Null MX (RFC 7505): an MX record with content . and priority 0 says that a domain accepts no mail. It must be the only MX of its name (422 NULL_MX_CONFLICT).
  • Plan minimum TTL: min_ttl in GET /v1/plans and GET /v1/account/subscription; a lower TTL is refused with 422 TTL_BELOW_PLAN_MINIMUM.
  • Every error body carries request_id, the same value as the X-Request-Id header.
  • New error codes: INVALID_PRIO, CONTENT_TOO_LONG, RRSET_TOO_LARGE, NULL_MX_CONFLICT, BATCH_FAILED, TTL_BELOW_PLAN_MINIMUM, RRSET_NOT_FOUND, EMPTY_RRSET, RRSET_SINGLE_VALUE, RRSET_NOT_EDITABLE, TRANSFER_LOCK_NOT_SUPPORTED, REGISTRAR_ERROR.

Deprecated

  • The offset parameter of GET /v1/audit and of the payment lists: use cursor. It keeps working for at least 12 months.

Changed

  • Request validation is stricter. A request body must be a valid JSON object, fields that take a list must be sent as a list, limit must be a whole number, and flags must be JSON true or false (null means "not sent").
  • Record content is checked against size limits (a TXT value up to 4096 bytes, all TXT values of a name together up to 16384 bytes, other types up to 65535 bytes), and priority, port and similar numbers against their ranges. A zone that is not yours answers 403 ACCESS_DENIED before anything else is checked.
  • An unknown path answers 404 NOT_FOUND, and a known path with a wrong method answers 405 METHOD_NOT_ALLOWED with an Allow header.
  • Retry-After is the exact number of seconds until a slot frees up.
  • POST /v1/auth/magic-link/request answers 422 VALIDATION_ERROR for a value that is not an e-mail address.
  • OpenAPI descriptions were corrected: documented response codes, limits and nullable fields match what the API does.

1.3.0 (2026-11-02)

Added

  • GET /v1/domains: renewal ({amount, currency}) and registered_at; DELETE /v1/domains/{domain} accepts force as true/false.
  • Cursor pagination for lists, record filters and an incremental audit export.
  • Apply a template to many zones at once (POST /v1/templates/{id}/apply, Business plan).
  • Webhook payloads with id and version, more events (including zone.created and zone.imported), Slack, Discord, Microsoft Teams and Telegram formats, and POST /v1/webhooks/{id}/test.
  • Alert rules for DNS changes (dangling CNAME, record changes, delegation changes) and test endpoints for alerts and e-mail.
  • Restricted Mode: 403 ACCOUNT_FROZEN for accounts with an unpaid balance.
  • Responses: dates in RFC 3339 UTC (Z), the full resource after a write, X-Request-Id on every response.

Deprecated (not before 2027-11-02)

  • GET /v1/domains: our (use managed_by_us), registered (use registered_at), renewal_price (use renewal).

1.2.0 (2026-10-21)

Added

  • A single API version and an operationId on every operation.
  • A versioning and deprecation policy, with Deprecation, Sunset and Link headers on deprecated routes.
  • soa_serial in record write responses.

Deprecated (sunset 2027-10-21)

  • POST /v1/domains/check: use POST /v1/domains/check-single.