API reference

Every route of this service, what each takes and what it answers, read from its own /openapi.json. Each operation has a Try it out that sends the request to this service from your browser and shows the answer.

The /v1 routes need an API key for this service: press Authorize and enter it as apiKey. It stays in this page's memory, is not stored by the browser, and is sent only to this service. Without one the reference still reads in full, and a /v1 call answers 401. A key for VerySafe's sandbox comes from VerySafe; a key for an installation of your own, from whoever runs it.

A verification is answered by a wallet, not by this page: start one with flow: cross_device, turn the authorizationRequestUri it returns into a QR code, scan it with a wallet within five minutes of the start (REQUEST_URI_VALIDITY_SECONDS, 300 by default; after that the wallet reports an unreadable request), and read the result with GET /v1/verifications/{id}. A real integration keeps its key on its server, never in a page.

Swagger UI 5.34.1 (Apache License 2.0), served from this origin. This page loads nothing from anywhere else and sends your requests only to this service.