Phone Validator
Validate and format a phone number (line type, carrier, region). Check and normalize the phone numbers you already have: valid or not, line type, carrier, E.164 format.
Credits: 1 search credit per validation. Lookups that find nothing cost nothing. See Pricing and limits.
Inputs and options
Input: phone (Phone number)
Optional: country_code (Country code (ISO-2, optional)).
This tool has no options.
Try one value
Code
The call returns the result as a VARIANT (example values, shortened):
Code
status is found, not_found, invalid or error; results holds the output columns and data the complete
Tomba record.
Run it over a table
Create a small table to try it (or use one of yours, after granting the app access):
Code
Run the tool, then read the results:
Code
Signature: validate_phones(input_table STRING, phone_column STRING, output_table STRING, max_rows INT DEFAULT 100000, country_code_column STRING DEFAULT '')
Start with a small max_rows (like 100) to check the match rate on your
data, then run the whole table, in the background if
it is large.
Output columns
Each row starts with INPUT_<name> columns (your values, unchanged) and then has:
VALID, E164_FORMAT, INTL_FORMAT, LOCAL_FORMAT, COUNTRY_CODE, LINE_TYPE, CARRIER, REGION, TIMEZONES, followed by the common columns
(LOOKUP_STATUS, CREDITS, DATA, SOURCE, …).
Tips
- The country column is optional but helps with local-format numbers (
030 1234567). It takes a column name, not a value like'US'. - Store
E164_FORMATin your CRM: it is the standard international format.