Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.prove.com/llms.txt

Use this file to discover all available pages before exploring further.

Flowchart: Pre-Fill for Consumers from v3/verify through a Success decision to Success=False or Success=True, then Continuous Monitoring and a phone number change event after success
Identities that pass the Global Fraud Policy are automatically enrolled in Manage.

Prerequisites

  • Access token — Obtain a bearer token using Prove OAuth (Authentication).

Implementation steps

1

Gather Required Inputs

Collect the phone number from your CRM or database.
2

Call the Verify Endpoint

Make a request to the /v3/verify endpoint including the Authorization header. Generate a bearer token as outlined on the Authentication page.
cURL
curl -X POST "https://platform.uat.proveapis.com/v3/verify" \
-H "Authorization: Bearer <YOUR_ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
    "phoneNumber": "2005550123",
    "verificationType": "prefill",
    "clientRequestId": "request-123"
}'
Replace <YOUR_ACCESS_TOKEN> with your acquired access token.
For Pre-Fill for Consumers, set verificationType to prefill and include phoneNumber. You can also pass clientRequestId, clientCustomerId, clientHumanId, or proveId when you need that linkage.
3

Process the Response

Use the samples below together with the /v3/verify response schema. Cross-check field meanings with Assurance levels and Global Fraud Policy when interpreting codes and evaluations.
{
  "success": "true",
  "correlationId": "713189b8-5555-4b08-83ba-75d08780aebd",
  "phoneNumber": "12005550123",
  "proveId": "a07b94ce-218c-461f-beda-d92480e40f61",
  "provePhoneAlias": "4B2C41FC4VKDEO100F960011D0AD4A8050MEK19P4SF9PD23EFE27CD2C76A6FAA8375E60AC0550604F6G32D9ED60E06262CCC570F3C15F2D16900184E",
  "isEnrolled": true,
  "clientRequestId": "request-123",
  "identity": {
    "firstName": "Alice",
    "lastName": "Smith",
    "dateOfBirth": "1992-03-02",
    "nationalId": "111-22-6789",
    "emails": [
      "alice@example.com",
      "a.smith@example.com",
      "ajohnson@globocorp.com"
    ],
    "addresses": [
      {
        "address": "123 Main St",
        "extendedAddress": "Apt A",
        "city": "New York",
        "region": "NY",
        "zipCode": "10001"
      },
      {
        "address": "Farm Road 223",
        "extendedAddress": "",
        "city": "Fargo",
        "region": "ND",
        "zipCode": "58801"
      }
    ],
    "assuranceLevel": "AL3",
    "reasons": ["AL3a"]
  },
  "evaluation": {
    "authentication": { "result": "pass" },
    "identification": { "result": "pass" },
    "risk": { "result": "pass" }
  }
}

In practice

  • success — Branch your UX and backend logic on pass vs fail.
  • identity — Use returned attributes for pre-fill where appropriate; read assuranceLevel and reasons for policy (allow, step-up, deny).
  • evaluation — Interpret authentication, identification, and risk under Global Fraud Policy; use failure codes when success is false.
  • IDs — Persist correlationId (and proveId when present) if you need support, auditing, or linking to other Prove flows.
If you passed optional identifiers on the request, the response may echo clientCustomerId and clientHumanId; see /v3/verify for details.

Sandbox testing

Test users

You must use project credentials when working with sandbox test users. Attempting to use these test users with different project credentials results in an unauthorized access error.
The following test users are available for testing using the /v3/verify endpoint in the Sandbox environment. Use these test users to simulate different verification scenarios and outcomes.
Use these test phone numbers exactly as shown. The sandbox environment doesn’t validate real customer information.
Phone NumberFirst NameLast NameVerification TypeExpected Outcome
2001004065MeadWillmentprefillSuccess
2001004067RoxiManneringprefillSuccess

Testing steps

Use test user Mead Willment to verify a successful verification:
cURL
curl -X POST "https://platform.uat.proveapis.com/v3/verify" \
  -H "Authorization: Bearer <YOUR_ACCESS_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "verificationType": "prefill",
    "phoneNumber": "2001004065",
    "clientRequestId": "test-request-001"
  }'
Expected response:
{
    "success": "true",
    "correlationId": "7c7f84bb-6b1d-4a7a-8570-8b14e3aed3d6",
    "clientRequestId": "test-request-001",
    "phoneNumber": "2001004065",
    "proveId": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
    "provePhoneAlias": "PSDMF50KQKCE882PARQH4RFPA1SAF31JNJDQM9J1Y61STZ4CQPB4EENRW2QN346BSXTSESXNDZ7S7GZ50NJSQRAEE7394RR1G4Q7EDB9SREK3T9KM4LZHX0PUB30H9FE",
    "identity": {
        "firstName": "Mead",
        "lastName": "Willment",
        "dateOfBirth": "1988-11-28",
        "emails": [
            "mwillment1t@digg.com"
        ],
        "assuranceLevel": "AL3",
        "reasons": null
    },
    "evaluation": {
        "authentication": {
            "result": "pass"
        },
        "identification": {
            "result": "pass"
        },
        "risk": {
            "result": "pass"
        }
    },
    "isEnrolled": true
}