Test the API in sandbox Try-it
➤ Principle
If you are connected on the 89C3 API dev portal, you can :
call any API through the menu in which you select your app and the access token
then you enter the requested parameters of the method that you want to test (headers or body), those mandatory are flagged (with a "*")
Once done, you can execute the request and get the result (incl'd error message) based on non-real persona test data as requested by the regulation (see the use case "Test with persona").
Please note that you need to execute the request "GET /accounts" before the methods "GET /accounts/transactions" and "GET /accounts/balances" in order to retrieve the "ressourceId" parameter requierd.
➤ Version 1.4.2
As of July 8, 2020, Try-it will only be possible for version V1.4.2.
If you have already applied for GoLive or used the self-enrolment API REGISTER , then you must create a new application and select the new STET API V1.4.2.
If you have NOT made a GoLive request, you can :
- either modify your existing application to associate it with the new STET V1.4.2 API
- either create a new application, then select the new STET V1.4.2 API
➤ Try-it parameters for the API "Account information"
NB : for the parameter "body", you can copy and paste the examples (left part of the screen) in the form on right part of the screen and apply your changes.
➤ Common parameters to all methods
Parameter | Description | Data type | Parameter type | Mandatory |
---|---|---|---|---|
Authorization | access token in header | Char | Header | Yes |
PSU-IP-Address | IP address used by the customer logged-in to you app *mandated if the PSU is connected, otherwise "blank" if you use the batch mode | Char | Header | No* |
PSU-IP-Port | IP port of the device used by the PSU connected to your app | Char | Header | No |
PSU-HTTP-Method | http method used for the request | Char | Header | No |
PSU-Date | Timestamp used for the PSU request | Char | Header | No |
PSU-GEO-Location | Geographic location given by the PSU if available | Char | Header | No |
PSU-User-Agent | Header "User-Agent" sent by the PSU device connected to your app | Char | Header | No |
PSU-Referer | Header "Referer" or "Referrer" sent by the PSU device connected to your app | Char | Header | No |
PSU-Accept | Header "Accept" sent by the PSU device connected to your app | Char | Header | No |
PSU-Accept-Charset | Header "Accept-Charset" sent by the PSU device connected to your app | Char | Header | No |
PSU-Accept-Encoding | Header "Accept-Encoding" sent by the PSU device connected to your app | Char | Header | No |
PSU-Accept-Language | Header "Accept-Language" sent by the PSU device connected to your app | Char | Header | No |
Digest | Body synthesis | Char | Header | No |
Signature | HTTP request signature (see https://datatracker.ietf.org/doc/draft-cavage-http-signatures/) The header field "keyId" should be formatted as KeiId="SN=XXX,CA=YYYYYYYYYYYYYYYY" in which "XXX" is the serial number (hex format) of the QSEAL certificate QSEAL "YYYYYYYYYYYYYYYY" is the full name of the certification authority having issued this certificate A message HTTP 400 will be returned by the server in case of an invalid or missing signature | Char | Header | Yes |
X-Request-ID | Consistency Header parameter to be included in the request, and it has to be returned in the response | Char | Header | Yes |
➤ Parameters dedicated to GET /accounts/{}/balances
Parameter | Description | Data type | Parameter type | Mandatory |
---|---|---|---|---|
accountResourceId | Main identification of the account resource to fetch and used as input paramater by the request. It is obtained as the "GET /accounts" result in the "ressourceId" field | Char | Path | Yes |
➤ Parameters dedicated to GET /accounts/{}/transactions
Parameter | Description | Data type | Parameter type | Mandatory |
---|---|---|---|---|
accountResourceId | Main identification of the account resource to fetch and used as input paramater by the request. It is obtained as the "GET /accounts" result in the "ressourceId" field | Char | Path | Yes |
dateTo | Exclusive maximal imputation date of the transactions (transactions having an imputation date equal to this parameter are NOT included in the result) | Char | Request | No |
dateFrom | Inclusive minimal imputation of the transactions (= those having an imputation date equal to this parameter are included in the result) | Char | Request | No |
afterEntryReference | Specify the value on which the result has to be computed. Only transactions having a technical id GREATER than this value must be included in the result | Char | Request | No |