AAkilIQ
Get an API key

Policy

Changelog and deprecations

What changed in the data API, when, and what will stop working and when.

Deprecation policy

An operation is announced as deprecated at least six months before it stops being served.

From the day it is announced, every response it gives carries a Deprecation header with the date it was deprecated, a Sunset header with the first day it may no longer be served, and a Link header to the notice.

The notice is published here, with what to use instead, and the API reference marks the operation deprecated.

A breaking change is never made within v1. It is published as a new version, and v1 keeps working until its own sunset, announced the same way.

Deprecated now

Nothing is deprecated.

Changelog

v1

  • AddedRead a published dataset's rows with GET /v1/datasets/{dataset_id}/rows, or with the specification in the body of POST /v1/datasets/{dataset_id}/query.
  • AddedFilters, sorting, field selection, search, sealed cursors and ETags with If-None-Match.
  • AddedAPI keys, live and sandbox, scoped to datasets and operations, with per-key and per-organisation rate limits.
  • AddedCredits on every response, credit quotas per period, and the X-Quota and X-Credits-Consumed headers.
  • AddedThe OpenAPI 3.1 document, the deprecation policy and this changelog.