Server-side APIEndpointsClinical records

Record vitals

Add a vitals reading for a patient, at a location.

POST /v1/patients/{patientId}/vitals

addressId is required by medos — a vitals reading belongs to the visit's location, and the gateway does not guess it.

API-key only (a widget session is refused), entitlement-gated on devapi_patients_vitals_create, and attributed with X-Acting-User-Id.

Path parameters

NameRequiredDescription
patientIdYesFills the :patientId segment.

Query parameters

NameRequiredDescription
addressIdYesRequired by medos — a reading belongs to the visit's location, and the gateway does not guess it.

Body

NameRequiredDescription
heightNo—
weightNo—
bloodPressureNo—
pulseNo—
temperatureNo—

Try it

POST/v1/patients/:patientId/vitalsAPI key onlydevapi_patients_vitals_create

Path

Query

Body

Request
POST /v1/patients//vitals?addressId=1
{}
to https://api.medos.one
Use a dedicated test key, and put your browser's address on its allowlist

A Developer API key authenticates on its own, so it only works from the addresses registered against it — and this page calls from your browser, not your servers. Unless your own public address is on the list you get a 403 naming it, which is the allowlist doing its job. Your browser may also reach us over IPv6 even when your server does not, so the address in the error is often not the one you expected. The key here is kept in memory only and never written to storage, but create a test key for it and deactivate that key when you are done.

Request

curl -s -X POST "https://api.medos.one/v1/patients/1/vitals?addressId=1" \
  -H "x-api-key: $MEDOS_API_KEY" \
  -H "X-Acting-User-Id: 4821"

Common failures

StatusCause
400 naming x-acting-user-idA write without the acting-user header.
403 with requiredFeatureNot entitled to this operation.
403 "only available to Developer API keys"A widget session token was used. Send x-api-key.
403 "not an active member"The acting user is not in your workspace, or is deactivated.

On this page