Get a paginated list of all verification requests with filtering, sorting, and search capabilities. Returns logs for the authenticated user's organization.
Authorization
ApiKeyAuth In: header
Query Parameters
Filter by verification channel code
Filter by end date (ISO format: 2025-12-31T23:59:59Z)
date-timePage number (default: 1)
Number of records per page (default: 50, max: 100)
Filter by request method (portal or api)
Filter by response code
Search in reference_id, searched_id, or transaction_id
Sort by field (created_at, amount_charged, gateway_response_time). Prefix with - for descending.
Filter by start date (ISO format: 2025-01-01T00:00:00Z)
date-timeFilter by status (pending, processing, success, failed, error)
Filter by charge status
Response Body
application/json
curl -X GET "https://example.com/api/v1/verification/logs/"{ "data": {}, "status": true, "message": "Request successful.", "errors": {}, "meta": { "timestamp": "2019-08-24T14:15:22Z", "version": "v1", "request_id": "string" }, "pagination": { "page": 0, "page_size": 0, "total_pages": 0, "total_items": 0 }}response_code values (e.g., 00 Success, 01 Not Found, 02 Unavailable).Join our developer Slack channel for real-time integration support, engineering updates, and direct Q&A with the Prembly team.
Join Slack ChannelCheck a verification's status GET
Returns the current state and result of a verification you submitted earlier. Use it to poll a verification that has not completed, and to retrieve the result afterwards. The identifier can be any of the references a submission hands back: - an SDK session id, like `sdk_session_6c8e3f94...` - a verification UUID, with hyphens or underscores - a reference id, like `ver_document_w_face_jba9xnk8r1` Not billed — checking a status does not re-run the verification, so poll as often as you need. Older integrations may call this on other paths, or by passing the identifier as a `session_id`, `verification_id` or `reference_id` query parameter instead of in the path. Those still work and are not documented; new integrations should use this path.
Submit async verification request POST
Submit a verification request for background processing. **Flow:** 1. Submit verification request 2. Receive verification_id immediately 3. Check status using GET /api/v1/verification/async/status/{verification_id}/ 4. Receive webhook notification when complete (if webhook_url configured) **Benefits:** - No waiting for gateway response - Can handle slow gateway responses - Higher throughput - Automatic retries on failure