Submit Verification from 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.

POST /b2b/verifications/{user}/url

Submit Verification from URL

cURL

curl --request POST \
  --url https://nexus.kraken.com/b2b/verifications/{user}/url \
  --header 'API-Key: <api-key>' \
  --header 'API-Sign: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "identity_document",
  "metadata": {
    "identity": {
      "full_name": {
        "first_name": "<string>",
        "last_name": "<string>",
        "middle_name": "<string>"
      },
      "date_of_birth": "2023-03-13"
    },
    "document_type": "passport",
    "document_number": "<string>",
    "issuing_country": "AD",
    "verifier": "<string>",
    "verified_at": "2023-03-13T12:34:56Z",
    "nationality": "AD",
    "verifier_response": "<unknown>",
    "external_verification_id": "<string>",
    "expiration_date": "2023-03-13"
  },
  "front_url": "<string>",
  "back_url": "<string>",
  "verifier_response_url": "<string>"
}
'

200

{
  "result": {
    "verification_id": "<string>"
  }
}

Authorizations

API-Key · string · header · required

The "API-Key" header should contain your API key.

API-Sign · string · header · required

Authenticated requests should be signed with the "API-Sign" header, using a signature generated with your private key, nonce, encoded payload, and URI path.

Headers

Payward-Version · enum<string> · default: 2025-04-15

The target version of the Embed API to use. The API version name is based on the date when the API version was released. For example, the API version 2025-04-15 was released on April 15, 2025.

Available options: 2025-04-15

Path Parameters

user · string · required

Internet International Bank Account Number (IIBAN)

Required string length: 14 - 42

Body

application/json

Option 1

Option 2

Option 3

type · enum<string> · required

Available options: identity_document

metadata · object · required

Metadata about the verification.

Show child attributes

front_url · string · required

Presigned URL to the front side of the identity document. The filename will be extracted from the URL path.

back_url · string | null

Presigned URL to the back side of the identity document (optional). The filename will be extracted from the URL path.

verifier_response_url · string | null

Presigned URL to the verifier response document (optional). The filename will be extracted from the URL path.

Response

200

application/json

Response

result · object

Show child attributes