Data

Identifiers

An identifier is a phone number or email address the user uses to verify for 1-Click Signup.

Identifiers are inputs: you pass them to us in API request bodies.

Name	Key	Type	Format	Description	Example
Phone	phone	string	E.164	Phone number a user uses to verify to 1-Click Signup	"+10123456789"
Email	email	string	email	Email address a user uses to verify to 1-Click Signup	"richard@piedpiper.net"

note

A phone number is required to source verified data (credentials and metadata) for a user. An email can't currently be used for this purpose on its own, but including it helps source better and more data — especially risk signals metadata.

Credentials

A credential is a piece of identity data about a user.

Credentials are outputs:** we return them to you in API response bodies.

Credential Formats

We support multiple formats for some credential types (see below). If you'd like to use formats different than the defaults, please reach out to us at Support@Verified.inc and we'll enable them for you.

KYC (Know Your Customer)

Coverage

We can source verified KYC type data for ~95% of US adults. Coverage for your user base may vary.

Name	Key	Type	Format(s)	Description	Example
Phone	phone	string	E.164	Phone number	"+10123456789"
Full Name	fullName	Default: Object string	Default: Object with keys for all child credentials listed below Any combination of child shortenedCredentialTypes under fullName, , (comma), and - (dash)	Full name	See 1ClickEntity example "Hendricks, Richard"
↳ First Name	fullName.firstName	string	Title Case	First name	"Richard"
↳ Middle Name	fullName.middleName	string	Title Case	Middle name	"Baudelaire"
↳ Last Name	fullName.lastName	string	Title Case	Last name	"Henricks"
Address	address	Default: Object string	Default: Object with keys for all child credentials listed below Any combination of child shortenedCredentialTypes under address, , (comma), and - (dash)	Address	See 1ClickEntity example "Palo Alto, US-CA"
↳ Line 1	address.line1	string	Title Case	Line 1 of address	"5320 Newell Rd"
↳ Line 2	address.line2	string	Title Case	Line 2 of address	""
↳ City	address.city	string	Title Case	City of address	"Palo Alto"
↳ State	address.state	string	Default: 2 letter abbreviation (last 2 characters of ISO 3166-2 code for US state/territory) Full state/territory name (ISO 3166-2 subdivision name)	State of address	"CA" "California"
↳ ZIP Code	address.zipCode	string	ZIP Code (5 digits, 0-9) or ZIP+4 (9 digits, 0-9, with a hypen after the first 5)	ZIP code of address	"94303" or "94303-3058"
↳ Country	address.country	string	Default: 2 letter abbreviation (ISO 3166-1 alpha-2 code, currently always "US") Full country name (ISO 3166-1 English short name, currently always "United States of America")	Country of address	"US"
Birth Date	birthDate	string	Default: Unix time (milliseconds) Any combination of y(year), M(month), d(day), /(slash), and -(dash)	Birth date	"617947200000" "08/01/1989"
SSN	ssn	string	9 digits (0-9)	Social Security Number	"123-45-6789"
Email Not Recommended	email	string	email	Email address	"richard@piedpiper.net"

Email Reliability

Email credentials can be less reliable compared to other types of data. Verifying them is challenging because many people use multiple email addresses, making it difficult to associate one email with a single individual. If email accuracy is critical, we recommend directly asking users for their email during your workflow to ensure reliability.

Credit Card

Add On

Name	Key	Type	Format(s)	Description	Example
Credit Card	creditCard	Object	Object with keys for all child credentials listed below	Credit card information	-
↳ Network	creditCard.network	string	Title Case	Network of credit card	"VISA"
↳ Issuing Bank	creditCard.issuingBank	string	Title Case	Issuing bank of credit card	"Bank of America"
↳ Cardholder Name	creditCard.cardholderName	string	Title Case	Cardholder name of credit card	"Richard Hendricks"
↳ PAN	creditCard.pan	string	16 digits (0-9)	Primary Account Number of credit card	"1234123412341234"
↳ Expiration Date	creditCard.expirationDate	string	4 digits (0-9)	Expiration date of credit card	"0828"
↳ CVC	creditCard.cvc	string	16 digits (0-9)	Card Verification Code	"123"
↳ Billing Address	creditCard.billingAddress	Default: Object string	Default: Object with keys for all child credentials listed below Any combination of child shortenedCredentialTypes under address, , (comma), and - (dash)	Address	See 1ClickEntity example "Palo Alto, US-CA"
↳ ↳ Line 1	creditCard.billingAddress.line1	string	Title Case	Line 1 of address	"5320 Newell Rd"
↳ ↳ Line 2	creditCard.billingAddress.line2	string	Title Case	Line 2 of address	""
↳ ↳ City	creditCard.billingAddress.city	string	Title Case	City of address	"Palo Alto"
↳ ↳ State	creditCard.billingAddress.state	string	Default: 2 letter abbreviation (last 2 characters of ISO 3166-2 code for US state/territory) Full state/territory name (ISO 3166-2 subdivision name)	State of address	"CA" "California"
↳ ↳ ZIP Code	creditCard.billingAddress.zipCode	string	ZIP Code (5 digits, 0-9) or ZIP+4 (9 digits, 0-9, with a hypen after the first 5)	ZIP code of address	"94303" or "94303-3058"
↳ ↳ Country	creditCard.billingAddress.country	string	Default: 2 letter abbreviation (ISO 3166-1 alpha-2 code, currently always "US") Full country name (ISO 3166-1 English short name, currently always "United States of America")	Country of address	"US"

Employment

Add On

Name	Key	Type	Format(s)	Description	Example
Employer	employer	Object	Object with keys for all child credentials listed below	Employer information	-
↳ Employer Name	employer.employerName	string	Title Case	Employer name	"Pied Piper"
↳ Employment Start Date	employer.employmentStartDate	string	Default: Unix time (milliseconds) Any combination of y(year), M(month), d(day), /(slash), and -(dash)	Employment start date	"1396310400000" "04/01/2014"
↳ Title	employer.title	string	Title Case	Title of employment	"CEO"

Vehicles

Add On

Name	Key	Type	Format(s)	Description	Example
Vehicle	vehicle	Object	Object with keys for all child credentials listed below	Vehicle information	-
↳ VIN	vehicle.vin	string	FMVSS 115, Part 565 (US standard to calculate VIN)	Vehicle Identification Number	"4Y1SL65848Z411439"
↳ Make	vehicle.make	string	Title Case	Vehicle make	"Toyota"
↳ Model	vehicle.model	string	Title Case	Vehicle model	"RAV4"
↳ Year	vehicle.year	string	Default: Unix time (milliseconds) Any combination of y(year), M(month), d(day), /(slash), and -(dash)	Year of vehicle manufacture	"617947200000" "08/01/1989"
↳ Owner(s)	vehicle.owners	string[]	Title Case	Names of vehicle owner(s)	["Richard Hendricks", "Erlich Bachman"]
↳ MSRP	vehicle.msrp	string	Title Case	Manufacturer's suggested retail price	"Richard"
↳ ↳ Currency	vehicle.msrp.currency	enum Possible values: "USD"	ISO 4217 currency code	Currency of manufacturer's suggested retail price	"USD"
↳ ↳ Amount	vehicle.msrp.amount	string	Any number of digits (0-9)	Amount of manufacturer's suggested retail price	"10000"

Properties

Add On

Name	Key	Type	Format(s)	Description	Example
Property	property	Object	Object with keys for all child credentials listed below	Property information	-
↳ Address	property.address	Default: Object string	Default: Object with keys for all child credentials listed below Any combination of child shortenedCredentialTypes under address, , (comma), and - (dash)	Address	See 1ClickEntity example "Palo Alto, US-CA"
↳ ↳ Line 1	property.address.line1	string	Title Case	Line 1 of address	"5320 Newell Rd"
↳ ↳ Line 2	property.address.line2	string	Title Case	Line 2 of address	""
↳ ↳ City	property.address.city	string	Title Case	City of address	"Palo Alto"
↳ ↳ State	property.address.state	string	Default: 2 letter abbreviation (last 2 characters of ISO 3166-2 code for US state/territory) Full state/territory name (ISO 3166-2 subdivision name)	State of address	"CA" "California"
↳ ↳ ZIP Code	property.address.zipCode	string	ZIP Code (5 digits, 0-9) or ZIP+4 (9 digits, 0-9, with a hypen after the first 5)	ZIP code of address	"94303" or "94303-3058"
↳ ↳ Country	property.address.country	string	Default: 2 letter abbreviation (ISO 3166-1 alpha-2 code, currently always "US") Full country name (ISO 3166-1 English short name, currently always "United States of America")	Country of address	"US"
↳ Owner(s)	property.owners	string[]	Title Case	Names of property owner(s)	["Erlich Bachman"]
↳ Details	property.details	string	Sentence case	Any additional property details	"Single family home, 4BR/3BA"

Government IDs

Add On

Name	Key	Type	Format(s)	Description	Example
Government ID	governmentId	Object	Object with keys for all child credentials listed below	Government ID	-
↳ Document Type	governmentId.documentType	enum Possible values: "drivers_license" "passport" "resident_card"	snake_case	Type of government ID	-
↳ Document Number	governmentId.documentNumber	string	Any number of digits (0-9)	Number of government ID	"9876543210"
↳ Document Front Image	governmentId.documentFrontImage	string	URL	Link to image of front of government ID	"+10123456789"
↳ Document Back Image	governmentId.documentBackImage	string	URL	Link to image of back of government ID	"+10123456789"

Demographics

Add On

Name	Key	Type	Format(s)	Description	Example
Age	age	string	1-3 digits (0-9)	Age	"35"
Sex	sex	string	enum Possible values: "male" "female" "intersex" "other"	Sex	"female"
Gender	gender	string	snake_case	Gender	"woman"
Race	race	enum[] Possible values: "white" "black_or_african_american" "american_indian_or_alaska_native" "asian" "native_hawaiian_or_other_pacific_islander"	snake_case	Race	["black_or_african_american", "asian"]
Ethnicity	ethnicity	enum Possible values: "hispanic_or_latino" "not_hispanic_or_latino"	snake_case	Ethnicity	"hispanic_or_latino"
Nationality	nationality	string	Title Case	Nationality	"United States"

Metadata

A piece of metadata is additional data that's not a user's identity data (their identifiers or credentials) — though it's often about that identity data.

Metadata are outputs: we return them to you in API response bodies.

Name	Key	Type	Applies To	Format	Description	Example
Verification Method	verificationMethod	enum Possible values: "phone_carrier" "credit_bureau" "otp" "customer_otp" "self_attested" null	Identifiers Credentials	snake_case	How an identifier or credential was verified	"phone_carrier"
Risk Signals	riskSignals	Object	Identifiers	Object with keys specified below in Risk Signals	Risk signals associated with the identifiers provided	See RiskSignals example
ID	id	string	Credentials	Version 4 UUID	Unique identifier for a credential	"174b9aaf-3219-4499-b54c-0eb6acc5dbf2"
Status	status	enum Possible values: "valid" "revoked" "otp" "self_attested" null	Credentials	snake_case	The status of a credential	"valid"
Expiration Date	expirationDate	string	Credentials	Unix time (milliseconds) or null	The date a credential expires	"1671847264479"
Fraud Signals Legacy	fraudSignals	string	Identifiers	Unix time (milliseconds) or null	The date a credential expires	"1671847264479"

tip

The most commonly used type of metadata is verificationMethod, which describes how a credential was verified:

• "phone_carrier": verified via phone carrier records
• "credit_bureau": verified via credit bureau records
• "otp": verified via an OTP (one time passcode)
• "customer_otp": verified via an OTP (one time passcode) by a Verified customer, not directly by Verified
• "self_attested": attested by the user themselves (not verified)
• null

You can build custom logic to handle credentials based on their verificationMethod, for example requiring additional verification if an important credential is "self_attested".

Risk Signals

By default, Verified returns either the Overall Risk Score, Risk Level, and Risk Recommendation, or (if the risk is too high) a OCE017 error. Other risk signals are optional add ons. To enable them, please ask your Verified support representative or email us at Support@Verified.inc.

See also the RiskSignals type.

Name	Key	Type	Format(s)	Description	Example
Overall	overall	Object	Object with keys for all overall risk signals listed below	Overall risk signals, considering all identifiers provided	See RiskSignals example
↳ Score	overall.score	integer	Number from 0 (low risk) to 600 (medium risk)	Overall risk score, considering all identifiers provided. (If the score is over 600, Verified blocks the user and returns a OCE017 error.)	463
↳ Level	overall.level	enum Possible values: "low" "medium-low" "medium"	kebab-case	Overall risk level, considering all identifiers provided. (This is a bucketing of the risk score, where 0-200 is "low", 201-400 is "medium-low", and 401-600 is "medium".)	"medium"
↳ Recommendation	overall.recommendation	enum Possible values: "allow" "flag"	kebab-case	Overall risk recommendation, considering all identifiers provided. (This is a bucketing of the risk level, where "low" and "medium-low" are "allow" and "medium" is "flag".)	"flag"
↳ Reason Codes Add On	overall.reasonCodes	enum[] Possible values: see Overall reason codes	"OCR" (for One Click Reason) followed by 5 digits (0-9)	Overall reason codes for risk score/level/recommendation, considering all identifiers provided	"OCR10021"
Phone Add On	phone	Object	Object with keys for all phone identifier risk signals listed below	Phone identifier risk signals	See RiskSignals example
↳ Carrier Add On	phone.carrier	Object	Object with keys for all carrier details listed below	Carrier information	"flag"
↳ ↳ ID Add On	phone.carrier.id	integer	Any number of digits (0-9)	Carrier ID number	309
↳ ↳ Name Add On	phone.carrier.name	string	"Title Case"	Carrier name	"AT&T Wireless"
↳ Reason Codes Add On	phone.reasonCodes	enum[] Possible values: see Phone reason codes	"OCR" (for One Click Reason) followed by 5 digits (0-9)	Phone identifier reason codes for risk score/level/recommendation	"OCR20004"
Email Add On	email	Object	Object with keys for all email identifier risk signals listed below	Email identifier risk signals	See RiskSignals example
↳ Reason Codes Add On	email.reasonCodes	enum[] Possible values: see Email reason codes	"OCR" (for One Click Reason) followed by 5 digits (0-9)	Email identifier reason codes for risk score/level/recommendation	"OCR60001"

Reason Codes

Add On

Overall

Add On

Code	Description	Details	Risk Indicator	Trust Indicator
OCR10010	low activity	Not enough activity or attributes to classify the transaction as either risky or trustworthy.
OCR10020	low regular activity	Trustworthy category, based on past behavior.		✔
OCR10021	regular activity	Most trustworthy category, based on past behavior.		✔
OCR10030	low-risk irregular activity	Risky category, based on past behavior.	✔
OCR10031	medium-risk irregular activity	High-risk category, based on past behavior.	✔
OCR10032	high-risk irregular activity	Highest-risk category, based on past behavior.	✔
OCR10040	irregular number type	This number has risky static attributes (like VOIP phone type or being on a blocklist).	✔

Phone

Add On

Code	Description	Details	Risk Indicator	Trust Indicator
OCR20001	no long-term activity	Much less than expected activity, or none at all, for this number over the past 90 days. Cannot classify.
OCR20002	high long-term activity	More than expected activity for this number over the past 90 days.	✔
OCR20003	high short-term activity	More than expected activity for this number over the last 24 hours.	✔
OCR20004	moderate long-term activity	Expected activity for this number over the past 90 days.		✔
OCR20005	moderate short-term activity	Expected activity for this number over the last 24 hours.		✔
OCR20006	sparse long-term activity	Sparse, regular volume of verification traffic on this number over the past 90 days.		✔
OCR20007	continuous long-term activity	Continuous, regular volume of verification traffic on this number over the past 90 days.		✔
OCR20008	very high long-term activity	Very high volume of verification traffic on this number over the past 90 days.	✔
OCR20009	very high short-term activity	Very high volume of verification traffic on this number over the past 24 hours.	✔
OCR20010	no activity	Very low volume of verification traffic, or none at all, was ever observed on this number.
OCR20011	low long-term activity	Low volume of verification traffic on this phone number over the past 90 days.
OCR20012	low short-term activity	Low volume of verification traffic on this phone number over the past 24 hours. Very low volume of verification traffic, or none at all over the past 90 days.
OCR20013	low activity	Less than expected activity for this number.
OCR20101	no range activity	Very little activity, or none at all, for a risky range that this number belongs to over the past 90 days. Also returned if the number does not belong to a risky range.		✔
OCR20102	low range activity	Some activity for a risky range that this number belongs to over the past 90 days.	✔
OCR20103	moderate short-term range activity	Significant activity for a risky range that this number belongs to over the last 24 hours.	✔
OCR20104	moderate long-term range activity	Significant activity for a risky range that this number belongs to over the past 90 days.	✔
OCR20105	high short-term range activity	Very significant activity for a risky range that this number belongs to over the last 24 hours.	✔
OCR20106	high long-term range activity	Very significant activity for a risky range that this number belongs to over the past 90 days.	✔
OCR20107	very high long-term range activity	Extremely significant activity for a risky range that this number belongs to over the past 90 days.	✔
OCR20108	very high short-term range activity	Extremely significant activity for a risky range that this number belongs to over the last 24 hours.	✔
OCR21001	moderate activity on risky services	Significant activity on this number to or from risky services over the past 90 days.	✔
OCR21002	high activity on risky services	Very significant activity on this number to or from risky services over the past 90 days.	✔
OCR21004	long-term activity on risky services	Verification traffic on risky services on this number over the past 90 days.	✔
OCR21005	short-term activity on risky services	Verification traffic on risky services on this number over the past 24 hours.	✔
OCR21006	high long-term activity on risky services	High volume of verification traffic on risky services on this number over the past 90 days.	✔
OCR21007	high short-term activity on risky services	High volume of verification traffic on risky services on this number over the past 24 hours.	✔
OCR21008	long-term range activity on risky services	Verification traffic on risky services on the range this number belongs to over the past 90 days.	✔
OCR21009	short-term range activity on risky services	Verification traffic on risky services on the range this number belongs to over the past 24 hours.	✔
OCR21010	high long-term range activity on risky services	High volume of verification traffic on risky services on the range this number belongs to over the past 90 days.	✔
OCR21011	high short-term range activity on risky services	High volume of verification traffic on risky services on the range this number belongs to over the past 24 hours.	✔
OCR21012	very high short-term activity on risky services	Very high volume of verification traffic on risky services on this number over the past 90 days.	✔
OCR21013	very high long-term activity on risky services	Very high volume of verification traffic on risky services on this number over the past 24 hours.	✔
OCR21014	very high short-term range activity on risky services	Very high volume of verification traffic on risky services on the range this number belongs to over the past 90 days.	✔
OCR21015	very high long-term range activity on risky services	Very high volume of verification traffic on risky services on the range this number belongs to over the past 24 hours.	✔
OCR21003	machine-like activity	Behavior pattern that suggests this number is being used by a bot. Although we expect a submitted number engaged in A2P traffic to communicate with automated systems, we don’t expect the user of that number to be an automated system.	✔
OCR21016	machine-like range activity	Extremely high volume of verification traffic in a very short period (less than 1 hour) on the range this number belongs to.	✔
OCR22001	seen in the last 1 day	This number was seen in verification traffic in the last 1 day.
OCR22007	seen in the last 7 days	This number was seen in verification traffic in the last 7 days.
OCR22015	seen in the last 15 days	This number was seen in verification traffic in the last 15 days.
OCR22101	seen in the last 1 month	This number was seen in verification traffic in the last 1 month.
OCR22102	seen in the last 2 months	This number was seen in verification traffic in the last 2 months.
OCR22103	seen in the last 3 months	This number was seen in verification traffic in the last 3 months.
OCR22203	seen more than 3 months ago	This number was not seen in verification traffic in the last 3 months.
OCR30201	no P2P data analyzed	P2P data was not analyzed. Cannot classify.
OCR40001	premium number	This is a premium number.	✔
OCR40002	VOIP number	This is a VOIP number.	✔
OCR40003	toll-free number	This is a toll-free number.	✔
OCR40004	invalid number	This is an invalid number.	✔
OCR40005	payphone number	This number is associated with a payphone.	✔
OCR40006	voicemail number	This is a voicemail number.	✔
OCR40007	pager number	This number is associated with a pager.	✔
OCR40008	high-risk phone type	This number has another phone type that is risky, and that is not covered by any of the other number_type reason codes.	✔
OCR40009	high-risk carrier	This number is associated with a very risky carrier.	✔
OCR40010	medium-risk carrier	This number is associated with a risky carrier.	✔
OCR40011	high-risk prefix	This number has a risky prefix.	✔
OCR40012	phone too long	This number is invalid because it is too long, even after the application of cleansing rules.	✔
OCR40013	blacklisted number	This number has been flagged as a source of fraud.	✔
OCR40014	high-risk country	The country code of this number is for a risky country, one that originates a disproportionate share of fraud attacks.	✔
OCR40015	technical number	This number is used for special technical purposes by telecom companies, such as for roaming.
OCR40016	number used by application	Reserved for use by customers with our applications (for example to send verification messages), but it appears that it is being used for a different purpose.	✔
OCR40017	number whitelisted by customer	You have flagged this number as safe.		✔
OCR40018	phone too short	This number is too short to be a valid phone number.	✔

Email

Add On

Code	Description	Details	Risk Indicator	Trust Indicator
OCR60001	moderate short-term activity	Expected level of activity for this email address over the last 24-hours.		✔
OCR60002	moderate long-term activity	Expected level of activity for this email address over the past 90 days.		✔
OCR60003	moderate short-term activity on risky services	Significant activity for this email address to or from risky services over the last 24 hours (see risky services above for definition of that term).	✔
OCR60004	moderate long-term activity on risky services	Significant activity on this email address to or from risky services over the last 90 days (see risky services above for definition of that term).	✔
OCR60005	high short-term activity	More than expected activity for this email address over the last 24-hours.	✔
OCR60006	high long-term activity	More than expected activity for this email address over the past 90 days.	✔