Reverse Phone Append API Documentation
Introduction The TDG Reverse Phone API provides a high-fidelity infrastructure for real-time identity recovery and lead validation. This endpoint serves as a professional caller id api and phone number lookup api, allowing enterprises to instantly resolve the individual name and physical address behind any 10-digit number. By integrating our reverse phone lookup api, developers can automate data enrichment and enhance CRM records with carrier-verified signals.
Authentication To access data, you must authenticate your requests using an API Key. By authenticating your requests with an API Key, you ensure secure and authorized access to our data services, allowing you to integrate our comprehensive and reliable data seamlessly into your applications and workflows.
Obtaining an API Key To obtain an API key, please contact our support team to receive your unique x-api-key within 24 hours. [Contact Us]
Including the API Key in Requests When interacting with our data services through APIs, SDKs, or command-line interfaces (CLI), it’s essential to include your API Key in the request. This API Key acts as a unique identifier that authenticates and authorizes your request to access our data.
Managing Your API Key Proper management of your API Key is crucial. Ensure it is kept confidential and not shared publicly or hard-coded in client-side applications. Rotate your keys periodically and revoke them immediately if compromised.
Best Practices Use HTTPS to encrypt API Key transmissions over the network, preventing interception by unauthorized parties. Implement rate limiting and access controls based on API Key usage to manage and monitor access effectively.
Security HTTPS encryption is required for all API transmissions. Request and response bodies are encoded as JSON.
CONVENTIONS
The base URL to send API requests is segregated into 3 categories.
- Lookup: https://api.tdg1.io/v2/lookup
- Append: https://api.tdg1.io/v2/append
- Verify: https://api.tdg1.io/v2/verify
HTTPS is required for all API requests. The TDG API follows RESTful conventions when possible, with most operations performed via POST requests on database resources. Request and response bodies are encoded as JSON.
ENDPOINT SPECIFICATIONS (PHONE LOOKUP)
Phone Lookup Retrieve name and address information associated with a specific phone number. This phone number lookup api is optimized for identity linkage and building comprehensive customer profiles.
HEADERS
- x-api-key (string) | required: Unique key obtained after contacting us.
BODY PARAMS
- Phone (string) | required: 10 digit numeric phone number (without spaces, dashes, or parentheses).
POST: https://testapi.tdg1.io/v3/lookup/phone
Sample Request
curl --location 'https://testapi.tdg1.io/v3/lookup/phone' \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api_key>' \
--data '{
"Phone":"<555-555-5555>"
}'
Sample Response
{
"Name": {
"LName": "Smith",
"FName": "Tom",
"MName": ""
},
"Address": {
"House": "123",
"PreDir": "",
"Street": "Main",
"StrType": "St.",
"PostDir": "",
"AptType": null,
"City": "Anytown",
"State": "FL",
"Zip": "34786",
"Z4": "",
"CNTY": "",
"Deliverable": true,
"ValDate": "5/1/2025"
},
"trace": "c31c2d88-2d57-4dcf-ac12-f5d4e139a8871"
}
IDENTITY VALIDATION (ID VERIFY)
ID Verify Validate the identity of individuals using multiple data points to mitigate fraud. This endpoint serves as a phone validation api and phone verification api, confirming the linkage between names, addresses, emails, and phone numbers.
BODY PARAMS- FName (string) | required if verified: Individual’s first name. (Required if you want to verify FName).
- LName (string) | required if verified: Last name, 20 characters max. (Required if you want to verify LName).
- Address1 (string) | required if verified: Address line 1, 64 characters max. (Required if you want to verify Address).
- Zip (string) | required if verified: 5 digit numeric USPS zip code. (Required if you want to verify Zip).
- Phone (string) | required if verified: 10 digit numeric phone number. (Required if you want to verify Phone).
- Email (string) | required if verified: Email address, 100 characters max. (Required if you want to verify Email).).
POST: https://api.tdg1.io/v2/verify/id
Sample Request
curl --location 'https://api.tdg1.io/v2/verify/id' \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api_key>' \
--data-raw '{
"FName": "<FName>",
"LName": "<LName>",
"Address1": "<Address1>",
"Zip": "<Zip>",
"Phone": "<Phone>",
"Email": "<Email>"
}'
Sample Response
{
"IDScores": {
"ValidAddress": "85",
"ValidPhone": "0",
"ValidEmail": "",
"ValidName": "100",
"ValidZip": "0",
"Deceased": "100",
"NameToPhone": "0",
"NameToEmail": "",
"NameToAddress": "0",
"AddressToPhone": "0",
"AddressToEmail": "",
"PhoneToEmail": "",
"ZipToPhone": "",
"USLocation": "",
"ValidPhone2": "",
"NameToPhone2": "",
"AddressToPhone2": "",
"Phone2ToEmail": "",
"PhoneConfidenceScore": "0",
"Phone2ConfidenceScore": "",
"AddressConfidenceScore": "0",
"ValidCount": "1.8",
"LinkageCount": "0",
"RiskFlagCount": "0",
"ValidationSummary": "FAIL",
"LinkageSummary": "FAIL",
"RiskFlagSummary": "PASS",
"IDVerifyScore": "76"
}
}
DEVELOPER TOOLS (SDK & POSTMAN)
TDG SDK The TDG SDK is an open-source project designed to simplify the process of integrating our data services into your applications. By using the SDK, developers can easily access and utilize our API functionalities, ensuring a smooth and efficient development experience.
- Access: Read Documentation on PyPI
- Run in Postman: [Import TDG Collection]
- Technical Docs: View Documentation
API RESPONSE CODES & COMPLIANCE
HTTPS STATUS CODE | Description |
200 | Successful |
204 | No Records found |
400 | Missing required parameter(s) |
401 | The user is invalid (verify your credentials) |
429 | You have reached the maximum number of transactions allowed |
440 | Too many results. Please refine your search criteria |
500 | System error. Retry search, if failure continues, contact support |
Compliance Notice: The Data Group is not a Consumer Reporting Agency (CRA). Our reverse phone append and identity verification tools are for marketing and lead validation purposes only. Data may not be used for FCRA-regulated purposes, such as determining eligibility for credit, insurance, or employment.
Need Technical Assistance?
