We have introduced v2 of our API's. The mean reasons for this version bump is that we now provide error details according RFC7807 for all our API's and that we have introduced an updated response for the Service:GetConfig and Merchant:GetConfig. We have also added some minor changes. More details below 🌱

New way to provide error details

We now adhere to the Problem details for HTTP APIs standard (RFC7807; https://www.rfc-editor.org/rfc/rfc7807).

When HTTP response code 400 or 422 is returned in the body the details are provided as follow:

{
    "type": "https://tools.ietf.org/html/rfc2616#section-10",
    "title": "An error occurred",
    "detail": "merchant.name: Is empty\nmerchant.coc: Is empty",
    "violations": [
        {
            "propertyPath": "merchant.name",
            "message": "Is empty",
            "code": "PAY-2828"
        },
        {
            "propertyPath": "merchant.coc",
            "message": "Is empty",
            "code": "PAY-2828"
        }
    ]
}

Updated response of the Service:GetConfig and Merchant:GetConfig

We have introduced a new response of the Service:GetConfig and Merchant:GetConfig. With this change the frontend implementation to create your own checkout will become much more easier. For a detailed description, please check https://developer.pay.nl/docs/create-the-checkout

Other changes

You can now authenticate the Transaction:Create API (https://developer.pay.nl/reference/post_transactions) with an SL-code and a secret besides an AT-code and a secret
Introduced a new endpont to upload documents; Documents:Add (https://developer.pay.nl/reference/post_documents)
Added support for the accept-languageparameter in the header. If supplied the API will return 400/422 error message in the language specified, if available. If there is no translation available, we will fallback to error messages in English.