The Arbol API is one host, https://api.getarbol.com, with several services: Arbol’s products (Raíz, Agenda, Account) and integrations with insurers, registries and clinical systems. Whatever the service, a call follows the same rules, which these pages describe.
How the API is laid out
- Paths. Each service’s operations live under
/v1/<service>/, such as/v1/account/organization. Take the method and path from the API reference: they don’t always mirror the operation’s name, and some reads usePOST. - Operation names. Every operation is named
<service>.<resource>.<verb>, such asaccount.organization.get. The API reference, the SDKs and the MCP tools are all named after it. - OpenAPI. The whole API is described at
https://api.getarbol.com/openapi.json, and each service athttps://api.getarbol.com/v1/<service>/openapi.json. Both are public.GET https://api.getarbol.com/lists them. - Credentials. Every call carries one credential in the
Authorizationheader. See Authentication.
The rules every call shares
Organizations
Every credential acts in one organization. Who may call, and with which permissions.
Responses and errors
The response envelope, error codes, request ids and size limits.
Pagination
How list operations return a page at a time, with cursors.
Retries
Which calls are safe to repeat, and how to handle a write whose outcome is unknown.
Versions and updates
What happens when the API changes, and when the SDK, the CLI, MCP and these docs update.