---
Source: https://docs.microblink.com/verify/quick-start-cloud
Title: Quick start (cloud)
Description: Quick start guide to using the BlinkID Verify cloud API
---

# Quick start (cloud)

This guide walks through sending document images to the Verify cloud API and getting a verification response.

:::note

This guide covers the cloud API.
If you're running Verify on your own infrastructure, see the [on-prem quick start](/on-prem/quick-start) instead.

:::

## Get your credentials

To use the cloud API, you need your client ID and client secret.

1. [Sign up at the developer hub](https://developer.microblink.com/).
2. Contact [sales](mailto:sales@microblink.com).
3. Your credentials will be made available under the "API keys" section in the developer hub.

## Make a request

The verification endpoint format is:

```
https://{region}.verify.microblink.com/api/v3/verify
```

:::tip[Find your region]

Find your region [here](./api.md#regions).

:::

The API uses multipart requests, for both uploading images and sending the configuration.

<ApiSample
  method="POST"
  url="https://us-east.verify.microblink.com/api/v3/verify"
  headers={{ Authorization: "Basic <credentials>" }}
  formData={[
    { name: "imageFirstSide", fileName: "front_id.jpg" },
    { name: "imageSecondSide", fileName: "back_id.png" },
    {
      name: "consent",
      value: {
        userId: "<your-id-for-the-end-user>",
        durationDays: 365,
      },
    },
  ]}
/>

Use Basic Authentication with your client ID and client secret.
The format is `Basic {base64(clientId:clientSecret)}`.

Every cloud request must carry a `consent` part.
See [Get your users' consent](./consent.md) for what it contains and why it's required.

<details>

  <summary>Images you can use for testing</summary>

  ![Test ID - front](/verify/img/non_identity_front.png)
  ![Test ID - back](/verify/img/non_identity_back.png)

</details>

To customize the request, see [Configuration](./configuration.md).

## Understand the response

The API responds with a JSON object containing the verification and extraction results.
Here's a trimmed example:

```json
{
  "verification": {
    "verdict": "Accept", // "Accept" if genuine, "Reject" if fraud
    "failedChecks": [], // failed checks at a glance
    "checks": {} // detailed info on all checks performed
  },
  "pipeline": {}, // per-stage status
  "imageAssessment": {}, // image quality, cropping, hand presence
  "extraction": {}, // extracted data from the document
  "images": {}, // cropped document, face, and signature images
  "messages": [], // error codes and similar
  "configurationUsed": {}, // what configuration was used
  "runtime": {} // trace ID and other statistics
}
```

The full response schema is available in the [API reference](/verify/api/ref/v3-cloud).


Last updated on Aug 6, 2026