Returns all specified request headers, the request body and additional diagnostic information
POST/healthcheck
Returns all specified request headers, the request body and additional diagnostic information
Request
Responses
- 200
- 500
- 501
- 502
- 503
- 504
Health Check Response
Response Headers
Indicates whether the response was created by the bLink platform or by the provider.
Internal Server Error - The server encountered an unexpected condition that prevented it from fulfilling the request.
Examples:
-
TechnicalServerError: type: /problems/TECHNICAL_ERROR title: Technical error on server side detail: Processing yielded a technical error instance: path/to/corresponding/resource
-
ResourceTooLarge: type: /problems/RESOURCE_TOO_LARGE title: Generated resource was too large detail: The generated resource exceeded the size limit instance: path/to/corresponding/resource
Response Headers
always en
Client defined ID from request to correlate HTTP requests between a client and a server
Not Implemented - The server does not support the functionality required to fulfill the request.
Examples:
- EndpointNotImplemented: type: /problems/NOT_IMPLEMENTED title: Target endpoint is not implemented detail: This endpoint is not implemented instance: path/to/corresponding/resource
Response Headers
always en
Client defined ID from request to correlate HTTP requests between a client and a server
Bad Gateway - The upstream gateway or proxy issued an invalid response.
Response Headers
always en
Client defined ID from request to correlate HTTP requests between a client and a server
Service Unavailable - The server is currently unable to handle the request due to a temporary overload or scheduled maintenance.
Response Headers
always en
Client defined ID from request to correlate HTTP requests between a client and a server
Gateway Timeout - The upstream gateway or proxy did not provide a response in time.
Response Headers
always en
Client defined ID from request to correlate HTTP requests between a client and a server