Returns list of accounts the requestor has access to
GET/accounts
Returns list of accounts the requestor has access to Paging is done based on the account object, i.e. if limit is set to 1, then 1 account object will be returned per page.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 405
- 500
- 501
- 502
- 503
- 504
Returns list of accounts the requestor has access to.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
An opaque string value, or an empty string if there are no more results.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Bad Request - The server cannot or will not process the request due to something that is perceived to be a client error as malformed request syntax.
Response Headers
i.e. "Bearer error='invalid_token'" according to RFC6750 section-3
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Unauthorized - The request has not been applied because it lacks valid authentication credentials for the target resource.
Response Headers
i.e. "Bearer error='invalid_token'" according to RFC6750 section-3
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Forbidden - The server understood the request but refuses to authorize it.
Response Headers
i.e. "Bearer error='invalid_token'" according to RFC6750 section-3
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Not Found - The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Method Not Allowed - The method received in the request-line is known by the origin server but not supported by the target resource.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Internal Server Error - The server encountered an unexpected condition that prevented it from fulfilling the request.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Not Implemented - The server does not support the functionality required to fulfill the request.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Bad Gateway - The server received an invalid response from the upstream server.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Service Unavailable - The server is currently unable to handle the request due to a temporary overload or scheduled maintenance.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)
Gateway Timeout - The server did not get a response in time that it needed in order to complete the request.
Response Headers
Client defined ID from request to correlates HTTP requests between a client and server.
Indicates whether the response was created by the bLink platform or by the provider or by the user. (SCOPE: SIX)