diff --git a/index.html b/index.html index c9d8959..d72af5c 100644 --- a/index.html +++ b/index.html @@ -226,8 +226,7 @@

-

Introduction

This page describes the Saferpay JSON application programming interface.

Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients. JSON will be returned in all responses from the API, including errors.

Content Encoding

UTF-8 must be used for text encoding (there are restrictions on allowed characters for specific fields though).

Content-Type and Accept headers should be set to application/json for server-to-server calls. Redirects use the standard browser types.

HTTP Headers:

Content-Type: application/json; charset=utf-8

Accept: application/json

Formats

The Saferpay JSON Api uses unified and standardized formats. The following abbreviations for format information are used in this page:

+

Introduction

This page describes the Saferpay JSON application programming interface.

Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients. JSON will be returned in all responses from the API, including errors.

Content Encoding

UTF-8 must be used for text encoding (there are restrictions on allowed characters for specific fields though).

Content-Type and Accept headers should be set to application/json for server-to-server calls. Redirects use the standard browser types.

HTTP Headers:

Content-Type: application/json; charset=utf-8

Accept: application/json

Formats

The Saferpay JSON Api uses unified and standardized formats. The following abbreviations for format information are used in this page:

@@ -15070,6 +15069,7 @@

Container "RestApi_Models_WalletInfo"

Name

Changelog

Table of Contents

Version 1.43 (released 2024-11-12)

    +
  • available on Sandbox: 2024-10-29
  • +
  • introduced version 1.43
  • +
  • added value 1.43 for SpecVersion
  • +
  • added DCC Information to the response of OmniChannel/AcquireTransaction
  • +
  • added BLIK as valid value for the field PaymentMethods
  • +
  • added new MerchantFundDistributor container with ForeignRetailer subcontainer. This affects the following requests: + +

Version 1.42 (released 2024-09-17)

  • available on Sandbox: 2024-09-03
  • introduced version 1.42