> ## Documentation Index > Fetch the complete documentation index at: https://docs.urtentic.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Verification Status > Retrieves the current status of a verification process. This endpoint allows you to check the progress and results of an ongoing or completed verification. ### Use Cases - Polling for verification completion - Checking verification results - Determining if additional inputs are needed - Retrieving verification outcome details ### Notes - This endpoint requires an API key with verification read permissions - Status updates may take time to process depending on the verification type - For real-time updates, configure webhooks instead of polling this endpoint ## OpenAPI ````yaml /api-reference/openapi.yml get /verifications/{verificationId}/status openapi: 3.0.0 info: title: Urtentic API version: '1.0' description: > # Introduction The Urtentic API provides comprehensive identity verification and workflow management capabilities. It enables organizations to create customized verification workflows, perform identity checks, and manage verification processes with features including liveness detection, location intelligence, and document verification. ## Authentication All authenticated endpoints require two headers: - `Authorization: Bearer {API_KEY}` - Your API key - `X-CLIENT-ID: {CLIENT_ID}` - Your client ID API credentials can be generated from your Urtentic Dashboard under Settings > API Keys. ## Webhook Notifications Configure webhook URLs in your Urtentic Dashboard to receive real-time notifications about verification status changes. Webhooks include the verification ID and current status, allowing your system to react to verification completions or failures. ## Key Features - User and organization management - Customizable verification workflows - Multiple verification processes (Liveness, Location, Document, Watchlist Check, Email) - Analytics and reporting - Webhook notifications for verification results contact: name: Urtentic Support Team email: support@urtentic.com url: https://urtentic.com/support termsOfService: https://urtentic.com/terms license: name: Urtentic License url: https://urtentic.com/license servers: - url: https://api.urtentic.com/api/v1 description: Urtentic API security: [] tags: - name: Identity description: > Management of verified identity data, including retrieval and validation of identity information. Endpoints in this category allow you to: - Retrieve verified identity details - Check identity verification status - Update identity information - Link identities across verification sessions - name: Processes description: > Configuration and management of individual verification process types that can be used in workflows. The Urtentic platform supports these verification processes: - **Document Verification**: OCR and authenticity checks for identity documents - **Liveness Detection**: Confirms a person is physically present and not using photos/videos - **Location Intelligence**: Verifies geographic location and environments - **Email Verification**: Validates email ownership through OTP - **Watchlist Check**: Screens identities against compliance databases - name: Verification description: > Core verification operations including starting verifications, submitting verification data, and retrieving results. Key operations include: - Starting new verification sessions - Submitting identity data for verification - Retrieving verification results - Validating inputs before submission - Tracking verification status - name: Webhook description: > Configuration and management of webhook endpoints for receiving real-time event notifications. The webhook system allows you to: - Receive real-time notifications about verification status changes - Configure multiple webhook endpoints for different environments - Specify which events trigger notifications - Verify webhook signature to ensure authenticity - Track webhook delivery and retry failed deliveries - name: Workflow description: > Creation and management of verification workflows, combining multiple verification processes into customized sequences. Workflows allow you to: - Define multi-step verification sequences - Configure country-specific document requirements - Set custom verification rules and thresholds - Create specialized flows for different use cases - Manage verification process order and dependencies paths: /verifications/{verificationId}/status: parameters: - name: verificationId in: path required: true schema: type: string format: uuid description: | Unique identifier of the verification. example: 85c94e71-6e3f-4a19-b15c-781d8a876542 get: tags: - Verification summary: Get Verification Status description: > Retrieves the current status of a verification process. This endpoint allows you to check the progress and results of an ongoing or completed verification. ### Use Cases - Polling for verification completion - Checking verification results - Determining if additional inputs are needed - Retrieving verification outcome details ### Notes - This endpoint requires an API key with verification read permissions - Status updates may take time to process depending on the verification type - For real-time updates, configure webhooks instead of polling this endpoint operationId: get-verification-status responses: '200': description: Verification status information content: application/json: schema: type: object properties: verificationId: type: string format: uuid description: Unique identifier for the verification example: 85c94e71-6e3f-4a19-b15c-781d8a876542 status: type: string description: > Current status of the verification: - PENDING: Verification has been created but not started - INITIATED: Verification has started but inputs are pending - PROCESSING: Inputs received and verification is in progress - COMPLETED: Verification completed successfully - FAILED: Verification failed - ABANDONED: Verification was abandoned by the user - EXPIRED: Verification session expired example: COMPLETED result: type: string description: | Result of the verification (if completed): - APPROVED: Verification passed all checks - DECLINED: Verification failed one or more checks - MANUAL_REVIEW: Verification requires manual review example: APPROVED completedAt: type: string format: date-time description: When the verification was completed example: '2023-06-15T15:30:00Z' steps: type: array description: Status of individual verification steps items: type: object properties: processType: type: string example: DOCUMENT_VERIFICATION status: type: string example: COMPLETED result: type: string example: APPROVED completedAt: type: string format: date-time example: '2023-06-15T15:25:00Z' missingInputs: type: array description: List of inputs that are still required items: type: string example: [] examples: completed_verification: value: verificationId: 85c94e71-6e3f-4a19-b15c-781d8a876542 status: COMPLETED result: APPROVED completedAt: '2023-06-15T15:30:00Z' steps: - processType: DOCUMENT_VERIFICATION status: COMPLETED result: APPROVED completedAt: '2023-06-15T15:25:00Z' - processType: LIVENESS status: COMPLETED result: APPROVED completedAt: '2023-06-15T15:28:00Z' missingInputs: [] pending_verification: value: verificationId: 85c94e71-6e3f-4a19-b15c-781d8a876542 status: INITIATED result: 'null' completedAt: '2023-06-15T15:30:00Z' steps: - processType: DOCUMENT_VERIFICATION status: PENDING result: 'null' completedAt: '2023-06-15T15:30:00Z' missingInputs: - FRONT_IMAGE - BACK_IMAGE '404': description: Verification not found content: application/json: schema: type: object properties: error: type: string message: type: string examples: verification_not_found: value: error: VERIFICATION_NOT_FOUND message: The specified verification ID was not found security: - apiKeyAuth: [] components: {} ````