---
title: "Create a verification request"
method: POST
path: "/v1/verification_requests"
tags: ["verificationRequests"]
---

# Create a verification request

`POST /v1/verification_requests`

Request verification of an unlisted organization. If the organization cannot be found through Chariot's search,
you can submit a verification request so that Chariot's compliance team can review and verify the organization.

## Request body

- object
  - `ein` string, required — The EIN of the organization to verify
  - `organization_name` string, required — The name of the organization as known to the grantmaker
  - `website` string — The organization's website URL
  - `recommended_mailing_address` VerificationRequestAddress, required — A mailing address for the organization being verified.
    - `line1` string, required — Street address line 1
    - `line2` string — Street address line 2 (suite, unit, etc.)
    - `city` string, required — City
    - `state` string, required — Two-letter US state code (e.g. "CA", "NY")
    - `zip_code` string, required — ZIP or postal code
  - `contact_email` string — Contact email for the nonprofit organization.

## Response `201`

The verification request was created

- VerificationRequest — A verification request allows grantmakers to request that Chariot's compliance team verify an unlisted organization, enabling disbursements to nonprofits not yet in Chariot's database.
  - `id` string, required — Unique identifier for the verification request
  - `ein` string, required — The EIN of the organization being verified
  - `organization_name` string, required — The name of the organization as provided by the grantmaker
  - `organization_id` string, required — The ID of the Organization record for the nonprofit being verified.
  - `status` 'needs_review' | 'verified' | 'failed', required — The status of the verification request. Possible values include: - `needs_review`: The request has been submitted and is awaiting review by Chariot's compliance team - `verified`: The organization has been verified as tax-exempt and eligible for disbursements - `failed`: Chariot's compliance team determined the organization is not eligible
  - `website` string — The organization's website URL
  - `recommended_mailing_address` VerificationRequestAddress — A mailing address for the organization being verified.
    - `line1` string, required — Street address line 1
    - `line2` string — Street address line 2 (suite, unit, etc.)
    - `city` string, required — City
    - `state` string, required — Two-letter US state code (e.g. "CA", "NY")
    - `zip_code` string, required — ZIP or postal code
  - `verified_at` string, date-time — When the organization was verified as tax-exempt and eligible for disbursements
  - `failed_at` string, date-time — When the verification request was rejected
  - `created_at` string, date-time — When the verification request was created
  - `updated_at` string, date-time — When the verification request was last updated

## Other responses

- `400` — The request is invalid or contains invalid parameters
- `401` — Unauthorized. The request is missing the security (OAuth2 Bearer token) requirements and the server is unable to verify the identify of the caller.
- `403` — Access denied
- `409` — Resource Conflicts
- `412` — Precondition Failed

## Changes

- **2026-06-29** `b87f7738d336` — 10 breaking, 25 info
  - removed the required property `code` from the response with the `400` status
  - removed the required property `code` from the response with the `401` status
  - removed the required property `code` from the response with the `403` status
  - removed the required property `code` from the response with the `409` status
  - …31 more
- **2026-06-29** `c65f43c5ad90` — 5 warning
  - removed the optional property `details` from the response with the `400` status
  - removed the optional property `details` from the response with the `401` status
  - removed the optional property `details` from the response with the `403` status
  - removed the optional property `details` from the response with the `409` status
  - …1 more
- **2026-06-25** `f89b4f376e94` — 15 info
  - added the optional property `details/items/debug` to the response with the `400` status
  - added the optional property `details/items/debug` to the response with the `401` status
  - added the optional property `details/items/debug` to the response with the `403` status
  - added the optional property `details/items/debug` to the response with the `409` status
  - …11 more
- …earlier changes not shown

[Full history](https://skmtc.dev/chariot-giving/apis/specs/changes/v1/verification_requests/post.md)

---

[API](https://skmtc.dev/chariot-giving/apis/specs.md) · [All operations](https://skmtc.dev/chariot-giving/apis/specs/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/chariot-giving/specs/revisions/6f769ddf43bd/schema)