Get an operation
Get the result of an earlier call that answered status "pending", by its operationId. SURA's portal does one thing at a time per account, so a call may wait its turn; it keeps running even if you stop waiting. Call this after retryAfterSeconds. It waits briefly and answers pending again while the operation is still running. Repeating the original call with the same arguments also returns the same operation.
- Scopes: any one of
sura:appointments:read,sura:appointments:write,sura:affiliations:read - Credentials: an API key, a client-credentials token or a person's access token
- Effect: read-only; safe to retry
- Limits: response up to 256 KB
- CLI:
arbol sura operations get· MCP tool:sura_operations_get
GET
https://api.getarbol.com/v1/sura/operations/{operationId}Authorization
Path parameters
Query parameters
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.
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.