MOBILE-ID · TRUSTED LTANS
Export / Transfer API
Create scoped export packages and inspect state and manifests before recipient delivery.
Orchestrating export and transfer
This page explains the business sequence; endpoint pages own detailed contracts. Each step retains its input revision and distinct result.
| Step | Contract / condition |
|---|---|
| Request export | POST /v1/archives/{archiveId}/exports → QUEUED Job; retain jobId, not a completed package. |
| Get result | GET /v1/jobs/{jobId}, then GET /v1/exports/{exportId} → ExportResult. |
| Download bytes | Use the provisioned channel; manifestReference alone proves neither download nor verification. |
| Initiate transfer | POST /v1/archives/{archiveId}/transfers with the correct exportId, destinationProfileId and approvalId. |
| Recipient acknowledges | POST /v1/transfers/{transferId}/acknowledgements with TransferAcknowledgement; check digest, recipient and scope. |
Stop-and-reconcile cases
Digest mismatch, unauthorized recipient, missing components or insufficient verification stop responsibility transfer. Retain the source, obtain material and retry under approval; lost responses alone do not justify a new transfer.