Use this endpoint to initiate the authorization process with a particular Data Provider.
The ID of the Data Recipient that you want to initiate the authorization process with.
The URI to redirect to after authorization is complete.
A randomly generated, unique string that's linked to this particular request. This adds an extra layer of security and is an OAuth 2.0 standard. For the request to be successful, this string must be validated to confirm it's being passed with the correct request.
Tells your server the type of response it can expect to receive from this request. For this use case, pass code as the value for this field to tell your server that you're sending an authorization code.
The scope of data that the Data Recipient collects from the customer, and is populated on the consent screen. To work with this Data Recipient, the customer must provide consent to share the scope of data they require. Possible values include:
ACCOUNT_BASIC - Basic account informationACCOUNT_DETAILED - Detailed account informationACCOUNT_PAYMENTS - Payment information linked to the accountINVESTMENTS - Investment information linked to the accountSTATEMENTS - PDF statements for the accountCUSTOMER_CONTACT - Business contact information for the accountCUSTOMER_PERSONAL - Information about the customer who owns the accountTRANSACTIONS - List of transactions for the accountThis is a space separated list. The minimum scope required is ACCOUNT_BASIC.
The ID of the Data Provider that you are authorizing.
A randomly-generated, unique identifier that correlates two or more requests.
The language that you want to display on the consent screen:
en - Englishfr - FrenchIf this field is left empty, the default value is English.
Upon successful authorization, the user is redirected to the redirect_uri with a code parameter containing the authorization code and the state parameter.
If authorization fails, the user is redirected to the redirect_uri with error, error_description, and state parameters.
The response is of type object.