It will receive parameters and provide you with a JSON.
Identity Verification: Confirm a person's identity in verification processes, such as financial services or contracts.
Lost Contact Retrieval: Locate contact information for people whose phone numbers have been lost or changed.
Fraud Prevention: Identify and prevent fraud by verifying the authenticity of contact information provided.
Database Update: Maintain updated customer or contact databases in CRM (Customer Relationship Management) systems.
Market Research: Obtain information about people for market research or surveys.
Besides the number of API calls per month, there are no other limitations.
To use this endpoint you must specify a first and last name. You can also specify a status and a paging in the parameters.
People Information - Endpoint Features
| Object | Description |
|---|---|
FirstName |
[Required] Indicates a first name |
LastName |
[Required] Indicates a Last name |
State |
[Required] Indicates a status |
Page |
[Required] Indicates a page value |
{
"Code": 200,
"Description": "OK",
"Source1": [
{
"FullName": "TERRY LELAND WARD",
"City": "HOUSTON",
"State": "TX",
"Age": "63",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": []
},
{
"FullName": "TERRY LELAND ANDREWS",
"City": "PALOS VERDES PENINSULA",
"State": "CA",
"Age": "69",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": []
},
{
"FullName": "CHRISTOPHER LELAND TERRY",
"City": "SUNDOWN",
"State": "TX",
"Age": "52",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": []
},
{
"FullName": "TERRY LELAND REEVES",
"City": "PORTLAND",
"State": "OR",
"Age": "49",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": [
{
"Email": "[email protected]"
}
]
},
{
"FullName": "MR TERRY LELAND DICKERSON",
"City": "HAYWARD",
"State": "CA",
"Age": null,
"Address": "22 CRYSTAL GATE CMNS HAYWARD, CA 94544-1369",
"Previous_Addresse": "2942 RED LE DR KATY, TX 77494-3204 (8\/19\/2010 - 11\/13\/2012)",
"PeoplePhone": [
{
"PhoneNumber": "2813958077",
"LineType": "LANDLINE\/SERVICES"
},
{
"PhoneNumber": "2818513607",
"LineType": "WIRELESS"
},
{
"PhoneNumber": "2818513670",
"LineType": "WIRELESS"
}
],
"Email": [
{
"Email": "[email protected]"
},
{
"Email": "[email protected]"
},
{
"Email": "[email protected]"
},
{
"Email": "[email protected]"
}
]
},
{
"FullName": "TERRY LELAND BOWERS",
"City": "RIVERSIDE",
"State": "CA",
"Age": "62",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": [
{
"Email": "[email protected]"
}
]
},
{
"FullName": "MR TERRY LELAND CAMPBELL",
"City": "EDMOND",
"State": "OK",
"Age": "80",
"Address": "4640 HILLSIDE LN EDMOND, OK 73025-1273",
"Previous_Addresse": "5050 SWAN LAKE RD BOSSIER CITY, LA 71111-6411 (5\/22\/2007 - 5\/22\/2007)",
"PeoplePhone": [
{
"PhoneNumber": "4055096666",
"LineType": "LANDLINE\/SERVICES"
},
{
"PhoneNumber": "4177253345",
"LineType": "LANDLINE\/SERVICES"
},
{
"PhoneNumber": "4178612881",
"LineType": "WIRELESS"
}
],
"Email": [
{
"Email": "[email protected]"
},
{
"Email": "[email protected]"
}
]
},
{
"FullName": "TERRY STEVEN LELAND",
"City": "HASTINGS",
"State": null,
"Age": "60",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": []
},
{
"FullName": "TERRY LUCAS LELAND",
"City": "FARMINGTON HILLS",
"State": null,
"Age": "73",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": []
},
{
"FullName": "TERRY D LELAND",
"City": "SEATTLE",
"State": null,
"Age": "71",
"Address": null,
"Previous_Addresse": null,
"PeoplePhone": [],
"Email": []
}
]
}
curl --location --request GET 'https://zylalabs.com/api/5070/us+people+data+api/6443/people+information?FirstName=John&LastName=Mc&State=Ohio&Page=1' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
To use this API, users must provide a person's name along with the state they are in. They can also indicate a page location.
The US People Data API is an API designed to provide detailed information about people residing in US. .
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The API typically supports JSON as the primary response format. JSON is widely used due to its simplicity and compatibility with most programming languages and frameworks.
The US People Data API returns detailed personal information, including full names, addresses (street, city, state, postal code), and contact details (phone numbers), formatted for easy integration into applications.
The GET People Information endpoint returns detailed personal data, including full names, cities, states, ages, and contact details. It also provides structured address components and may include previous addresses, phone numbers, and emails when available.
Key fields in the response data include FullName, City, State, Age, Address, Previous_Address, PeoplePhone, and Email. These fields provide essential information for identifying and contacting individuals.
The response data is organized in a JSON format, with each individual's information encapsulated in an object. Each object contains fields for personal details, making it easy to parse and integrate into applications.
Users can specify parameters such as first name, last name, status, and paging options. These parameters help refine search results and manage the volume of data returned.
Users can customize requests by including specific first and last names, selecting a status to filter results, and using paging to navigate through multiple entries. This allows for targeted searches based on user needs.
The data is sourced from various public records and databases, ensuring a comprehensive collection of information. The API aims to provide accurate and up-to-date details about individuals.
Data accuracy is maintained through regular updates and quality checks against reliable sources. The API employs validation processes to ensure the information provided is as accurate as possible.
Typical use cases include identity verification for financial services, retrieving lost contact information, fraud prevention, updating CRM databases, and conducting market research or surveys.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
651ms
Service Level:
100%
Response Time:
583ms
Service Level:
100%
Response Time:
666ms
Service Level:
100%
Response Time:
5,476ms
Service Level:
100%
Response Time:
2,956ms
Service Level:
100%
Response Time:
633ms
Service Level:
100%
Response Time:
60ms
Service Level:
100%
Response Time:
1,600ms
Service Level:
100%
Response Time:
3,155ms
Service Level:
100%
Response Time:
6,817ms
Service Level:
100%
Response Time:
437ms
Service Level:
100%
Response Time:
452ms
Service Level:
100%
Response Time:
1,377ms
Service Level:
100%
Response Time:
1,037ms
Service Level:
100%
Response Time:
1,049ms
Service Level:
67%
Response Time:
1,982ms
Service Level:
100%
Response Time:
309ms
Service Level:
100%
Response Time:
2,183ms
Service Level:
100%
Response Time:
424ms
Service Level:
100%
Response Time:
2,242ms