Look up a patient
Find one patient by exact document type and number. The match is exact: there is no partial or name search. found:false is an expected result, not an error — confirm the document type and the number with the caller and try again. Returns the patient's names, age, sex, city, entitlement status, and primaryIps: the primary-care IPS SURA has assigned to this person, read from the portal so the caller never has to know it. The health plan is never a question for the caller: the portal assigns the coverage itself and the appointment tools read it from the live form, so do not ask which plan or coverage to use and do not pass one anywhere.
- Scopes: any one of
sura:appointments:read,sura:appointments:write - Credentials: an API key, a client-credentials token or a person's access token
- Effect: read-only; safe to retry
- Limits: request body up to 32 KB, response up to 256 KB
- CLI:
arbol sura patients lookup· MCP tool:sura_patients_lookup
POST
https://api.getarbol.com/v1/sura/patients/lookupAuthorization
Request body JSON required
Returns
200
Successful operation.
400
INVALID_INPUT: The request does not match the published schema.
401
UNAUTHORIZED: A valid access token is required.
403
FORBIDDEN: The token does not authorize this operation.
404
CONNECTION_NOT_FOUND: The organization has no such connection.
409
PORTAL_SESSION_CONFLICT: The organization's connection to this integration couldn't complete the request. Don't retry it automatically; if it keeps happening, contact your Arbol team.CONNECTION_NOT_CONFIGURED: The organization has no SURA connection that can run this operation.
413
REQUEST_TOO_LARGE: The request exceeds the allowed size.
415
UNSUPPORTED_MEDIA_TYPE: The request content type is not supported.
429
RATE_LIMITED: The request rate limit was exceeded. Try again later.
500
INTERNAL_ERROR: The service could not complete the operation.
502
OUTCOME_UNKNOWN: The operation may have been applied; check its result before repeating it.PORTAL_CREDENTIALS_REJECTED: The organization's connection to this integration couldn't complete the request. Don't retry it automatically; if it keeps happening, contact your Arbol team.PORTAL_UNAVAILABLE: The organization's connection to this integration couldn't complete the request. Don't retry it automatically; if it keeps happening, contact your Arbol team.