List all allergies

GET/healthcare/{connection_id}/allergy

Parameters

limitnumber default=100
offsetnumber default=0
updated_gtedate-time
Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
sort enum
order enum
querystring
Query string to search. eg. email address or name
patient_idstring
The patient ID to filter by
fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection

Returns

idstring
Unique identifier for the allergy/intolerance
created_atdate-time
When the allergy record was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
When the allergy record was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
patient_idstring
The patient who has the allergy
encounter_idstring
The encounter in which the allergy was recorded
practitioner_idstring
The practitioner who recorded or asserted the allergy
namestring
Human-readable name of the substance
codes array
Codings for the substance (e.g. RxNorm, SNOMED CT)
status enum
Valid values:
"ACTIVE"
"INACTIVE"
"RESOLVED"
"OTHER"
Clinical status of the allergy
type enum
Valid values:
"FOOD"
"MEDICATION"
"ENVIRONMENT"
"BIOLOGIC"
"OTHER"
Category of the substance
criticality enum
Valid values:
"LOW"
"HIGH"
"UNABLE_TO_ASSESS"
"OTHER"
Potential severity of future reactions
reactions array
Codings for observed reaction manifestations (e.g. hives, anaphylaxis)
onset_atdate-time
When the allergy was first identified (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
recorded_atdate-time
When the allergy was recorded (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
notesstring
Free-text notes about the allergy
metadata array

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'GET',
  url: 'https://api.unified.to/healthcare/5de520f96e439b002043d8dc/allergy',
  headers: {
    authorization: 'bearer .....'
  },
  params: {
    limit: 50,
    offset: 0,
    updated_gte: '2026-10-12T03:24:38.891Z',
    sort: 'updated_at',
    order: 'asc',
    query: '',
    patient_id: '',
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?