Manage proxy consent for a User
Authentication
Path parameters
Response
Object containing the RedirectUrl needed for SCA redirection if triggered by the API call (otherwise returned null).
Object containing the RedirectUrl needed for SCA redirection if triggered by the API call (otherwise returned null).
Allow a user to give or revoke consent for proxy actions.
This endpoint allows your platform to manage consent given by the end user for SCA-triggering actions taken under proxy.
Your platform needs to retrieve the returned PendingUserAction.RedirectUrl, add an encoded returnUrl query parameter for them to be returned to after the SCA session, and redirect the user (read more about SCA redirection).
On the SCA session link in the response, the user can:
Read more about proxy consent for SCA-triggering actions →”
Bearer authentication of the form Bearer <token>, where token is your auth token.
If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.