API changelog

What changed in the API and when, for those who have integrated with it.

Everything that changes the behaviour of the API for an integrator goes here: a new endpoint, a new field, a new error code or rule, a changed limit.

How to read the changelog

Compatible changes are released without a version change: a new endpoint, a new optional request field, a new response field, a new error code or a new value of details.rule. A client must skip unknown response fields and handle an unknown error code by its HTTP status.
Incompatible changes are not made in version v1: a removed or renamed endpoint or field, a field that changed its meaning or type, a required field that did not exist before. Such a change is released as a new version next to the old one, and an entry about it appears here in advance.

Entries go from newest to oldest.

The first release of the public API.

Sign-in with an API key: Authentication.
GET /api/v1/me: key check.
GET /api/v1/services: the services the merchant can accept a payment with in the key's environment.
The common error shape and the request rate limit.
The paths POST /api/v1/payments, GET /api/v1/payments/:id and GET /api/v1/payments are reserved.

Clarifications made the same day, before the first integrations:

the key's label is removed from the GET /api/v1/me response: it is an administrator's note, visible only in the console;
the Basic scheme is accepted only with an empty password;
if a key has several reasons to be rejected, one is named, in this order: revocation, expiry, disabling.