API Integration
How customers connect their applications to Identity for verification session creation, status checks, and operational workflows.
Section
What the API should handle
- create verification sessions
- fetch session and customer trust status
- retrieve operator-safe summaries
- support hosted-flow launch or embedded flow handoff
Section
Recommended implementation pattern
- Create a verification session from your backend.
- Pass your own customer or business reference into the request.
- Launch the user into the Remllo-powered verification flow or guide your own client UI using the API.
- Consume webhooks so your platform updates customer state without polling.
Product boundary
Let the customer’s product own activation or approval in their core application. Identity should provide the trust decision and supporting evidence summary, not assume control of the customer’s business workflow.
Next UpWebhooks and Delivery
Continue Through The DocsIdentity Documentation