Asynchronous acknowledgement
HTTP 202 returns a tracking job ID; it does not confirm completed evidence.
MOBILE-ID · TRUSTED LTANS
Asynchronous Jobs
Handle timeouts, dependency waits, retries and result references without duplicate commands.
Separate HTTP time from job lifetime
Interrupted connection
Query the existing job or reconcile its idempotency key before resubmitting.
States and actions
QUEUEDRUNNINGSUCCEEDEDExceptions: WAITING_EXTERNAL / RETRY_PENDING / FAILED / CANCELLED
| State | Meaning and next action |
|---|---|
| QUEUED | Accepted and waiting for execution resources. |
| RUNNING | Running; no terminal result yet. |
| WAITING_EXTERNAL | Waiting for storage, TSA or another dependency. |
| RETRY_PENDING | A bounded retry is scheduled. |
| SUCCEEDED | Read the result reference; success does not mean every evidence item is valid. |
| FAILED | Inspect Problem and reconcile the cause before issuing another command. |
| CANCELLED | Cancelled under the environment’s capabilities and permissions. |
Follow through to the result resource
GET /v1/jobs/job-test-001
{
"jobId": "job-test-001",
"state": "SUCCEEDED",
"resourceId": "ver-test-001",
"correlationId": "corr-test-001",
"resultReference": "/v1/verifications/ver-test-001"
}For verification, follow resultReference to the report; successful HTTP processing may still produce INDETERMINATE. Resolve references only against the configured API origin.
Controlled retries
- Honor
pollAfterSecondsand Retry-After when supplied; avoid busy polling. - Retain correlation context for reconciliation; never log tokens.
- Idempotency window, timeouts and retry counts are environment-defined, not default SLAs.
Job API
Follow queued, running, dependency-wait and final states; use resultReference without equating SUCCEEDED with VALID.
Error Catalog
Diagnose operation-specific failures, distinguish HTTP errors from verification outcomes and choose recovery actions.
Read integration guide →
Integration test plan
Success, duplicate, data-loss, TSA, webhook and handover tests with expected outcomes.
Read integration guide →Separate three state domains
| Domain | Example | Cannot infer |
|---|---|---|
Job | SUCCEEDED | Does not imply valid evidence. |
ArchiveObject | EVIDENCE_READY | Does not imply every independent assessment is VALID. |
VerificationReport | INDETERMINATE | Not automatically an HTTP failure or false data. |