Direct service calls
Call one verification service and orchestrate the rest yourself.
Where a hosted journey is more than you need, you can call a single service: extract a document, match a face, screen a name. You supply the inputs and handle the outcome.
curl https://api.example.com/api/v1/integration/services \
-H "X-API-Key: pmt_live_..."GET /services lists what you may call, which is your institution's plan intersected with your credential's scopes — so it is exactly what will work. Each entry declares its input and output keys; use those names.
Reading the outcome
| Status | Means |
|---|---|
| 200 | The call completed. Read outcome and outputs. |
| 422 | The provider answered and refused your request. Your input, usually. |
| 502 | The provider failed. Retry is reasonable. |
| 504 | The provider did not answer in time. Retry is reasonable. |
A provider refusing your request is reported as a refusal rather than as a platform failure, so you can tell your own bad input from our bad day.
In sandbox
No provider is contacted. The response carries one value per declared output, built from the service's own declaration, so the shape matches production exactly. The values are obviously synthetic and must never be treated as a real answer.