Skip to content

Add age verification
to your application.

Connect record checks, phone verification, and Photo ID to your checkout or account flow. Use the returned age result to decide what happens next.

See how it works ↓Contact Us
5.0 / 5Shopify App Store4.9 / 5SourceForge
Chosen by teams including
AyloCharlotte’s WebMedterraCannKoi CBDCornbread HempHouseplantHometown HeroVaping.comMi-PodBATCHWYNKAscent ProteinForiaWillie’s RemedyVenaFiveCycling FrogMuscleSportDelta ExtraxNowadaysNot BeerLa AuroraFunky Buddha

Send a request, read the result

Keep credentials on your server and evaluate the age result in the response.

Illustrative example
Name & address lookupExample exchange
POST/v1/detection/person/by-name-address
Request · server-side
{"first_name": "Jordan",
 "last_name": "Avery",
 "address": {
   "country": "US",
   "line_1": "218 Elm Street",
   "city": "Austin",
   "district": "TX",
   "postal_code": "78701"
 },
 "age_requirement": [21],
 "exclude": ["dob"]}
Response · illustrative
{
  "detection": {
    "data": {
      "match_found": true,
      "dob": null,
      "met_age_requirement": {
        "21": true
      }
    },
    "message": "Match found"
  }
}
21+ requirement met

Your application can grant restricted access.

Use your domain token server-side

The documented API uses an Authorization header with the Bearer prefix. Never expose a live token in browser code.

Read the age result

A successful HTTP response is not itself an age approval. Inspect the returned data and requested age requirement.

Choose the right service

Record lookups and document-verification orders have different requirements.

Illustrative example
Choose a service
Name & address
Phone age lookup
Photo ID✓

SSN and country-specific checks have their own documented endpoints. SMS possession and phone age lookup are separate services.

Photo ID 
POST /v1/verification
InputsCreate a verification order
ResponseSubmission URL and verification lifecycle
AuthenticationBearer domain token

Match the service to the task

Use record-lookup services for supported data checks and the verification-order flow for Photo ID.

Build from the full reference

The documentation contains required fields, optional settings and complete response definitions.

Handle each response

Distinguish request errors from unresolved or unsuccessful verification.

Illustrative example
Request examplesSeparate requests
200Name & address
422Incomplete request
401Authentication
Response handling
HTTP status401
Customer referenceacct_2214
Authentication failed

Check the Authorization header and domain token.

Log references and necessary result details. Keep tokens and unnecessary personal information out of logs.

Separate request errors from verification outcomes

Authentication and validation errors need different handling from an unresolved age check.

Keep sensitive information out of logs

Use references and the minimum response detail your team needs. Avoid logging tokens or unnecessary personal data.

Questions about the API

Are the JavaScript and Python samples SDK calls?

No. They use standard HTTP clients: fetch in JavaScript and urllib in Python. No assumed BlueCheck SDK is required.

Does every service return the same status?

No. Record lookups and Photo ID verification orders have different response shapes. Follow the reference for the service you use.

Can I use this for checkout and account signup?

Use a supported ecommerce integration for orders, or connect the API to your website’s account and access flow. Apply the returned result before granting restricted access.

Inputs, coverage, and complete API reference →

Get started

Connect your first verification request.

Contact Us