Start a credentialing-agent run for a practitioner
POST/agent/practitioners/:practitionerId/runs
Start a credentialing-agent run for a practitioner
Request
Responses
- 202
- 400
- 404
- 409
- 422
- 502
- 503
Accepted - agentOS's response, passed through unchanged; the run itself proceeds asynchronously
Bad Request - missing or blank tenant-id, or the request body is not a valid JSON object
Not Found - agentOS integration is off, this tenant is not enrolled for the credentialing agent, credentialingWorkflowId is missing/blank, credentialingWorkflowId does not belong to the caller's tenant, credentialingWorkflowId does not belong to the path practitionerId, or the practitioner id is unknown to agentOS
Conflict - agentOS's response, passed through unchanged (e.g. this practitioner already has a run in progress)
Unprocessable Entity - agentOS's response, passed through unchanged (e.g. an invalid state in statesToCredential)
Bad Gateway - a network/timeout failure reaching agentOS, or a genuine 5xx from agentOS itself
Service Unavailable - agentos_not_configured (no credential configured) or agentos_credential_unavailable (m2m mode: Auth0 unreachable and no still-valid cached token); api-layer never called agentOS