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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
CLEAR

CLEAR Verification Sessions API

The Verification Sessions API from CLEAR — 4 operation(s) for verification sessions.

Documentation Provider Profile APIs.io OpenAPI GitHub

CLEAR Verification Sessions API is published by CLEAR on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Verification Sessions. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 6 operations across 4 paths, and defines 49 schemas. It is described by OpenAPI 3.2.0, at version 1.1.

Requests are made against a single base URL, https://verified.clearme.com/v1.

6 operations 4 paths 49 schemas 3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1
Base URL
https://verified.clearme.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

CLEAR Verification Sessions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Authorization_Bearer). By default, every request must be authenticated.

Paths & Operations 6

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

Verification Sessions 6
POST
/verification_sessions
Create Verification Session
create_verification_session body → 200400401412429500
GET
/verification_sessionsdeprecated
List Verification Sessions
list_verifications 5 params → 200400401412429500
POST
/verification_sessions/{id}/custom_fields
Add Custom Fields to Verification Session
add_custom_fields_verification_vendor_backend 1 param body → 200400401412429500
GET
/verification_sessions/{id}
Get Verification Session
get_verification 2 params → 200400401412429500
PUT
/verification_sessions/{id}
Submit User Profile Information for Verification Session
update_verification_session 1 param body → 200400401412429500
GET
/verification_sessions/search
Search Verification Sessions with Advanced Filters
search_verification_sessions 14 params → 200400401412429500

Schemas 49

The contract defines 49 schemas that model the data the API accepts and returns. The most detailed are VerificationSessionOut (28 properties), TraitsOut (20 properties), WatchlistHitDetails (16 properties), HistoricalAddressOut (14 properties). Each schema is shown below with its type and property counts.

DocumentOut
object
Verified document object returned to the vendor.
14 properties
ErrorType400
string
VerificationSessionOut
object
We return data in the following schema for our Verification Session routes.
28 properties
NameMatchingModel
object
Parameters for creating a name for matching
3 properties
LocationInfo
object
Information about where a request came from parsed from its IP or other request-level information.
7 properties
VerificationUpdateOptions
object
1 property
KeysetPaginatedVerificationSessionsOut
object
3 properties
VerificationSessionStatus
string
The statuses that a a verification session can be in.
WatchlistHitDetails
object
Details about the watchlist hit person
16 properties
VerificationSessionsOut
object
2 properties
VerificationSearchSortField
string
HealthInsuranceOut
object
Verified health insurance object returned to the vendor.
8 properties
FieldErrors
object
3 properties 3 required
SoraExternalCheckExport
object
7 properties 1 required
AddressMatchingModel
object
Parameters for creating an address for matching
6 properties
HistoricalNameOut
object
10 properties
ErrorType401
string
VerificationOptions
object
Options for verification session creation.
8 properties
APIError400Out
object
3 properties
HistoricalAddressOut
object
14 properties
AddressOut
object
Verified address object returned to the vendor.
6 properties
WatchlistHit
object
4 properties 3 required
NameMatchingModelV2
object
Parameters for creating a name for matching, excluding middle name.
2 properties
SessionInfoOut
object
Information gathered from the user's frontend session.
6 properties
APIError412Out
object
3 properties
APIError429Out
object
3 properties
WatchlistSource
object
Information regarding the source of the watchlist hit
3 properties 3 required
TraitsOut
object
Information collected from the user returned to the vendor.
20 properties
APIError401Out
object
3 properties
UserProfileMatchingRequestDetailsV2
object
User profile matching details for verification session.
5 properties
SortByOptions
string
CustomFieldsIn
object
1 property 1 required
VerificationStatus
string
The statuses that a verification can be in.
WatchlistHits
object
2 properties 1 required
ErrorType412
string
VerificationSearchSortDirection
string
WatchlistHitEntityType
string
WatchlistDate
object
3 properties 1 required
VerifiedEmailOut
object
Verified email object returned to the vendor.
3 properties
WatchlistHitTypes
string
Types of watchlist hits.
PaginationLinks
object
Links to other response pages for paginated responses
6 properties
SoraDocumentTypeEnum
string
APIError500Out
object
3 properties
ErrorType500
string
ErrorType429
string
UserProfileMatchingResponseDetailsV2
object
Response object for user profile matching in verification sessions.
5 properties
HistoricalDataOut
object
2 properties
SoraExternalCheckAdditionalDetails
object
Additional details returned for some checks.
1 property
Date
object
A date object.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clear-verification-sessions-api-openapi.yml Raw ↑
#Verification Sessions
← Back to C APIs
API Details
ID
clear:clear-verification-sessions-api
Base URL
https://verified.clearme.com/v1
Docs
https://docs.clearme.com/reference/the-verification-sessions-api
Provider
CLEAR
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=clear-verification-sessions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/clear-verification-sessions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of CLEAR Verification Sessions 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.