Connector Endpoints
Funds Confirmations
Tokens
Create an access token for confirmation of funds consent. As a result, Connector should send a success, update or fail callback to Salt Edge PSD2 Compliance with result of the operation, be it success, fail or request for additional steps.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InByb3ZpZGVyX2NvZGUiOjIxLCJjbGllbnRfaWQiOjEsInJlZGlyZWN0X3VybCI6Imh0dHBzOi8vcHJpb3JhLWRlbW8uc2FsdGVkZ2UuY29tL2Jlcmxpbmdyb3VwL3BpaXMvNSIsImFwcF9uYW1lIjoiUHJpb3JhIERlbW8gUFJPRFVDVElPTiIsImF1dGhvcml6YXRpb25fdHlwZSI6Im9hdXRoIiwiYWNjb3VudCI6eyJjdXJyZW5jeSI6IkVVUiIsImliYW4iOiJERTIzMTAwMTAwMTAxMjM0NTY3ODkiLCJiYmFuIjoiNTM5MCAwNzU0IDcwMzQiLCJwYW4iOiIxMjM0MTIzNDEyMzQxMjM0IiwibWFza2VkX3BhbiI6IjEyMzQ1Nnh4eHh4eDEyMzQiLCJtc2lzZG4iOiI0NDc5MTIzNDU2NzgiLCJiYW5rX2FjY291bnRfaWRlbnRpZmllciI6IjEyMzQxMjM0MTIzNCJ9LCJjYXJkX251bWJlciI6IjEyMzQxMjM0MTIzNDEyMzQiLCJjYXJkX2V4cGlyeV9kYXRlIjoiIDIwMTktMDgtMjEiLCJjYXJkX2luZm9ybWF0aW9uIjoiY2FyZCBpbmZvcm1hdGlvbiIsInJlZ2lzdHJhdGlvbl9pbmZvcm1hdGlvbiI6InJlZ2lzdHJhdGlvbiBpbmZvcm1hdGlvbiIsInNlc3Npb25fc2VjcmV0IjoiYTA3MmY3NzYtOGFiNi02ZjYxLWIwZmQtZmJjOWJiM2ZhMDY3In0sImV4cCI6MTczMjQ0NTM1NCwiaXNzIjoicHJpb3JhLnNhbHRlZGdlLmNvbSJ9.Zc0iE7i13eNuitynibjSHFEm47M-exSnfq76Yzv2aJFNAosNC_No_p3bNXtMIIa9DrioSjgjrVsQFatinDy0tc1DRf4ieuLzxHGGDPYH5idP_JNfuCbYcjSRse3NmGlnXHQ67b-s-jwyIVR70PlhiAmv1BaYZuzBQvy0t8_QG8kDI_yU6ANSWCb8rEIfgrfhz1zhjQJxk7AYQWnBd_LvP3jkjtZN82C3j4Kp9gwgHpaNBPMayAZunwGWsnHuyi4RtgrNF-bsjEY7WRpKTuhzTLH_xzf_mfAHdpE-z2QkGsgulmdUI5_RLryAq8mXCDt5BdwQOmG4M3JjweDrjEsS7A" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Client-Id: 552" \
-X POST "https://your.connector.url/api/priora/v2/funds_confirmations/tokens"
Example of request parameters
{"data":{"provider_code":21,"client_id":1,"redirect_url":"https://priora-demo.saltedge.com/berlingroup/piis/5","app_name":"Priora Demo PRODUCTION","authorization_type":"oauth","account":{"currency":"EUR","iban":"DE2310010010123456789","bban":"5390 0754 7034","pan":"1234123412341234","masked_pan":"123456xxxxxx1234","msisdn":"447912345678","bank_account_identifier":"123412341234"},"card_number":"1234123412341234","card_expiry_date":" 2019-08-21","card_information":"card information","registration_information":"registration information","session_secret":"a072f776-8ab6-6f61-b0fd-fbc9bb3fa067"},"exp":1574093209}
Request
POST
https://your.connector.url/api/priora/v2/funds_confirmations/tokens
Headers
Header | Type | Description |
---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key .
|
Accept
|
string, required | Media type that is acceptable for the response. Allowed values: application/json |
Content-Type
|
string, required | The media type of the body of the request. Allowed values: application/json |
Client-Id
|
integer, required | TPP application identifier in Salt Edge PSD2 Compliance. |
Consent-Id
|
integer, optional | ID of the corresponding consent object. |
Psu-Device-ID
|
string, optional | UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID need to be unaltered until removal from device. |
Psu-User-Agent
|
string, optional | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Psu-Geo-Location
|
string, optional | The forwarded Geo Location of the corresponding HTTP request between PSU and TPP if available. |
Unpacked Request Authorization
Response headers
Header | Type | Description |
---|---|---|
Retry-After
|
integer, optional | Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request. |
Response
Upon successful request, 200 status code should be returned.
Delete
Revoke an already existing and active access token.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InByb3ZpZGVyX2NvZGUiOiJkZW1vYmFuayIsInNlc3Npb25fc2VjcmV0IjoiaDI5Yzk0MVBRNF9rNl82UG4tbzUifSwiZXhwIjoxNzMyNDQ1MzU1LCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.gjv0jvsEDZ_EisivBuNqhsGOesrkxbXb2P6OFfvSXKXnpy-1pU_VujdSUtG-qJsjXB7SQ2ANdALL0IJol6jC4h2lVqteFUKvog-s1ZMUoIDhw7onvBEFdm91pNkr1FFkZzPVg68wZ1EkzM4u6yV8JD_n-YHo9KTot1FbVGj-Xge1ukwf1wVPnarEB7_ySqMxXURW5-XJkoniRfFWRkp_H7VAH8kBwXyer5903N6M7ETz47IM2Wje6woB06-y95Gof0PJ0FzMkHGu4EywdTBx07QhMPgodhP30udmBjf2VB9ZGCLVq1yTniAJbh1nIZKYusyPU3CDy-FtGYi8t2Oy2w" \
-H "Access-Token: 65adc909f5676f3902787ecb6f379c1c48bfc18a222157713808274b100b9e255f7b4b59a3ecd7689cb2abe26f8705dfd89b7a0cc9e9a07a587dc64a7c4572ad" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Client-Id: 843" \
-X DELETE "https://your.connector.url/api/priora/v2/funds_confirmations/tokens"
Example of request parameters
{"data":{"provider_code":"demobank","session_secret":"h29c941PQ4_k6_6Pn-o5"},"exp":1574093209}
Request
DELETE
https://your.connector.url/api/priora/v2/funds_confirmations/tokens
Headers
Header | Type | Description |
---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key .
|
Access-Token
|
string, required | The token which is created by a connector as a result of successful authentication. |
Accept
|
string, required | Media type that is acceptable for the response. Allowed values: application/json |
Content-Type
|
string, required | The media type of the body of the request. Allowed values: application/json |
Client-Id
|
integer, required | TPP application identifier in Salt Edge PSD2 Compliance. |
Consent-Id
|
integer, optional | ID of the corresponding consent object. |
Psu-Device-ID
|
string, optional | UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID need to be unaltered until removal from device. |
Psu-User-Agent
|
string, optional | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Psu-Geo-Location
|
string, optional | The forwarded Geo Location of the corresponding HTTP request between PSU and TPP if available. |
Unpacked Request Authorization
Response headers
Header | Type | Description |
---|---|---|
Retry-After
|
integer, optional | Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request. |
Response
Upon successful request, 200 status code with an empty JSON "{}"
should be returned.
Check Funds
Checks whether a specific amount is available at point of time of the request on an account addressed by IBAN or other available identifiers.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7ImNsaWVudF9pZCI6Miwic2Vzc2lvbl9zZWNyZXQiOiJhWE1nWm1GcGJIVnlaU0IwYnlCamIyMXRkVzVwWTJGMFpRMEsiLCJhY2NvdW50Ijp7ImN1cnJlbmN5IjoiVVNEIiwibWFza2VkX3BhbiI6IioqKioqKioqKioqKjMyNDEiLCJpYmFuIjoiREUyMzEwMDEyMDAyMDEyMzQ1Njc4OSIsImJiYW4iOiI1MzkwMDc1NDcwMzQiLCJiaWMiOiJCQVJDR0IyMlhYWCIsImJhbmtfYWNjb3VudF9pZGVudGlmaWVyIjoiMTIzNDEyMzQxMjM0In0sImluc3RydWN0ZWRfYW1vdW50Ijp7ImFtb3VudCI6Ijg3IiwiY3VycmVuY3kiOiJVU0QifSwiY2FyZF9udW1iZXIiOiIxMjM0MTIzNDEyMzQxMjM0IiwicHJvdmlkZXJfY29kZSI6MjF9LCJleHAiOjE3MzI0NDUzNTUsImlzcyI6InByaW9yYS5zYWx0ZWRnZS5jb20ifQ.eilD-UOyfmfe_grHrO3ASG7lwrtJ_D5iWXt4sEYdWLOt7iUkjeLdzmWH9xD_h4j2FV4DFVzq7SIy28139Q7RwUegKippKiBxNf9txf4EtjBN4ApV2bLOVZTTSe8ws6lKOmb13Wnl3gaAipAaaBu7gvpdXTIYP6dK1AzPijuRdNviPLbkax9-ZYK0tNqpFlWb2A8nueYBp1GxRGgTGVUheo4QBwEHGrD0JGQgpqp6MqqZi-t18X4Z5EFQ486rUkw6Y6sn2t87j5Pkgca5sSNJNSFHNlH5lvn609VOMWMuKjJasv4KqX6tQE74CDdl3g_jzbJ-jE10n5peMPqOxjA4WQ" \
-H "Access-Token: aXMgZmFpbHVyZSB0byBjb21tdW5pY2F0ZQ0K" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Client-Id: 843" \
-X POST "https://your.connector.url/api/priora/v2/funds_confirmations"
Example of request parameters
{"data":{"client_id":2,"session_secret":"aXMgZmFpbHVyZSB0byBjb21tdW5pY2F0ZQ0K","account":{"currency":"USD","masked_pan":"************3241","iban":"DE23100120020123456789","bban":"539007547034","bic":"BARCGB22XXX","bank_account_identifier":"123412341234"},"instructed_amount":{"amount":"87","currency":"USD"},"card_number":"1234123412341234","provider_code":21},"exp":1571232332}
Example of response
Request
POST
https://your.connector.url/api/priora/v2/funds_confirmations
Headers
Header | Type | Description |
---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key .
|
Access-Token
|
string, required | The token which is created by a connector as a result of successful authentication. |
Accept
|
string, required | Media type that is acceptable for the response. Allowed values: application/json |
Content-Type
|
string, required | The media type of the body of the request. Allowed values: application/json |
Client-Id
|
integer, required | TPP application identifier in Salt Edge PSD2 Compliance. |
Consent-Id
|
integer, optional | ID of the corresponding consent object. |
Psu-Device-ID
|
string, optional | UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID need to be unaltered until removal from device. |
Psu-User-Agent
|
string, optional | The forwarded Agent header field of the HTTP request between PSU and TPP, if available. |
Psu-Geo-Location
|
string, optional | The forwarded Geo Location of the corresponding HTTP request between PSU and TPP if available. |
Unpacked Request Authorization
Response headers
Header | Type | Description |
---|---|---|
Retry-After
|
integer, optional | Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request. |
Response
Upon successful request, 200 status code should be returned.
Related Errors
Class | Code | Description |
---|---|---|
ResourceUnknown | 404 | The addressed resource is unknown relative to the TPP |
Salt Edge Endpoints
Sessions
Session Callback Endpoints are responsible for assuring communication between ASPSP and TPP, where ASPSP notifies about its Redirect SCA authorisation page and if the authorisation process is successful or failed.
Success
Success callback should be sent to Salt Edge PSD2 Compliance when all required verification steps have been passed, and therefore access is granted.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7ImV4dHJhIjp7fSwic2Vzc2lvbl9zZWNyZXQiOiJCVnV2ZVNMUUNyQTVqQllVeXhYZSJ9LCJleHAiOjE3MzI0NDUzNTYsImlzcyI6InByaW9yYS5zYWx0ZWRnZS5jb20ifQ.nF73YPw77RESejqWyWGqpAA66uhQcx69MeZp6c5Ogv_jGvPqiyEdXDTUvRP2nMhH5PKdLqLPU7tHynG6o1xsINQAIsySw0Z_-UTX9evf3ERjVHDr5imxAvE5y0Gme13u-VUIa-idw0u73L7hCF361mclX1_AzHwfI_drGkK0O6A0xnvoXt3YT-TIKKaNCEjJdf0cA_35hJdKptMmaCs8ajltkVS5Bylmn_J-nDJJOkQozRJZVnLLSk-1MH93yTbkfagJ5A4khxFOtheDduuSJgSbSVWuHzwOxbRaY0DnzqMHoCEyqgbUwuv5-YgNWKAnGsZe85TS5Cb_85niCS_Gog" \
-H "App-Id: qjQYP-jCx-8FBsZSgNVzIw" \
-H "App-Secret: -XeeN2UhtdphUGtI-FZpzg" \
-X PATCH "/api/connectors/v2/sessions/:session_secret/success"
Example of request parameters
Example of response
{"data":{},"meta":{"time":"2019-11-18T16:04:48.773Z"}}
Request
PATCH
/api/connectors/v2/sessions/:session_secret/success
Headers
Header | Type | Description |
---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key .
Can raise:
AuthorizationMissing
|
App-Id
|
string, required |
Provider's app_id from connection details tab.
Can raise:
ProviderNotFound, ProviderDisabled, ConfigurationError
|
App-Secret
|
string, required |
Provider's app_secret from connection details tab.
|
Unpacked Request Authorization
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
Class | Code | Description |
---|---|---|
SessionClosed | 400 | Session specified in request is already closed and cannot be modified. |
ConfigurationError | 400 | Missing configurations in dashboard. |
SessionExpired | 401 | Found session is expired and cannot be processed anymore. |
AuthorizationMissing | 401 | Authorization header is missing. |
SessionFinalised | 403 | Session specified in request is already finalised and cannot be processed. |
SessionNotFound | 404 | Session specified in request does not exist or cannot be retrieved. |
ProviderNotFound | 404 | Provider specified in request does not exist or cannot be retrieved. |
ProviderDisabled | 406 | Cooperation with specified Provider is impossible. |
Update
Update callback may be accessed multiple times in order to request multiple steps of authorization or to send other updates to Salt Edge PSD2 Compliance session.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InNlc3Npb25fZXhwaXJlc19hdCI6IjIwMjAtMDQtMTBUMTI6MzM6NTAuMjE1WiIsInN0YXR1cyI6IlJDVkQiLCJzY2Ffc3RhdHVzIjoicHN1QXV0aGVudGljYXRlZCIsInJlZGlyZWN0X3VybCI6Imh0dHBzOi8vcmVkaXJlY3QtdXJsLmNvbSIsImV4dHJhIjp7fSwic2Vzc2lvbl9zZWNyZXQiOiJCVnV2ZVNMUUNyQTVqQllVeXhYZSJ9LCJleHAiOjE3MzI0NDUzNTYsImlzcyI6InByaW9yYS5zYWx0ZWRnZS5jb20ifQ.FGDZJD2VC5j2vXnT6Vcaay19OqS27TLbtpviU5LLuYbavgku-W_TdWrHXHGpKBpViGsGedj7Nus9UeH54NQ7sCOZ9NqfQmcMkZnY2ETqx6shrnkITPgqF4pKGlA2PEVqdQUoKO_C2LGkdg-6g5CfirEEbzFaEdGU7P_6TCGhV7844XoHjg8ZFYCbbfvR3zBTlnrBqm1D1zL2cWPVpHi9RdZJbX8btz_G5_a5d5lvHkqKWAbBCdc4ijwkCXz2xduxQrRXDGTdzehxC7o6Y5uwLxYuVhMseDIWZA6Fggf2MdrOKk2wNqAhazo9ZCwEIbWZ0iI0dnuvd-8W_1hOVMBA_g" \
-H "App-Id: q5QE7Dqlpm1d5weLS5pn7w" \
-H "App-Secret: y8imt1cgG8x2zmBMrF-oxw" \
-X PATCH "/api/connectors/v2/sessions/:session_secret/update"
Example of request parameters
Example of response
{"data":{},"meta":{"time":"2019-11-18T16:04:48.853Z"}}
Request
PATCH
/api/connectors/v2/sessions/:session_secret/update
Headers
Header | Type | Description |
---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key .
Can raise:
AuthorizationMissing
|
App-Id
|
string, required |
Provider's app_id from connection details tab.
Can raise:
ProviderNotFound, ProviderDisabled, ConfigurationError
|
App-Secret
|
string, required |
Provider's app_secret from connection details tab.
|
Unpacked Request Authorization
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
Class | Code | Description |
---|---|---|
SessionClosed | 400 | Session specified in request is already closed and cannot be modified. |
ConfigurationError | 400 | Missing configurations in dashboard. |
SessionExpired | 401 | Found session is expired and cannot be processed anymore. |
AuthorizationMissing | 401 | Authorization header is missing. |
SessionFinalised | 403 | Session specified in request is already finalised and cannot be processed. |
SessionNotFound | 404 | Session specified in request does not exist or cannot be retrieved. |
ProviderNotFound | 404 | Provider specified in request does not exist or cannot be retrieved. |
ProviderDisabled | 406 | Cooperation with specified Provider is impossible. |
Fail
Fail callback should be used when authorization process has been compromised for any reason: broken request, invalid credentials, etc.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoiM1BRaXB1RFBvV3BhMTFGY1ZFVjYiLCJlcnJvcl9jbGFzcyI6IkludGVybmFsUHJvdmlkZXJFcnJvciIsImVycm9yX21lc3NhZ2UiOiJJbnRlcm5hbCBlcnJvciIsImV4dHJhIjp7fX0sImV4cCI6MTczMjQ0NTM1NywiaXNzIjoicHJpb3JhLnNhbHRlZGdlLmNvbSJ9.c-fwpFjzfXLM7n720o3vp1_smRoAMtk1er5nsXPPOxir6M7X41ZUTMVKqJCXMyxmoZ9oLl95RWap2pZfEdxj25NDYv-Yb2-udH7BdSOH-WSUofBkio_yevNNQEP7yU2IQMD1pC0h3c12WxlJnSfYvwUOvyHvj5_ZevfHEMOHseq-CB60KhOiAy2Autgp9Dl1YcUKO9etfy0cl7VMs18WCkMejsid8UmWmgXKARt2bLGXiSnf9C0rvzlevctqnERmMMVAPf2zLN2eTf2Ar9HgusXdUX0MRYmluHFEB4_h_R9-g0MVyZUAO9plDeyw_7vzFz7UsSejx4bOaF0sUUGhow" \
-H "App-Id: xU7SyhPrd95GAPSMNo_XMQ" \
-H "App-Secret: BVSkESo7zpRdzk_hWUUwCQ" \
-X PATCH "/api/connectors/v2/sessions/:session_secret/fail"
Example of request parameters
{"data":{"session_secret":"3PQipuDPoWpa11FcVEV6","error_class":"InternalProviderError","error_message":"Internal error","extra":{}},"exp":1574093208}
Example of response
{"data":{},"meta":{"time":"2019-11-18T16:04:48.710Z"}}
Request
PATCH
/api/connectors/v2/sessions/:session_secret/fail
Headers
Header | Type | Description |
---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key .
Can raise:
AuthorizationMissing
|
App-Id
|
string, required |
Provider's app_id from connection details tab.
Can raise:
ProviderNotFound, ProviderDisabled, ConfigurationError
|
App-Secret
|
string, required |
Provider's app_secret from connection details tab.
|
Unpacked Request Authorization
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
Class | Code | Description |
---|---|---|
SessionClosed | 400 | Session specified in request is already closed and cannot be modified. |
ConfigurationError | 400 | Missing configurations in dashboard. |
SessionExpired | 401 | Found session is expired and cannot be processed anymore. |
AuthorizationMissing | 401 | Authorization header is missing. |
SessionFinalised | 403 | Session specified in request is already finalised and cannot be processed. |
SessionNotFound | 404 | Session specified in request does not exist or cannot be retrieved. |
ProviderNotFound | 404 | Provider specified in request does not exist or cannot be retrieved. |
ProviderDisabled | 406 | Cooperation with specified Provider is impossible. |
Tokens
Revoke
Revoke callback needs to be called any time a token is revoked on the Provider Connector side.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7fSwiZXhwIjoxNzMyNDQ1MzU3LCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.MWxLnjZrzN1o0GMlKemBQ0w740AmOvpnXYhHZb6AR2fjWUKeW9h6rxUt-2sOFeM2GKWJKhwUogltb4Ic6vQaDqU-gC30K9WfepxownivSODmqvbRHw7V-t6yqgY1ShacVMUUjLzorNfWSWIoUPinSqaaM2bLQF50wV1kLe9A1wJHUZeJgqHHwcgrbk-JhB2GGsDbF3sJ6evjLoOINaDB6_78DHr-P3PA0sBlEVuWFexwFonzdeDa4G10C2Pilw-0u_6HzFRzj_mwf2KftHpOYZiDW5qvE3LAN1-aqRzVQEVrg3Uh2a2zs5roaO0nLNT4nZ2bgwxiuysYOWvCiaznUw" \
-H "App-Id: cfOK5P9RVooLksNv8il3rw" \
-H "App-Secret: rwkTbW41SPT55uo1I_-UGQ" \
-H "Token: example_Token" \
-X PATCH "/api/connectors/v2/funds_confirmations/tokens/revoke"
Example of request parameters
{"data":{},"exp":1574093208}
Example of response
{"data":{"revoked":true},"meta":{"time":"2019-11-18T16:04:48.928Z"}}
Request
PATCH
/api/connectors/v2/funds_confirmations/tokens/revoke
Headers
Header | Type | Description |
---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key .
Can raise:
AuthorizationMissing
|
App-Id
|
string, required |
Provider's app_id from connection details tab.
Can raise:
ProviderNotFound, ProviderDisabled, ConfigurationError
|
App-Secret
|
string, required |
Provider's app_secret from connection details tab.
|
Token
|
string, required | Token for which we are requesting info. Can raise: TokenNotFound, TokenMissing |
Unpacked Request Authorization
Response
Revoke callback needs to be called any time a token is revoked on the Provider Connector side.
Related Errors
Class | Code | Description |
---|---|---|
ConfigurationError | 400 | Missing configurations in dashboard. |
TokenMissing | 400 | This request cannot be performed without Access_Token header. |
AuthorizationMissing | 401 | Authorization header is missing. |
TokenNotFound | 401 | Token specified in request does not exist or cannot be retrieved. |
ProviderNotFound | 404 | Provider specified in request does not exist or cannot be retrieved. |
ProviderDisabled | 406 | Cooperation with specified Provider is impossible. |