> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# GET /verifications/{verification_id}

**Get a verification**

Returns a verification using its ID.

The response includes the verification steps.

**Required permissions:** `verification.read`

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `verification_id` | string | required | Unique Paddle ID for this verification entity, prefixed with `slrvrf_`. (pattern: `^slrvrf_[a-z\d]{26}$`) |

## Response (200)

- `data`: object (required) — Represents a verification entity.
  - `id`: string (required) — Unique Paddle ID for this verification entity, prefixed with `slrvrf_`. (pattern: `^slrvrf_[a-z\d]{26}$`)
  - `status`: string (required) — Overall status of the verification, derived from the status of its steps. `pending` until the first step exists.
    - `pending` — Verification hasn't started, or is waiting for its next step to start.
    - `in_progress` — Paddle is running automated checks. No input is required.
    - `in_review` — Paddle is reviewing the information provided by the account holder.
    - `action_required` — Action is required before the verification can continue.
    - `completed` — Verification is complete. For an `onboarding` verification, the account is ready for live payments.
    - `failed` — Verification didn't complete.
  - `verification_type`: string (required) — Type of verification. An account has at most one `onboarding` verification.
    - `onboarding` — A verification created as part of account onboarding.
    - `domain` — A verification created for a domain review.
  - `created_at`: string (date-time) (required) — RFC 3339 datetime string of when this entity was created. Set automatically by Paddle.
  - `updated_at`: string (date-time) (required) — RFC 3339 datetime string of when this entity was updated. Set automatically by Paddle.
  - `steps`: array (required) — Verification steps that make up this verification.
    - `id`: string (required) — Unique Paddle ID for this verification step entity, prefixed with `slrvrfstp_`. (pattern: `^slrvrfstp_[a-z\d]{26}$`)
    - `key`: string (required) — Key of the verification step.
      - `account_setup` — The account holder submits the prerequisite account details.
      - `domain_review` — Paddle reviews the domain.
      - `business_identification` — Paddle validates the business. Public companies and sole traders don't need this step.
      - `identity_verification` — Paddle validates the stakeholders of the business. Public companies don't need this step.
      - `final_review` — Paddle performs a manual review of the business.
      - `automated_review` — Paddle submits the business to a third-party provider for automated review. Where an account has no completed domain verification yet, this step stays `pending` until one completes.
    - `status`: string (required) — Status of the verification step.

Steps are created as `pending` initially, then move through `in_progress` and `in_review` states as Paddle processes each step.
      - `pending` — This step hasn't started yet.
      - `in_progress` — Paddle is running automated checks for this step. No input is required.
      - `in_review` — Paddle is reviewing this step.
      - `action_required` — Action is required before this step can continue.
      - `failed` — This step didn't complete.
      - `completed` — This step is complete and no further action is required.
    - `expires_at`: string (date-time) | null (required) — RFC 3339 datetime string of when this step expires. `null` if this step never expires.
    - `created_at`: string (date-time) (required) — RFC 3339 datetime string of when this entity was created. Set automatically by Paddle.
    - `updated_at`: string (date-time) (required) — RFC 3339 datetime string of when this entity was updated. Set automatically by Paddle.
- `meta`: object (required) — Information about this response.
  - `request_id`: string (required) — Unique ID for the request relating to this response. Provide this when contacting Paddle support about a specific request.

### Response example

```json
{
  "data": {
    "id": "slrvrf_01jjr5d4c14h4y3lqlk9bedkw7",
    "verification_type": "onboarding",
    "status": "action_required",
    "steps": [
      {
        "id": "slrvrfstp_01jjr5d4c14h4y3lqlk9bedkw8",
        "key": "account_setup",
        "status": "completed",
        "expires_at": null,
        "created_at": "2025-03-10T10:30:00.00Z",
        "updated_at": "2025-03-10T10:30:00.00Z"
      },
      {
        "id": "slrvrfstp_01jjr5d4c14h4y3lqlk9bedkw9",
        "key": "automated_review",
        "status": "action_required",
        "expires_at": null,
        "created_at": "2025-03-10T10:30:00.00Z",
        "updated_at": "2025-03-10T10:30:00.00Z"
      }
    ],
    "created_at": "2025-03-10T10:30:00.00Z",
    "updated_at": "2025-03-10T10:30:00.00Z"
  },
  "meta": {
    "request_id": "80e30719-f099-52de-92c4-1d2b7b7247f3"
  }
}
```