Skip to main content
A complete example of the GET /verifications/{user_id}/data response for a finished verification. It shows every journey step with the data and documents that step collected.
The steps shown, and the keys inside each step’s data object, depend on the journey configured for your integration. The field names below are illustrative, not a fixed contract. Read data dynamically and do not hardcode field names.
Example GET /verifications/{user_id}/data response

What is fixed

Regardless of journey, the response envelope is stable:
  • user_id, reference_id, and status on the response.
  • Each entry in steps carries key, title, required, status, and completed_at.
  • Each entry in a step’s documents carries document_id, tag, kind, filename, content_type, size_bytes, and uploaded_at.
Timestamps are in IST. Only the contents of each step’s data object vary between journeys; treat the envelope as the contract and the inner data keys as dynamic.

Document tags

A document’s tag (for example gst_certificate) names what the file is. The set of tags is defined by your journey, so match on tags defensively rather than assuming a fixed list.