Released docs. You are viewing the documentation published with v0.46.0. Development docs are available at Latest.
/health
const url = 'https://example.com/health';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/healthResponses
Section titled “Responses”Process is live
Invalid request or request body exceeds the configured bound
object
object
object
object
Example
{ "code": "request.invalid", "detail": "The Discovery request is invalid.", "status": 400, "title": "Invalid request", "type": "https://id.registrystack.org/problems/registry-discovery/invalid-request"}Headers
Section titled “Headers”Canonical W3C Trace Context version 0; the trace identifier equals the problem traceId.
Request exceeded the configured time limit or the response could not be produced
object
object
object
object
Example
{ "code": "request.invalid", "detail": "The Discovery request is invalid.", "status": 400, "title": "Invalid request", "type": "https://id.registrystack.org/problems/registry-discovery/invalid-request"}Headers
Section titled “Headers”Canonical W3C Trace Context version 0; the trace identifier equals the problem traceId.
Cookies on Registry Stack
We use optional cookies to understand how you use the main Registry Stack website and this documentation. If you contact us, we may link this activity to your enquiry. You can change your choice at any time. Read the privacy policy.
Your browser asks sites not to track you, so optional tracking stays off.
We could not use or save that choice. Optional tracking remains off.