curl --request GET \
--url https://api.clinikehr.com/v1/metadata \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.clinikehr.com/v1/metadata', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.clinikehr.com/v1/metadata"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){}Get the FHIR capability statement
FHIR R4 CapabilityStatement — exactly what this gateway supports, nothing more. No bearer key required (this is the same discovery document for every caller); Content-Type is application/fhir+json, not the envelope. Lists ONLY the resources/interactions this gateway actually serves — Patient, Appointment, DocumentReference (notes), Condition, AllergyIntolerance, MedicationStatement, MedicationRequest, Practitioner (providers), Coverage, Organization (insurance payers) and MedicationKnowledge (inventory items), search parameters limited to the query filters the plain JSON routes already accept. There is no _include/_revinclude and no general /fhir passthrough — see the developer guide (api-docs/fhir.mdx) for what a partner will not find.
curl --request GET \
--url https://api.clinikehr.com/v1/metadata \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.clinikehr.com/v1/metadata', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.clinikehr.com/v1/metadata"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Response
OK.
The response is of type object.