Outputs
An output is a piece of data we return from the SDK or API.
Text to Signup
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Phone | phone | string | E.164 | Phone number a user uses to verify for 1-Click Signup | "+12125550010" |
1-Click Verify
GET /1-click/verifications/device-ip always returns device IP in IPv6 format, because this is what our other endpoints require. We internally map IPv4 to IPv6 when necessary.
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Device IP | deviceIp | string | IPv6 | IPv6 address of user's device | "::121:2555:0010" |
| Phone | phone | string | E.164 | Phone number a user uses to verify for 1-Click Signup | "+12125550010" |
1-Click Signup
Credentials
A credential is a piece of identity data about a user.
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.
Core Data
We can source the data below for ~95% of US adults if you provide both phone and a challenge (either birthday or SSN4) as inputs — and for about 20% if you provide only phone. (The one exception is the Sex credential, which we can source for ~80% of US adults.)
Exact coverage depends on your user base and varies widely across companies. Some companies see >97% coverage, while a few see only 50%. See Coverage for more information.
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Phone | phone | string | E.164 | Phone number | "+12125550010" |
| Full Name | fullName |
|
| Full name |
|
| ↳ First Name | fullName.firstName | string | Title Case | First name | "Richard" |
| ↳ Middle Name | fullName.middleName | string | Title Case | Middle name | "Harrison" |
| ↳ Last Name | fullName.lastName | string | Title Case | Last name | "Hendricks" |
| Address | address |
|
| Address |
|
| ↳ 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 |
| State of address |
|
| ↳ ZIP Code | address.zipCode | string | ZIP Code (5 digits, 0-9) | ZIP Code of address | "94303" |
| ↳ Country | address.country | string |
| Country of address |
|
| Birth Date | birthDate | string | Birth date |
|
|
| SSN (or ITIN) | ssn | string | 9 digits (0-9) | Social Security Number (or Individual Taxpayer Identification Number) | "000456789" |
| Sex | sex | string |
| Sex | "Male" |
We can return up to 3 most recent addresses for a user, if you have risk signals turned on. We order these addresses from most to least recent, as best as we're able to determine recency.
You can show the user a dropdown to select one of the addresses on the info confirmation step (see here on the User Experience page). We highly recommend this because it helps reduce the chance the user will need to manually enter an address, reducing friction and boosting conversion.
If we find an ITIN but not an SSN for a user, we return the ITIN under the ssn key. ITINs and SSNs are both 9 digit numbers, and ITINs are easily distinguishable because they start with the number 9.
Government IDs Beta
Access to driver's license data varies state by state, so coverage and recency are substantially lower than for core data.
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Driver's License | driversLicense | object | Object with keys for all child credentials listed below | Driver's license | - |
| ↳ Document Number | driversLicense.documentNumber | string | Format varies by state | Driver's license number | "A0000000" |
| ↳ Issuance State | driversLicense.issuanceState | string |
| Issuance state of driver's license |
|
| ↳ Issuance Date | driversLicense.issuanceDate | string |
| Issuance date of driver's license |
|
| ↳ Expiration Date | driversLicense.expirationDate | string |
| Expiration date of of driver's license |
|
| ↳ Address | driversLicense.address |
|
| Driver's license address |
|
| ↳ ↳ Line 1 | driversLicense.address.line1 | string | Title Case | Line 1 of driver's license address | "5320 Newell Rd" |
| ↳ ↳ Line 2 | driversLicense.address.line2 | string | Title Case | Line 2 of driver's license address | "" |
| ↳ ↳ City | driversLicense.address.city | string | Title Case | City of driver's license address | "Palo Alto" |
| ↳ ↳ State | driversLicense.address.state | string |
| State of driver's license address |
|
| ↳ ↳ ZIP Code | driversLicense.address.zipCode | string | ZIP Code (5 digits, 0-9) | ZIP Code of driver's license address | "94303" |
| ↳ ↳ Country | driversLicense.address.country | string |
| Country of driver's license address |
|
We're working on adding support for new types of government ID. Let us know what would be most helpful for your use case! Email us at Support@Verified.inc and we'll prioritize accordingly.
Vehicles Coming Soon
| Output | 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" |
| ↳ License Plate | vehicle.licensePlate | string | Any alphanumeric string | Vehicle license plate | "ABC123" |
| ↳ Make | vehicle.make | string | Title Case | Vehicle make | "Toyota" |
| ↳ Model | vehicle.model | string | Title Case | Vehicle model | "RAV4" |
| ↳ Year | vehicle.year | string |
| Year of vehicle manufacture |
|
Employment Coming Soon
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Employer | employer | object | Object with keys for all child credentials listed below | Employer information | - |
| ↳ Name | employer.name | string | Title Case | Employer name | "Pied Piper" |
| ↳ Address | employer.address |
|
| Address |
|
| ↳ ↳ Line 1 | employer.address.line1 | string | Title Case | Line 1 of address | "5320 Newell Rd" |
| ↳ ↳ Line 2 | employer.address.line2 | string | Title Case | Line 2 of address | "" |
| ↳ ↳ City | employer.address.city | string | Title Case | City of address | "Palo Alto" |
| ↳ ↳ State | employer.address.state | string |
| State of address |
|
| ↳ ↳ ZIP Code | employer.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 | employer.address.country | string |
| Country of address |
|
Properties Coming Soon
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Property | property | object | Object with keys for all child credentials listed below | Property information | - |
| ↳ Address | property.address |
|
| Address |
|
| ↳ ↳ 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 |
| State of address |
|
| ↳ ↳ 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 |
| Country of address |
|
| ↳ Owner(s) | property.owners | string[] | Title Case | Names of property owner(s) | ["Erlich Bachman"] |
| ↳ Seller(s) | property.sellers | string[] | Title Case | Names of property seller(s) | ["Erlich Bachman"] |
Metadata
A piece of metadata is additional data that's not a user's identity data — though it's often about that identity data.
Verification Method
| Output | Key | Type | Applies To | Format | Description | Example |
|---|---|---|---|---|---|---|
| Verification Method | verificationMethod |
|
| snake_case | How an identifier or credential was verified | "phone_carrier" |
What Verification Method Means
verificationMethod describes how a credential was verified:
"credit_bureau": verified via credit bureau records"data_bureau": verified via data bureau records"phone_carrier": verified via phone carrier 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
| Output | Key | Type | Applies To | Format | Description | Example |
|---|---|---|---|---|---|---|
| Risk Signals | riskSignals | object |
| Object with keys specified below in Risk Signals | Risk signals associated with the identifiers provided | See RiskSignals example |
Risk signals metadata enhance 1-Click Signup's anti-fraud capabilities. They come with extra cost and can be disabled if desired, but we recommend that you use them to improve your ability to prevent fraud.
See also the RiskSignals type.
You can configure which risk signals you receive using the risk signals brand setting:
| Option | Description |
|---|---|
| On | Include risk signals |
| Off Not Recommended | Don't include risk signals |
If risk signals are enabled, we will block users with an Overall Score greater than 600 and return a OCE017 error.
We and other companies assign specific services — called "risky services" — to interact with numbers that are considered more likely to be malicious. These risky services are not themselves risky. Rather, if the phone number you submit to our API has had a lot of interaction with them, that phone number is potentially risky.
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Overall | overall | object | Object with keys for all overall risk signals listed below | Overall risk signals, considering all relevant inputs provided | |
| ↳ Score | overall.score |
| Number from 0 (low risk) to 1000 (high risk) | Overall risk score, considering all relevant inputs provided. (If the score is over 600, Verified blocks the user and returns a OCE017 error.) |
|
| ↳ Level | overall.level |
|
| Overall risk level, considering all relevant inputs provided. (This is a bucketing of the risk score, where 0-200 is "low", 201-400 is "medium-low", 401-600 is "medium", 601-800 is "medium-high", and 801-1000 is "high".) |
|
| ↳ Recommendation | overall.recommendation |
|
| Overall risk recommendation, considering all relevant inputs provided. (This is a bucketing of the risk level, where "low" and "medium-low" are "allow", "medium" is "flag", and "medium-high" and "high" are "block".) |
|
| ↳ Reason Codes | overall.reasonCodes |
|
| Overall reason codes for risk score/level/recommendation, considering all relevant inputs provided |
|
| Phone | phone | object | Object with keys for all phone risk signals listed below | Phone risk signals | |
| ↳ Carrier | phone.carrier | object | Object with keys for all carrier details listed below | Carrier information |
|
| ↳ ↳ ID | phone.carrier.id | integer | Any number of digits (0-9) | Carrier ID number | 309 |
| ↳ ↳ Name | phone.carrier.name | string | "Title Case" | Carrier name | "AT&T Wireless" |
| ↳ Reason Codes | phone.reasonCodes |
|
| Phone reason codes for risk score/level/recommendation |
|
email | object | Object with keys for all email risk signals listed below | Email risk signals | ||
| ↳ Reason Codes | email.reasonCodes |
|
| Email reason codes for risk score/level/recommendation |
|
| Device IP | deviceIp | object | Object with keys for all device IP risk signals listed below | IP address identifier risk signals | |
| ↳ Reason Codes | deviceIp.reasonCodes | Details
Possible values: see Device IP reason codes |
| Device IP reason codes for risk score/level/recommendation |
|
Reason Codes
Overall
Code | Description | Details | Risk Indicator | Trust Indicator |
|---|---|---|---|---|
| low activity | Not enough activity or attributes to classify the transaction as either risky or trustworthy. | ||
| low regular activity | Trustworthy category, based on past behavior. | ✔ | |
| regular activity | Most trustworthy category, based on past behavior. | ✔ | |
| low-risk irregular activity | Risky category, based on past behavior. | ✔ | |
| medium-risk irregular activity | High-risk category, based on past behavior. | ✔ | |
| high-risk irregular activity | Highest-risk category, based on past behavior. | ✔ | |
| irregular number type | This number has risky static attributes (like VOIP phone type or being on a blocklist). | ✔ |
Phone
Code | Description | Details | Risk Indicator | Trust Indicator |
|---|---|---|---|---|
| no long-term activity | Much less than expected activity, or none at all, for this number over the past 90 days. Cannot classify. | ||
| high long-term activity | More than expected activity for this number over the past 90 days. | ✔ | |
| high short-term activity | More than expected activity for this number over the last 24 hours. | ✔ | |
| moderate long-term activity | Expected activity for this number over the past 90 days. | ✔ | |
| moderate short-term activity | Expected activity for this number over the last 24 hours. | ✔ | |
| sparse long-term activity | Sparse, regular volume of verification traffic on this number over the past 90 days. | ✔ | |
| continuous long-term activity | Continuous, regular volume of verification traffic on this number over the past 90 days. | ✔ | |
| very high long-term activity | Very high volume of verification traffic on this number over the past 90 days. | ✔ | |
| very high short-term activity | Very high volume of verification traffic on this number over the past 24 hours. | ✔ | |
| no activity | Very low volume of verification traffic, or none at all, was ever observed on this number. | ||
| low long-term activity | Low volume of verification traffic on this phone number over the past 90 days. | ||
| 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. | ||
| low activity | Less than expected activity for this number. | ||
| 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. | ✔ | |
| low range activity | Some activity for a risky range that this number belongs to over the past 90 days. | ✔ | |
| moderate short-term range activity | Significant activity for a risky range that this number belongs to over the last 24 hours. | ✔ | |
| moderate long-term range activity | Significant activity for a risky range that this number belongs to over the past 90 days. | ✔ | |
| high short-term range activity | Very significant activity for a risky range that this number belongs to over the last 24 hours. | ✔ | |
| high long-term range activity | Very significant activity for a risky range that this number belongs to over the past 90 days. | ✔ | |
| very high long-term range activity | Extremely significant activity for a risky range that this number belongs to over the past 90 days. | ✔ | |
| very high short-term range activity | Extremely significant activity for a risky range that this number belongs to over the last 24 hours. | ✔ | |
| moderate activity on risky services | Significant activity on this number to or from risky services over the past 90 days. | ✔ | |
| high activity on risky services | Very significant activity on this number to or from risky services over the past 90 days. | ✔ | |
| long-term activity on risky services | Verification traffic on risky services on this number over the past 90 days. | ✔ | |
| short-term activity on risky services | Verification traffic on risky services on this number over the past 24 hours. | ✔ | |
| high long-term activity on risky services | High volume of verification traffic on risky services on this number over the past 90 days. | ✔ | |
| high short-term activity on risky services | High volume of verification traffic on risky services on this number over the past 24 hours. | ✔ | |
| long-term range activity on risky services | Verification traffic on risky services on the range this number belongs to over the past 90 days. | ✔ | |
| short-term range activity on risky services | Verification traffic on risky services on the range this number belongs to over the past 24 hours. | ✔ | |
| 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. | ✔ | |
| 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. | ✔ | |
| 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. | ✔ | |
| 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. | ✔ | |
| 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. | ✔ | |
| 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. | ✔ | |
| 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. | ✔ | |
| 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. | ✔ | |
| seen in the last 1 day | This number was seen in verification traffic in the last 1 day. | ||
| seen in the last 7 days | This number was seen in verification traffic in the last 7 days. | ||
| seen in the last 15 days | This number was seen in verification traffic in the last 15 days. | ||
| seen in the last 1 month | This number was seen in verification traffic in the last 1 month. | ||
| seen in the last 2 months | This number was seen in verification traffic in the last 2 months. | ||
| seen in the last 3 months | This number was seen in verification traffic in the last 3 months. | ||
| seen more than 3 months ago | This number was not seen in verification traffic in the last 3 months. | ||
| no P2P data analyzed | P2P data was not analyzed. Cannot classify. | ||
| premium number | This is a premium number. | ✔ | |
| VOIP number | This is a VOIP number. | ✔ | |
| toll-free number | This is a toll-free number. | ✔ | |
| invalid number | This is an invalid number. | ✔ | |
| payphone number | This number is associated with a payphone. | ✔ | |
| voicemail number | This is a voicemail number. | ✔ | |
| pager number | This number is associated with a pager. | ✔ | |
| 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. | ✔ | |
| high-risk carrier | This number is associated with a very risky carrier. | ✔ | |
| medium-risk carrier | This number is associated with a risky carrier. | ✔ | |
| high-risk prefix | This number has a risky prefix. | ✔ | |
| phone too long | This number is invalid because it is too long, even after the application of cleansing rules. | ✔ | |
| blacklisted number | This number has been flagged as a source of fraud. | ✔ | |
| high-risk country | The country code of this number is for a risky country, one that originates a disproportionate share of fraud attacks. | ✔ | |
| technical number | This number is used for special technical purposes by telecom companies, such as for roaming. | ||
| 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. | ✔ | |
| number whitelisted by customer | You have flagged this number as safe. | ✔ | |
| phone too short | This number is too short to be a valid phone number. | ✔ |
Email
Code | Description | Details | Risk Indicator | Trust Indicator |
|---|---|---|---|---|
| moderate short-term activity | Expected level of activity for this email address over the last 24-hours. | ✔ | |
| moderate long-term activity | Expected level of activity for this email address over the past 90 days. | ✔ | |
| moderate short-term activity on risky services | Significant activity for this email address to or from risky services over the last 24 hours . | ✔ | |
| moderate long-term activity on risky services | Significant activity on this email address to or from risky services over the last 90 days . | ✔ | |
| high short-term activity | More than expected activity for this email address over the last 24-hours. | ✔ | |
| high long-term activity | More than expected activity for this email address over the past 90 days. | ✔ |
Device IP
Code | Description | Details | Risk Indicator | Trust Indicator |
|---|---|---|---|---|
| moderate short-term activity | Expected level of activity for this IP address over the last 24 hours. | ✔ | |
| moderate long-term activity | Expected level of activity for this IP address over the past 90 days. | ✔ | |
| moderate short-term activity on risky services | Significant activity for this IP address to or from risky services over the last 24 hours . | ✔ | |
| moderate long-term activity on risky services | Significant activity on this IP address to or from risky services over the last 90 days . | ✔ | |
| high short-term activity | More than expected activity for this IP address over the last 24 hours. | ✔ | |
| high long-term activity | More than expected activity for this IP address over the past 90 days. | ✔ | |
| high short-term activity on risky services | Very significant activity for this IP address to or from risky services over the last 24 hours . | ✔ | |
| high long-term activity on risky services | Very significant activity on this IP address to or from risky services over the last 90 days . | ✔ | |
| very high short-term activity | Very frequent changes of IP address attributes in verification traffic on this number over the past 24 hours. | ✔ | |
| very high long-term activity | Very frequent changes of IP address attributes in verification traffic on this number over the past 90 days. | ✔ | |
| short-term activity on risky services | Changes of IP address attributes in verification traffic on risky services on this number over the past 24 hours. | ✔ | |
| long-term activity on risky services | Changes of IP address attributes in verification traffic on risky services on this number over the past 90 days. | ✔ | |
| very high short-term activity on risky services | Very frequent changes of IP address attributes in verification traffic on risky services on this number over the past 24 hours. | ✔ | |
| very high long-term activity on risky services | Very frequent changes of IP address attributes in verification traffic on risky services on this number over the past 90 days. | ✔ | |
| anonymous proxy | This IP address is associated with anonymous proxies, which can help conceal the true origins of online traffic. | ✔ | |
| VPN | This IP address is associated with virtual private networks (VPNs), which can help conceal the true origins of online traffic. | ✔ | |
| hosting provider | This IP address is associated with web hosting servers, which have a pattern of activity different than genuine end users. | ✔ | |
| TOR exit node | This IP address is associated with Tor anonymous browsers, which can help conceal the true origins of online traffic. | ✔ |
1-Click Health
We can source the data below for ~80% of US adults. Exact coverage depends on your user base.
See Coverage for more information.
If we return multiple health insurance plans for a user, they're ordered from most to least probable. All plans we return have a high probability of matching the user, since we filter out low probability ones.
A user may have multiple plans, for example if they have separate ones for medical, dental, or vision. We recommend that you let the user choose which plan they want to use, setting the first plan we return (which we deem most probable) as the default choice.
1-Click Health can return many different IDs for a given payer:
verifiedId: This ID identifies the payer within Verified but is not used in external systems. It never changes, so it can reliably used to identify the payer over time.ids[]: These IDs identify the payer in external systems, like healthcare clearing houses or the payer's own system. They may change over time.ids[0]: This is considered the primary ID for the payer and is generally the ID the payer uses for itself. It may change over time.
Basic Insurance Details
Basic insurance details include high level information about health insurance plans, like the member ID and payer. Full insurance details are available when an eligibility check is run.
Member ID
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Member ID | memberId | string | Alphanumeric | Member ID for health insurance plan | "V000000000" |
Payer
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Payer | payer | Payer | See Payer | Payer for health insurance plan | See Payer Example |
| ↳ Name | payer.name | string | Title Case | Name of payer for health insurance plan | "Aviato Health Insurance Of California" |
| ↳ Verified ID | payer.verifiedId | string | V followed by 6 digits (0-9) | Verified ID (never changes) of payer for health insurance plan | "V431835" |
| ↳ IDs | payer.ids | string[] | Array of strings | IDs (can change) of payer for health insurance plan — ids[0] is considered primary | ["0000A"] |
| ↳ Logo URL | payer.logoUrl | string | URL | URL for logo of payer for health insurance plan | "https://assets.verified.inc/1-click/health/payers/11145919-80e4-4cb0-8518-cffbf44ee9fb.png" |
Additional Info
Unlike member ID and payer, this additional info isn't generally user facing.
| Output | Key | Type | Format(s) | Description | Example |
|---|---|---|---|---|---|
| Verification Method | verificationMethod |
| snake_case | How a health insurance plan was verified | "clearinghouse" |
| Coverage Types | coverageTypes |
| lower case | Coverage type(s) of health insurance plan | "[medical]" |
| Service Type Codes | serviceTypeCodes | string[] | Array of strings | List of X12 service type codes for health insurance plans | ["30"] |
| Is Medicare | isMedicare | boolean | - | Whether health insurance plan is for Medicare | true |
What Verification Method Means
verificationMethod describes how a health insurance plan was verified:
"clearinghouse": verified via clearinghouse records"self_attested": attested by the user themselves (not verified)null
You can build custom logic to handle health insurance plans based on their verificationMethod, for example applying additional validation if one is "self_attested".
Full Insurance Details
Full insurance details include all known information about a health insurance plan and are available when an eligibility check is run.
EDI 271
| Output | Key | Type | Format | Description | Example |
|---|---|---|---|---|---|
| EDI 271 | edi_271 | string | X12 EDI 271 (Health Care Eligibility Benefit Response) | Address | See X12 EDI 271 examples |
Eligibility
| Output | Key | Type | Format | Description | Example |
|---|---|---|---|---|---|
| Eligibility | eligibility | ParsedEdi271 | See ParsedEdi271 | Parsed version of edi_271 | See ParsedEdi271 Example |
| ↳ Coverage Status | eligibility.coverageStatus |
| camelCase | Coverage status of health insurance plan | "active" |
| ↳ Coverage Type | eligibility.coverageType |
| lower case | Coverage type(s) of health insurance plan | "[medical]" |
| ↳ Service Type Codes | eligibility.serviceTypeCodes | string[] | Array of strings | List of X12 service type codes for health insurance plan | ["30"] |
| ↳ Payer | eligibility.payer | object | Object with key described below | Payer for health insurance plan | ["0000A"] |
| ↳ ↳ Payer Name | eligibility.payer.name | string | - | Name of payer for health insurance plan | "Aetna" |
| ↳ Member | eligibility.member | object | Object with keys described below | Member for health insurance plan | - |
| ↳ ↳ Member ID | eligibility.member.memberId | string | - | Member ID of member for health insurance plan | "A484069" |
| ↳ ↳ Full Name | eligibility.member.fullName | string | - | Full name of member for health insurance plan | - |
| ↳ ↳ ↳ First Name | eligibility.member.fullName.firstName | object | - | First name of member for health insurance plan | "Richard" |
| ↳ ↳ ↳ Last Name | eligibility.member.fullName.lastName | string | - | Last name of member for health insurance plan | "Hendricks" |
| ↳ ↳ Birth Date | eligibility.member.birthDate | string | yyyy-MM-dd | Birth date of member for health insurance plan | "1989-08-01" |
| ↳ ↳ Sex | eligibility.member.sex |
| Title Case | Sex of member for health insurance plan | "Male" |
| ↳ ↳ Full Name | eligibility.member.fullName | object | - | Full name of member for health insurance plan | - |
| ↳ ↳ ↳ First Name | eligibility.member.fullName.firstName | string | - | First name of member for health insurance plan | "Richard" |
| ↳ ↳ Address | eligibility.member.address | object | Object with keys described below | Address of member for health insurance plan | |
| ↳ ↳ ↳ Line 1 | eligibility.member.address.line1 | string | Title Case | Line 1 of address of member for health insurance plan | "5320 Newell Rd" |
| ↳ ↳ ↳ Line 2 | eligibility.member.address.line2 | string | Title Case | Line 2 of address of member for health insurance plan | "" |
| ↳ ↳ ↳ City | eligibility.member.address.city | string | Title Case | City of address of member for health insurance plan | "Palo Alto" |
| ↳ ↳ ↳ State | eligibility.member.address.state | string | 2 letter abbreviation (last 2 characters of ISO 3166-2 code for US state/territory) | State of address of member for health insurance plan | "CA" |
| ↳ ↳ ↳ ZIP Code | eligibility.member.address.zipCode | string | ZIP Code (5 digits, 0-9) | ZIP Code of address of member for health insurance plan | "94303" |
| ↳ Plan | eligibility.plan | object | Object with keys described below | Details for health insurance plan | - |
| ↳ ↳ Name | eligibility.plan.name | string | - | Name for health insurance plan | "Managed Choice Open Access" |
| ↳ ↳ Group Number | eligibility.plan.groupNumber | string | - | Group number (for employer or purchaser group) for health insurance plan | "123456-123-12345" |
| ↳ ↳ Group Name | eligibility.plan.groupName | string | - | Group name (for employer or purchaser group) for health insurance plan | "Pied Piper" |
| ↳ ↳ Insurance Types | eligibility.plan.insuranceTypeCodes | string[] | Array of strings | List of X12 insurance descriptor codes relevant to benefit of health insurance plan | ["C1"] |
| ↳ ↳ Effective Date | eligibility.plan.effectiveDate | string | yyyy-MM-dd | Coverage start date for health insurance plan | "2026-01-01" |
| ↳ ↳ Termination Date | eligibility.plan.terminationDate | string | yyyy-MM-dd | Coverage end date for health insurance plan | "2026-12-31" |
| ↳ Benefits | eligibility.benefits | object[] | Array of objects | Benefits for health insurance plan | - |
| ↳ ↳ Type | eligibility.benefits[i].type |
| camelCase | Type of cost share for health insurance plan | "deductible" |
| ↳ ↳ Service Type Codes | eligibility.benefits[i].serviceTypeCodes | string[] | Array of strings | List of X12 service type codes relevant to benefit for health insurance plan | ["30"] |
| ↳ ↳ Insurance Type | eligibility.benefits[i].insuranceTypeCode | string | - | X12 insurance descriptor code for health insurance plan | "C1" |
| ↳ ↳ Level | eligibility.benefits[i].level |
| camelCase | Coverage level that amount applies to for health insurance plan | "individual" |
| ↳ ↳ Network | eligibility.benefits[i].network |
| camelCase | Whether 271 says health insurance plan is in or out of network (different from the network object of type NetworkDecision, which is based on network rules you define) | "in" |
| ↳ ↳ Amount | eligibility.benefits[i].amount | string | decimal | Dollar amount applicable (copay, or period total for deductible or out of pocket) for health insurance plan | "1500.00" |
| ↳ ↳ Remaining | eligibility.benefits[i].remaining | string | decimal | Dollar amount remaining (deductible or out of pocket) for health insurance plan | "750.00" |
| ↳ ↳ Percent | eligibility.benefits[i].percent | string | decimal fraction | Patient coinsurance responsibility for health insurance plan | "0.20" |
| ↳ Contacts | eligibility.contacts | object[] | Array of objects | Contacts for health insurance plan | - |
| ↳ ↳ Name | eligibility.contacts[i].name | string | - | Entity to contact (e.g. the payer's member services or a carve out administrator) about health insurance plan | "Aetna Member Services" |
| ↳ ↳ Service Type Codes | eligibility.contacts[i].serviceTypeCodes | string[] | Array of strings | List of X12 service type codes relevant to contact for health insurance plan | ["30"] |
| ↳ ↳ Phone | eligibility.contacts[i].phone | string | - | Phone number | "8005550000" |
| ↳ ↳ Fax | eligibility.contacts[i].fax | string | - | Fax number | "8005550001" |
eligibility.contacts[i].email | string | Email address | "memberservices@aetna.com" | ||
| ↳ ↳ URL | eligibility.contacts[i].url | string | URL | Contact URL | "https://aetna.com/member-services" |
Network Decision
Network decisions are included in outputs when an eligibility check is run and at least one network rule is defined.
| Output | Key | Type | Format | Description | Example |
|---|---|---|---|---|---|
| Network | network | NetworkDecision | See NetworkDecision | Parsed version of edi_271 | See NetworkDecision Example |
| ↳ Status | network.status |
| UPPER_SNAKE_CASE | Network status of health insurance plan, based on your network rules | "IN_NETWORK" |
| ↳ Rules | network.rules | NetworkRule[] | Array of NetworkRules | List of network rules that matched health insurance plan | - |
| ↳ ↳ Rule | network.rules[i] | NetworkRule | See NetworkRule | Network rule that matched health insurance plan | See NetworkRule Example |
| ↳ ↳ ↳ UUID | network.rules[i].uuid | string | Version 4 UUID | Unique identifier for the network rule | "ab280ee0-5f66-4076-9d1b-255d5f0024e3" |
| ↳ ↳ ↳ Name | network.rules[i].name | string | - | Name for the network rule | "Rule 1: Aetna - INN" |
| ↳ ↳ ↳ Status | network.rules[i].status |
| UPPER_SNAKE_CASE | Network status the network rule returns | "IN_NETWORK" |
| ↳ ↳ ↳ Notes | network.rules[i].notes | string | - | Notes about the network rule | "Requires manual review" |
| ↳ ↳ ↳ Metadata | network.rules[i].metadata | object | - | Metadata for the network rule | |
| ↳ ↳ ↳ ↳ Metadata | network.rules[i].metadata[key] | string | number | boolean | - | Piece of metadata for the network rule | "selfPay": false |
| ↳ ↳ ↳ Start Date | network.rules[i].startDate | string | yyyy-MM-dd | Start date for the network rule | "2026-10-01" |
| ↳ ↳ ↳ End Date | network.rules[i].endDate | string | yyyy-MM-dd | End date for the network rule | "2027-09-30" |
| ↳ ↳ ↳ Conditions | network.rules[i].conditions | object[] | Array of objects | Conditions for when the network rule matches | |
| ↳ ↳ ↳ ↳ Condition | network.rules[i].conditions[j] | object | - | Condition for when the network rule matches | |
| ↳ ↳ ↳ ↳ ↳ Key | network.rules[i].conditions[j].key |
| camelCase | Key for condition | "payerId" |
| ↳ ↳ ↳ ↳ ↳ Operator | network.rules[i].conditions[j].operator |
| UPPER_SNAKE_CASE | Operator for condition | "EQUAL" |
| ↳ ↳ ↳ ↳ ↳ Values | network.rules[i].conditions[j].values | string[] | camelCase | Value(s) for condition | ["V404110"] |