verificationRequests

Create a verification request

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.

post/v1/verification_requests

Request body

einstring required

The EIN of the organization to verify

organization_namestring required

The name of the organization as known to the grantmaker

websitestring

The organization's website URL

contact_emailstring

Contact email for the nonprofit organization.

Example request

{
  "ein": "123456789",
  "organization_name": "Local Community Foundation",
  "website": "https://localfoundation.org",
  "recommended_mailing_address": {
    "line1": "123 Main St",
    "line2": "Suite 100",
    "city": "San Francisco",
    "state": "CA",
    "zip_code": "94105"
  },
  "contact_email": "contact@localfoundation.org"
}

Response

The verification request was created

idstring required

Unique identifier for the verification request

einstring required

The EIN of the organization being verified

organization_namestring required

The name of the organization as provided by the grantmaker

organization_idstring 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

websitestring

The organization's website URL

verified_atstring date-time

When the organization was verified as tax-exempt and eligible for disbursements

failed_atstring date-time

When the verification request was rejected

created_atstring date-time

When the verification request was created

updated_atstring date-time

When the verification request was last updated

Example response

{
  "id": "vr_01jpjen1s23s29kkmnjsb6fzga",
  "ein": "123456789",
  "organization_name": "Local Community Foundation",
  "organization_id": "org_01jpjenf5q6cawy43yxfcrxhct",
  "status": "needs_review",
  "website": "https://localfoundation.org",
  "recommended_mailing_address": {
    "line1": "123 Main St",
    "line2": "Suite 100",
    "city": "San Francisco",
    "state": "CA",
    "zip_code": "94105"
  },
  "created_at": "2020-01-31T23:00:00Z",
  "updated_at": "2020-01-31T23:00:00Z"
}

Changes

Changed in 4 of the 41 revisions of this API.25545

Jun 29, 2026b87f7738d3361025See the full diff
- ▲
  removed the required property code from the response with the 400 status
  response-required-property-removed
- ▲
  removed the required property code from the response with the 401 status
  response-required-property-removed
- ▲
  removed the required property code from the response with the 403 status
  response-required-property-removed
- ▲
  removed the required property code from the response with the 409 status
  response-required-property-removed
- ▲
  removed the required property code from the response with the 412 status
  response-required-property-removed
- ▲
  removed the required property message from the response with the 400 status
  response-required-property-removed
- ▲
  removed the required property message from the response with the 401 status
  response-required-property-removed
- ▲
  removed the required property message from the response with the 403 status
  response-required-property-removed
- ▲
  removed the required property message from the response with the 409 status
  response-required-property-removed
- ▲
  removed the required property message from the response with the 412 status
  response-required-property-removed
- ○
  media type application/json was changed to a more specific media type application/problem+json for the response status 400
  response-media-type-name-specialized
- ○
  media type application/json was changed to a more specific media type application/problem+json for the response status 401
  response-media-type-name-specialized
- ○
  media type application/json was changed to a more specific media type application/problem+json for the response status 403
  response-media-type-name-specialized
- ○
  media type application/json was changed to a more specific media type application/problem+json for the response status 409
  response-media-type-name-specialized
- ○
  media type application/json was changed to a more specific media type application/problem+json for the response status 412
  response-media-type-name-specialized
- ○
  added the required property detail to the response with the 400 status
  response-required-property-added
- ○
  added the required property detail to the response with the 401 status
  response-required-property-added
- ○
  added the required property detail to the response with the 403 status
  response-required-property-added
- ○
  added the required property detail to the response with the 409 status
  response-required-property-added
- ○
  added the required property detail to the response with the 412 status
  response-required-property-added
- ○
  added the required property status to the response with the 400 status
  response-required-property-added
- ○
  added the required property status to the response with the 401 status
  response-required-property-added
- ○
  added the required property status to the response with the 403 status
  response-required-property-added
- ○
  added the required property status to the response with the 409 status
  response-required-property-added
- ○
  added the required property status to the response with the 412 status
  response-required-property-added
- ○
  added the required property title to the response with the 400 status
  response-required-property-added
- ○
  added the required property title to the response with the 401 status
  response-required-property-added
- ○
  added the required property title to the response with the 403 status
  response-required-property-added
- ○
  added the required property title to the response with the 409 status
  response-required-property-added
- ○
  added the required property title to the response with the 412 status
  response-required-property-added
- ○
  added the required property type to the response with the 400 status
  response-required-property-added
- ○
  added the required property type to the response with the 401 status
  response-required-property-added
- ○
  added the required property type to the response with the 403 status
  response-required-property-added
- ○
  added the required property type to the response with the 409 status
  response-required-property-added
- ○
  added the required property type to the response with the 412 status
  response-required-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jun 29, 2026c65f43c5ad905See the full diff
- ●
  removed the optional property details from the response with the 400 status
  response-optional-property-removed
- ●
  removed the optional property details from the response with the 401 status
  response-optional-property-removed
- ●
  removed the optional property details from the response with the 403 status
  response-optional-property-removed
- ●
  removed the optional property details from the response with the 409 status
  response-optional-property-removed
- ●
  removed the optional property details from the response with the 412 status
  response-optional-property-removed
Jun 25, 2026f89b4f376e9415See the full diff
- ○
  added the optional property details/items/debug to the response with the 400 status
  response-optional-property-added
- ○
  added the optional property details/items/debug to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property details/items/debug to the response with the 403 status
  response-optional-property-added
- ○
  added the optional property details/items/debug to the response with the 409 status
  response-optional-property-added
- ○
  added the optional property details/items/debug to the response with the 412 status
  response-optional-property-added
- ○
  added the optional property details/items/type to the response with the 400 status
  response-optional-property-added
- ○
  added the optional property details/items/type to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property details/items/type to the response with the 403 status
  response-optional-property-added
- ○
  added the optional property details/items/type to the response with the 409 status
  response-optional-property-added
- ○
  added the optional property details/items/type to the response with the 412 status
  response-optional-property-added
- ○
  added the optional property details/items/value to the response with the 400 status
  response-optional-property-added
- ○
  added the optional property details/items/value to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property details/items/value to the response with the 403 status
  response-optional-property-added
- ○
  added the optional property details/items/value to the response with the 409 status
  response-optional-property-added
- ○
  added the optional property details/items/value to the response with the 412 status
  response-optional-property-added
Jun 25, 202690671617b825155See the full diff
- ▲
  the code response's property type/format changed from number/ to string/ for status 400
  response-property-type-changed
- ▲
  the code response's property type/format changed from number/ to string/ for status 401
  response-property-type-changed
- ▲
  the code response's property type/format changed from number/ to string/ for status 403
  response-property-type-changed
- ▲
  the code response's property type/format changed from number/ to string/ for status 409
  response-property-type-changed
- ▲
  the code response's property type/format changed from number/ to string/ for status 412
  response-property-type-changed
- ▲
  removed the required property error from the response with the 400 status
  response-required-property-removed
- ▲
  removed the required property error from the response with the 401 status
  response-required-property-removed
- ▲
  removed the required property error from the response with the 403 status
  response-required-property-removed
- ▲
  removed the required property error from the response with the 409 status
  response-required-property-removed
- ▲
  removed the required property error from the response with the 412 status
  response-required-property-removed
- ▲
  removed the required property timestamp from the response with the 400 status
  response-required-property-removed
- ▲
  removed the required property timestamp from the response with the 401 status
  response-required-property-removed
- ▲
  removed the required property timestamp from the response with the 403 status
  response-required-property-removed
- ▲
  removed the required property timestamp from the response with the 409 status
  response-required-property-removed
- ▲
  removed the required property timestamp from the response with the 412 status
  response-required-property-removed
- ○
  added the optional property details to the response with the 400 status
  response-optional-property-added
- ○
  added the optional property details to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property details to the response with the 403 status
  response-optional-property-added
- ○
  added the optional property details to the response with the 409 status
  response-optional-property-added
- ○
  added the optional property details to the response with the 412 status
  response-optional-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history