Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.43.0.
records.facility.get
const url = 'https://example.com/v1/records/facilities/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0?accessProfile=example';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
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/v1/records/facilities/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0?accessProfile=example' \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Canonical record UUID.
Header Parameters
Section titled “Header Parameters”Optional W3C trace context. Responses carry Registry trace context for the request.
Query Parameters
Section titled “Query Parameters”Select one compiled access profile. Required when the route has no default; otherwise omission uses its default.
Comma-separated subset of readable API property names.
Responses
Section titled “Responses”Record returned
object
object
object
object
Example
{ "data": { "domainData": { "status": "active" } }, "meta": { "datasetIdentifier": "facility-registry", "entityTypeIdentifier": "facility", "registryIdentifier": "facility-registry" }}object
object
object
object
Example
{ "@context": "https://id.registrystack.org/contexts/registry-record/v1", "data": { "domainData": { "status": "active" } }, "meta": { "datasetIdentifier": "facility-registry", "entityTypeIdentifier": "facility", "registryIdentifier": "facility-registry" }}Headers
Section titled “Headers”Caller-dependent responses must not be stored.
Strong Registry ETag bound to the record, package revision, caller profile, and response field set.
Example
<https://id.registrystack.org/profiles/registry-record/v1>; rel="profile", </v1/schemas/facility>; rel="describedby"Emitted only for application/json and application/ld+json Registry Record responses and omitted for application/geo+json. Carries the Registry Record profile and caller-visible record type schema. The describedby target includes the configured deployment prefix and is never derived from Host or forwarded headers.
Responses vary by authorization and negotiated representation.
Trace context for this response.
Example
00-11111111111111111111111111111111-2222222222222222-01Problem response
object
Examples
{ "code": "request.invalid", "detail": "The request is invalid.", "status": 400, "title": "Bad Request", "traceId": "11111111111111111111111111111111", "type": "https://id.registrystack.org/problems/registry-breg/request/invalid"}Headers
Section titled “Headers”Caller-dependent responses must not be stored.
Trace context for this problem response.
Example
00-11111111111111111111111111111111-2222222222222222-01Problem response
object
Examples
{ "code": "authentication.refused", "detail": "The bearer credential is missing or refused.", "status": 401, "title": "Unauthorized", "traceId": "11111111111111111111111111111111", "type": "https://id.registrystack.org/problems/registry-breg/authentication/refused"}Headers
Section titled “Headers”Caller-dependent responses must not be stored.
Trace context for this problem response.
Example
00-11111111111111111111111111111111-2222222222222222-01Problem response
object
Examples
{ "code": "resource.not_found", "detail": "The requested resource was not found.", "status": 404, "title": "Not Found", "traceId": "11111111111111111111111111111111", "type": "https://id.registrystack.org/problems/registry-breg/resource/not_found"}Headers
Section titled “Headers”Caller-dependent responses must not be stored.
Trace context for this problem response.
Example
00-11111111111111111111111111111111-2222222222222222-01Problem response
object
Examples
{ "code": "source.unavailable", "detail": "The Registry data service is unavailable.", "status": 503, "title": "Service Unavailable", "traceId": "11111111111111111111111111111111", "type": "https://id.registrystack.org/problems/registry-breg/source/unavailable"}Headers
Section titled “Headers”Caller-dependent responses must not be stored.
Trace context for this problem response.
Example
00-11111111111111111111111111111111-2222222222222222-01Problem response
object
Examples
{ "code": "request.timeout", "detail": "The request timed out.", "status": 504, "title": "Gateway Timeout", "traceId": "11111111111111111111111111111111", "type": "https://id.registrystack.org/problems/registry-breg/request/timeout"}Headers
Section titled “Headers”Caller-dependent responses must not be stored.
Trace context for this problem response.
Example
00-11111111111111111111111111111111-2222222222222222-01