Create session package
Use the organization gMedic account. No automatic write retries; reconcile an unknown outcome before repeating.
- Scope:
gmedic:sessions:write - Credentials: an API key, a client-credentials token or a person's access token
- Effect: writes; not idempotent: check the outcome before you retry
- Limits: request body up to 32 KB, response up to 256 KB
- CLI:
arbol gmedic session-packages create· MCP tool:gmedic_session_packages_create
POST
https://api.getarbol.com/v1/gmedic/session-packagesAuthorization
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: This organization has no gMedic connection with this id.RECORD_NOT_FOUND: gMedic has no record with one of the ids sent.
409
NOT_CONFIGURED: This organization has no verified gMedic connection.
413
REQUEST_TOO_LARGE: The request exceeds the allowed size.
415
UNSUPPORTED_MEDIA_TYPE: The request content type is not supported.
422
PROVIDER_INPUT_REJECTED: gMedic rejected the supplied fields.
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.PROVIDER_ACCESS_REJECTED: The configured gMedic account did not authorize this operation.PROVIDER_RESPONSE_INVALID: gMedic returned an unexpected response.
503
UPSTREAM_UNAVAILABLE: The upstream service could not complete the request.CATALOG_SEARCH_INCOMPLETE: The service catalog search could not be completed within its limits. Service absence cannot be concluded.PROVIDER_UNAVAILABLE: gMedic is temporarily unavailable.