Numverify

The Numverify Workflow Builder block validates an individual’s phone number and returns country, formatting, carrier, and line-type information. The current block represents numverify.

Requirements

Application field	Requirement	Notes
Phone number	Required	A complete international number is preferred.
Country code	Optional	Use a country code when the phone number is not in international format.

API flow

Call Enrich Business Credit Application.
Set provider to numverify.
Put phone_number and optional country_code in options.
Confirm data.onqueue: true.
Check the latest lifecycle status with Get Commercial Data, filtered with services[]=numverify.
Retrieve the provider-specific validation records from GET /api/applications/{application_id}/validate_numbers and select records whose business_credit_service is numverify. This provider-specific route does not currently have an OpenAPI reference operation.

{
  "provider": "numverify",
  "options": {
    "phone_number": "+14155550100",
    "country_code": "US"
  }
}

Data Orchestration availability and flow

The block is available in the Phone Number Verification group for individual entities. Configure the phone number to validate and, when needed, its country code. Each run creates a validation record associated with the application; it does not alter the supplied number.

What the service returns

Result area	Response path	Meaning
Lifecycle	`data.statuses.numverify` from Get Commercial Data	Latest Numverify execution message.
Validation records	Provider-specific `GET /api/applications/{application_id}/validate_numbers` route (not currently represented in OpenAPI)	Stored phone-validation records and raw Numverify responses.

Representative response

{
  "data": [{
        "phone_number": "+14155550100",
        "is_valid": true,
        "line_type": "mobile",
        "response": {
          "valid": true,
          "number": "14155550100",
          "local_format": "4155550100",
          "international_format": "+14155550100",
          "country_prefix": "+1",
          "country_code": "US",
          "country_name": "United States of America",
          "location": "California",
          "carrier": "Example Carrier",
          "line_type": "mobile"
        }
      }]
}

Field meanings

Field	Type	Meaning
`is_valid`, `response.valid`	Boolean	Whether Numverify considers the number valid.
`line_type`	String or null	Normalized line type stored by Lendflow; unavailable values remain null.
`local_format`	String	Nationally formatted number when available.
`international_format`	String	Internationally formatted number when available.
`country_prefix`	String	Calling-code prefix, such as `+1`.
`country_code`	String	Country code returned by Numverify.
`country_name`	String	Country name returned by Numverify.
`location`	String	Provider-supplied geographic label; it is not proof of the subscriber’s current location.
`carrier`	String	Provider-supplied carrier name.

Invalid numbers can return empty strings and a null line_type; consumers should check valid before using enrichment details.

Errors and statuses

Signal	Meaning
HTTP `422`	`phone_number` is missing, options are invalid, or the service is unavailable.
Provider `success: false`	Numverify returned an API error; Lendflow marks the job failed.
`valid: false`	The provider completed the lookup but did not validate the number. This is a result, not a transport error.
`Started`	Lookup is in progress.
`Success`	Lendflow stored the validation, including an invalid-number result.

FAQ

Is country_code required?

No. It is optional, but it can disambiguate a number that is not already in international format.

Does valid false mean the API call failed?

No. It means Numverify completed the lookup and classified the number as invalid. Check the lifecycle status separately.

Can this block validate a business entity?

No. The current block is available only for individual entities.

​Numverify

​Requirements

​API flow

​Data Orchestration availability and flow

​What the service returns

​Representative response

​Field meanings

​Errors and statuses

​FAQ