Submit Verification from URL
POST/b2b/verifications/:user/url
Submit a verification for a user with documents provided via presigned URLs.
Instead of uploading files directly via multipart form data, this endpoint accepts presigned URLs pointing to your document files. The server will download the files from the provided URLs and process them. The filename will be extracted from each URL path.
This is useful when your documents are already stored in a cloud storage provider (e.g. AWS S3, Google Cloud Storage) and you want to avoid re-uploading them.
A verification is defined as a check that has been performed on a user to verify information provided by the user. This is typically done by a third party, such as a company that specializes in identity verification.
Checks are most commonly performed on documents provided by the user, such as a passport or driver's license, but can also include other types of checks such as a sanctions check or a Politically Exposed Person (PEP) check.
Domain allowlisting
For security, the domains you use for presigned URLs must be allowlisted before you can use this endpoint. Contact your account manager to configure the allowed domains for your integration.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 408
- 409
- 429
- 500
- 503
Response
Bad Request — the request was malformed or contained invalid parameters. Not retryable.
Unauthorized — authentication failed or credentials are missing/invalid. Not retryable.
Forbidden — the authenticated user does not have permission to perform this action. Not retryable.
Not Found — the requested resource does not exist. Not retryable.
Request Timeout — the request took too long to process. Retryable.
Conflict — the request conflicts with the current state of the resource. Retryable in some cases (see error code).
Too Many Requests — rate limit exceeded. Retryable with backoff.
Internal Server Error — an unexpected error occurred. Generally retryable.
Service Unavailable — the service is temporarily unavailable. Retryable.