With the permission granted, you will receive a code which will allow you to retrieve the accessToken authentication and process requests involving another user. Following the OAuth 2.0 Authorization Framework specification this request is made with the attributes in x-www- form-urlencoded, rather than a JSON.
TIP
URL example for access token generation:
Now that you have your seller's permission to trade on his behalf, you will receive a `` code '' that will allow you to retrieve the authentication accessToken (OAuth token).
IMPORTANTT
Following the specification of the OAuth 2.0 Authorization Framework, this request is made with the attributes in
x-www-form-urlencoded, instead of a JSON. Observe the Header Params settings in the table above to learn how to authorize this request.
Atributos
Name | Description | Details |
|---|---|---|
| Unique identifier of the application making the request DEPRECATED | string(4) |
| APP private key DEPRECATED | string(32) |
| Seller redirect URL (must be the same one used in the permission request action) DEPRECATED | string |
| Request type desired. Possible values: AUTHORIZATION_CODE. DEPRECATED | string(18) |
| Authentication token DEPRECATED | string(32) |
| Wirecard Account id that gave you the permission DEPRECATED | string(16) |
| APP unique identifier making the request. In the format: APP-M11STAPPOAU | string(4) |
| APP private key. The | string(32) |
| Seller redirect URL (must be the same one used in the permission request action). | string |
| Request type desired. Possible values: AUTHORIZATION_CODE. | string(18) |
| Authentication token. | string(35) |
| Token to update the authentication token. | string(35) |
| Validation code to retrieve the access token. The code returned to the registered URL when the user gives permission authorization. | string(32) |
| Permissions that have been granted (Possible values according to the resource). | string |
| Wirecard account structure. | structured, |
└─ | Wirecard account id. | string, |