In the eIDAS VideoID workflow, the user completes video identification on the Uanataca platform (link sent by email). The request is created in VIDEOPENDING; when the user finishes video ID, the status moves to VIDEOREVIEW. A Uanataca Certified Operator validates the evidence. For Natural Person profiles the request can be approved in this step; for other profiles the request may move to CREATED and require an update and document upload before approval. After approval, status becomes ENROLLREADY and the user receives the link to complete certificate issuance.
Implementing a webhook is recommended so your application is notified when the status changes (e.g. VIDEOPENDING → VIDEOREVIEW). See Webhook configuration.
Get first unused scratchcard — Same as classic workflow.
Create request — Create Request with
videoid_mode: 1, profile,scratchcard,registration_authority,email,mobile_phone_number. Request is in VIDEOPENDING.Video identification — Performed by the end user on the Uanataca platform (link from email). Evidences (name, surname, ID data) are obtained. On completion, status becomes VIDEOREVIEW (or VIDEOINCOMPLETE/VIDEOERROR if failed).
Validation — A Uanataca Certified Operator validates the evidence. For Natural Person profiles the request may be approved here (ENROLLREADY). For other profiles it moves to CREATED.
Update request (optional) — For non–Natural Person profiles, use Update Request to complete fields not obtained from video ID. Fields from video identification cannot be modified.
Upload documents (optional) — For non–Natural Person profiles, use Upload VideoID evidence to upload required documents.
Approve request — Same as classic: generate RAO declaration, generate contract, Approve request. Status becomes ENROLLREADY; user receives the pre-auth link.
- Workflows overview
- External VideoID — When you upload evidence and video via API
- Webhooks
- API reference (OpenAPI)