Auth Specification
This chapter contains information on what is required to make a successful request with the Authorization API. You will need credentials for basic authentication. Our Postman collection also contains an authorisation API call. Download the postman collection to set it up :
Endpoints
Environment | Endpoint URL |
---|---|
Sandbox | Provided via MSafe after being requested |
Production | Provided via MSafe after being requested |
How does it work?
You need an access token to use the API. To obtain an access token you need to call the oAuth API. The oAuth 2.0 specifications recommend passing the API key and secret values as an HTTP-Basic Authentication header. Don't have credentials yet? You can request them in the top right of this portal under the button "Get API keys".
Your API key and secret need to be base64 encoded before you can send them in the header.
In pseudo-code:
result = Base64Encode
(concat('ns4fQc14Zg4hKFCNaSzArVuwszX95X11
', ':','ZIjFyTsNgQN1yxI
'))
In this example, ns4fQc14Zg4hKFCNaSzArVuwszX95X11
is the API key and ZIjFyTsNgQN1yxI
is the secret.
The result being: bnM0ZlFjMTRaZzRoS0ZDTmFTekFyVnV3c3pYOTV3YOlpJakZ5VHNOZ1FOeXhJ==
Headers
- Name
Content-Type
- Type
- application/x-www-form-urlencoded
- Tag(s)
- Mandatory
- Description
Content type and encoding of the request.
- Name
Authorization
- Type
- Basic
- Tag(s)
- Mandatory
- Description
Basic authorisation token.
Request body
- Name
data-urlencode
- Type
- grant_type=client_credentials
- Tag(s)
- Mandatory
- Description
We only support the grant_type: client_credentials.
Response body
On a succesful request, you will receive an access_token
as well as some other information about your customer profile, your products when your token was issued and after how many seconds it expires.
At SurePay we do not work with refresh_tokens
. You can not refresh this token. It is advised to make another API call with basic authentication to fetch a new access_token
when this one expires.
Request Curl example
curl --location --request POST '<hostValueWillBeSharedBySurePay>/oauth/client_credential/accesstoken' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Authorization: Basic <your basic token>' \
--data-urlencode 'grant_type=client_credentials'
Response example
{
{
"refresh_token_expires_in": "0",
"api_product_list": "[Account Check V2 - Banks - Acc]"
"api_product_list_json": [
"Account Check V2 - Banks - Acc"
],
"organization_name": "surepay",
"developer.email": "service@surepay.nl",
"token_type": "BearerToken",
"issued_at": "169320014579017",
"client_id": "<your client ID>",
"access_token": "<your bearer token>",
"application_name": "123123-07c2-4e4e-9dfe-1234567ef7d3",
"scope": "",
"expires_in": "3599",
"refresh_count": "0",
"status": "approved"
}
}
- Replace
<hostValueWillBeSharedBySurePay>
with the url provided via MSafe by SurePay, and replace<your basic token>
with your own base64 encoded API key and secret.