Use the /api/v1/recipients endpoint to add a new Data Recipient to the Open Banking API.
/api/v1/recipients endpoint to add a new Data Recipient to the Open Banking API.
To successfully call this endpoint, you must first call the /Token endpoint to obtain a valid access_token using the following settings:
client_credentials{partner client_id}{partner client_secret}client:adminBearer token obtained from the /Token endpoint.
The name of the new Data Recipient. Enter it exactly as you want customers to see it, using a maximum length of 256 characters.
256The 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 the following:
ACCOUNT_BASIC = Basic account information (required) ACCOUNT_DETAILED = Detailed account information ACCOUNT_PAYMENTS = Payment information linked to the account INVESTMENTS = Investment information linked to the account TRANSACTIONS = Payment information linked to the account STATEMENTS = PDF statements for the account CUSTOMER_CONTACT = Contact information for the account CUSTOMER_PERSONAL = Information about the customer who owns the account The scopes needs to be delimited by a space and they must include ACCOUNT_BASIC at a minimum
URL redirects for the Data Recipient, using an HTTPS scheme.
A hyperlink to the Data Recipient's logo, using the HTTPS scheme.
Countries that the Data Recipient is registered in. Possible values include: - CA - Canada - US - United States
The description of the Data Recipient, using a maximum length of 512 characters.
512A hyperlink to the terms of service between the customer and the Data Recipient, using an HTTPS scheme. Must be human-readable.
A hyperlink to the Data Recipient's corporate website, using an HTTPS scheme.
Point of contacts for the Data Recipient.