How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Veryfi Checks API

The Checks API from Veryfi — 2 operation(s) for checks.

Veryfi Checks API is one of 14 APIs that Veryfi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checks. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 4 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version v8.

Requests are made against a single base URL, https://api.veryfi.com/api/v8.

4 operations 2 paths 3 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v8
Server
https://api.veryfi.com/api/v8
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Veryfi Checks API declares 3 security schemes for authenticating requests. An API key is passed in the header as CLIENT-ID (clientId). An API key is passed in the header as AUTHORIZATION (apiKey). An API key is passed in the header as X-Veryfi-Request-Signature (requestSignature). By default, every request must be authenticated.

  • clientId — Your Veryfi account client identifier
  • apiKey — API key in format: 'apikey USERNAME:APIKEY'
  • requestSignature — HMAC-SHA256 signature for request validation

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Checks 4
POST
/partner/checks
Process a Check
processCheck body → 201401
GET
/partner/checks
List All Checks
listChecks → 200401
GET
/partner/checks/{documentId}
Get a Check
getCheck 1 param → 200401404
DELETE
/partner/checks/{documentId}
Delete a Check
deleteCheck 1 param → 200401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ProcessDocumentRequest (13 properties), Check (9 properties), Error (3 properties). Each schema is shown below with its type and property counts.

Check
object
A processed check with extracted data
9 properties
Error
object
API error response
3 properties
ProcessDocumentRequest
object
Request body for document processing operations
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

veryfi-checks-api-openapi.yml Raw ↑

Other APIs Veryfi publishes across the network.

Veryfi Receipts & Invoices API
Veryfi Bank Statements API
Veryfi W-2 API
Veryfi W-9 API
Veryfi Checks API
Veryfi Any Documents API
Veryfi Classification API
Veryfi Any Documents API
Veryfi Bank Statements API
Veryfi Classification API
Veryfi Documents API
Veryfi W-2 Forms API
Where this information came from

This is an independent, third-party profile of Veryfi Checks API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.