Find availability
Find the free appointment times for one patient and one service. With no date it answers with the soonest day that has room; with a date it answers for that day. times[] are the hours you may book, otherDates[] are other days that month with room, and otherProfessionals[] are the other doctors who see this service. Offer two or three times, never the whole list.
- 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 availability lookup· MCP tool:sura_availability_lookup
POST
https://api.getarbol.com/v1/sura/availability/lookupAuthorization
Request body JSON required
- professionaloptionalstring | null
Doctor's name, or part of it, when the caller asked for someone specific. Use list_professionals to check the service's registered doctors independently of available slots; absence from an open-agenda selector does not mean the doctor does not exist. Omit it to see whoever has room soonest.
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.