These endpoints provide the possibility for a TPP to access the account information and transaction history of a Belfius Customer, provided TPP has received the required token(s) generated as a result of consent process.
You can use the production host when you want to go live:
Click the button below to download the open API specification.
DownloadReturns the account-details and associated balance for a given PSU account that is specified by the AISP through an encrypted logical-id of account. In case of a multi-currency account, the returned account balance is always a balance in euro. This balance is associated to the balance of the euro compartment or the globalised amount in euro of the balance of all compartments (depending on the parameter of the account). A list of each currency compartment with its balance is also provided in the API response.
If present (& with value true), it is indicating that a PSU has directly asked this account access in real-time. The PSU then might be involved in an additional consent process, if the given consent is not any more sufficient.
Encrypted Logical ID of the account which is mapped to IBAN.
Customer Access token to be passed as a header.Scope of this access-token is limited to a given type [e.g. AIS] and given IBAN. Token itself should be passed as bearer token in Authorization header like:"Bearer 987tghjkiu6trfghjuytrghj".
Request id to be passed as custom header. It will be used as sort of correlation id for logging and tracting purposes.
It must be of type application/json including version number.[Accept:application/vnd.belfius.api+json; version=1].
Accept-Language header field sent by the Client terminal. It can include language in ISO 639-1 format [example-:fr]. If no Accept-Language header is present or if it is present with a language which is not at all known to server, HTTP 406[Not Accepted] will be returned.
Client ID of registered TPP.
Redirect-URI of the client.
{ "type": "current-account", "iban": "BE80350454678790", "currency": "EUR", "balance": "123.12", "multicurrency": "True", "accountName": "Account Name", "other_compartments": [ { "currency": "EUR", "balance": -123.12 } ], "_links": { "self": { "href": "string", "templated": "boolean" }, "transactions": { "href": "string", "templated": "boolean" } } }
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
{ "type": "current-account", "iban": "BE80350454678790", "currency": "EUR", "balance": "123.12", "multicurrency": "True", "accountName": "Account Name", "other_compartments": [ { "currency": "EUR", "balance": -123.12 } ], "_links": { "self": { "href": "string", "templated": "boolean" }, "transactions": { "href": "string", "templated": "boolean" } } }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
Returns transactions for an account for a given PSU account that is specified by the AISP through an encrypted logical-id for account. The request may use some filter parameter in order to restrict the query - on a given imputation date range The result may be subject to pagination (i.e. retrieving a partial result in case of having too much results) through a set of pages by the ASPSP. Thereafter, the AISP may ask for the next page of results.
Inclusive minimal imputation date of the transactions in ISO_8601 UTC date format [YYYY-MM-DD]. Transactions having an imputation date equal to this parameter are included within the result.
Exclusive maximal imputation date of the transactions in ISO_8601 UTC date format [YYYY-MM-DD]. Transactions having an imputation date equal to this parameter are not included within the result.
If present (& with value true), it is indicating that a PSU has directly asked this account access in real-time. The PSU then might be involved in an additional consent process, if the given consent is not any more sufficient.
Caller can provide the pagesize which is records per call.
Populate with next_page_key present in the reply from API-GW if present.
ISO 4217 3-letter alphabatic Currency-codes.
Encrypted Logical ID of the account which is mapped to IBAN.
Access token to be passed as a header.Scope of this access-token is limited to a given type [e.g. AIS] and given IBAN. Token itself should be passed as bearer token in Authorization header like:"Bearer 987tghjkiu6trfghjuytrghj".
Request id to be passed as custom header. It will be used as sort of correlation id for logging and tracting purposes.
It must be of type application/json including version number.[Accept:application/vnd.belfius.api+json; version=1.2].
Accept-Language header field sent by the Client terminal. It can include language in ISO 639-1 format [example-:fr]. If no Accept-Language header is present or if it is present with a language which is not at all known to server, HTTP 406[Not Accepted] will be returned.
Client ID of registered TPP.
Redirect-URI of the client.
SCA token to be passed as header. It is mandatory only for cases where client is trying to access the transactions with date_from older than 90 days from today [date-from > today - 90 days]. Client gets this token as a result of seperate SCA flow while asking for authorization to access transaction history for date-from beyond 90 days from today. The token itself is an encrypted JWT with limited lifetime. Please note that SCA-TOKEN will be checked only if date_from & date_to are filled-in & meet the creteria of date-from > today - 90 days.
{ "_embedded": { "transactions": "[]", "next_page_key": "783j23kj2hkj2h42u492424nh24924k2" }, "_links": { "self": { "href": "string", "templated": "boolean" }, "account": { "href": "string", "templated": "boolean" } } }
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
{ "_embedded": { "transactions": "[]", "next_page_key": "783j23kj2hkj2h42u492424nh24924k2" }, "_links": { "self": { "href": "string", "templated": "boolean" }, "account": { "href": "string", "templated": "boolean" } } }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }