Request an Access Token based on a given grant type, indicated by grant_type and request payload properties.
Response provides information on the original Rich Authorization Request (RAR) as described in RFC 9396.
The application/json Content Type is included in the Request Body for tooling compatibility, but requests MUST be sent using the Content Type application/x-www-form-urlencoded.
The OAuth 2.0 Client ID of the Client, as set in the Open Finance Trust Framework (OFTF).
private_key_jwt client assertion
Code verifier value, created for Proof of Key Code Exchange correlating with value sent with Authorization Request.
The grant type, which must be set to authorization_code.
authorization_code The authorization code received by the TPP from the Authorization Server.
The OAuth 2.0 redirect URI of the Client, as set in the Open Finance Trust Framework. This MUST match a redirect URI value registered at the OFTF.
Access Token Scope as sent in Authorization Request and granted by the End User.
The request has succeeded.
OAuth 2.0 Access Token issued through Authorization Code grant.
Access Token type.
Bearer Validity period of Access Token in seconds.
Authorization details are sent in the Pushed Authorization Request
1Bank Data Sharing Consent
Access Token Scope as sent in Authorization Request and granted by the End User.
OAuth 2.0 state value, provided as a means to support integrity checking by the Client under FAPI 2.0. Omitted from Refresh Token Grant.
OAuth 2.0 Refresh Token. Omitted from responses where not supported by a given consent type.
OpenID Connect ID Token, returned where applicable to requested scope and supported flows.