Error Codes
blink Error Codes
The following tables present all the details of the possible bLink error codes you can receive when interacting with bLink APIs.
General Error Codes
| Error Code | Definition | Type | Title | Detail |
|---|---|---|---|---|
| 400 | Bad Request | /problems/INVALID_PAYLOAD | The payload was not valid | ID is missing. |
| /problems/MALFORMED_PAYLOAD | Payload does not comply with API specification | Malformed JSON. | ||
| /problems/MALFORMED_PAYLOAD | Invalid parameter values have been detected | Data for date in the future cannot be requested. | ||
| /problems/RESOURCE_TOO_LARGE | Generated resource was too large | The generated resource exceeded the size limit | ||
| /problems/INVALID_PAYLOAD | JSON not Valid | scope: must not be null | ||
| /problems/INVALID_PAYLOAD | JSON not Valid | username: must not be null | ||
| 401 | Unauthorized | /problems/INVALID_TOKEN | The OAuth Token is invalid | Something is wrong with this token. |
| /problems/EXPIRED_TOKEN | The OAuth Token is expired | The token is no longer valid. | ||
| 403 | Forbidden | /problems/INSUFFICIENT_PRIVILEGES | No privileges for the requested operation | Insufficient privileges for the requested operation. |
| 404 | Not Found | /problems/TECHNICAL_ERROR | URL not found | The requested endpoint does not exist |
| /problems/NOT_IMPLEMENTED | Feature is not implemented | This interface does not support intraday data | ||
| /problems/INSUFFICIENT_PRIVILEGES | Insufficient privileges to access resource | The provided token does not grant access to the requested resources | ||
| 405 | Not Allowed | /problems/WRONG_METHOD | This HTTP Operation is not allowed on this endpoint | Only GET operations are allowed. |
| 500 | Technical Errors | /problems/TECHNICAL_ERROR | Technical error on server side | Processing yielded a technical error. |
| /problems/RESOURCE_TOO_LARGE | Generated resource was to large | The generated resource exceeded the size limit. | ||
| 501 | Not Implemented | /problems/NOT_IMPLEMENTED | Not Implemented | This feature/endpoint is not implemented. |
| 503 | Service Unavailable | /problems/TECHNICAL_ERROR | This is the general problem description | Detailed problem description with respect to the current request, e.g., invalid account number format. |
Consent Management 2.0
| Error Code | Definition | Type | Title | Detail |
|---|---|---|---|---|
| 401 | Unauthorized | /problems/INVALID_TOKEN | The OAuth Token is invalid | Something is wrong with this token. |
| /problems/EXPIRED_TOKEN | The OAuth Token is expired | The token is no longer valid. |
Consent Management 2.0 with Consent as a Service
| Error Code | Definition | Type | Title | Detail |
|---|---|---|---|---|
| 403 | Unauthorized | /problems/EXPIRED_TOKEN | Permission expired | Specified permission has expired permanently |
| /problems/INSUFFICIENT_PRIVILEGES | Access denied | Access not allowed for specified permission |
OAuth2 Error Codes
To complement the bLink error codes, OAuth2 error codes should be utilized in cases where the OAuth2 standard applies.
Relevant parts of the OAuth2 specification regarding the error codes to use can be found here:
- https://datatracker.ietf.org/doc/html/rfc6749#section-4.1.2.1
- https://datatracker.ietf.org/doc/html/rfc6749#section-5.2
- https://datatracker.ietf.org/doc/html/rfc6749#section-7.2
- https://datatracker.ietf.org/doc/html/rfc6750#section-3.1
[The blink system specifies rfc6750 section 3 to the effect that a 401 status code MUST not only SHOULD be returned from the resource in cases where the access token provided is expired, revoked, malformed, or invalid for other reasons. Only if a 401 status code is returned the "Consent-as-a-Service" solution will make an attempt to automatically refresh the access token in this case.]