API Versions¶

General Information¶

The API version controls the behavior of the API and is specified in the URL for API calls:

URL example

https://b2b-api.qiwi.com/partner/v1/sites/

When a backwards-compatible change is introduced to the API, QIWI may release a new version.

Backwards-compatible changes are those that may potentially disrupt integration.

Backwards-compatible changes may include:

Removal of a method.
Removal or renaming of a request parameter.
Removal or renaming of a response field.
Addition of a new mandatory parameter to a request.
Change in the type of a request parameter or response field.
Change in requirements for a request parameter, such as making an optional parameter mandatory.
Changes in authentication or authorization requirements.

Added the credentialOnFile field with client bank card tokenization data to the response of the payment request and to payment notifications.

Added client data fields for microfinance organization payments to the customFields and customer objects of the invoice creation request and payment request.
Added client data fields for microfinance organization payments to the payment form call with publicKey.

First version of the payment acceptance API.