Find detailed hospital information by name, city, state, ZIP code, or eich county, including address, contact, care type, ownership, and bed count.
The US Hospitals Data API provides a comprehensive and reliable way to access detailed information about hospitals across the United States, allowing you to integrate critical hospital data into your applications, platforms, and systems. This API is designed to deliver highly relevant information with flexible search parameters, allowing users to search for hospitals by name, city, state, zip code, or county, making it easy to obtain specific results for specific needs.
A key advantage of the Hospitals API is its adaptability. Users can refine their searches using parameters such as geographic coordinates (latitude and longitude ranges) to find hospitals within specific areas, or filter by county or state to narrow down results. The API also supports partial name matching, allowing for more flexible search queries. For premium users, it offers advanced controls such as result limits and offsets to tailor data retrieval to specific needs.
This API is ideal for developers creating healthcare platforms, emergency response systems, research databases, or patient information portals. It allows users to locate and evaluate hospitals based on their location, the services they offer, their capacity, and other relevant factors, improving access to healthcare and decision-making processes.
In short, the US Hospitals Data API is a versatile and powerful resource for accessing accurate and detailed information about hospitals across the country. It simplifies the hospital search process, provides detailed data about facilities, and enables informed decisions about healthcare, research, and planning.
Hospital Finder - Endpoint Features
| Object | Description |
|---|---|
name |
Optional Name of the hospital you wish to search for. Partial matches are accepted. |
city |
[Required] City where the hospital is located. |
state |
Optional State where the hospital is located. |
zipcode |
Optional Postal code of the hospital's location. |
county |
Optional County where the hospital is located. |
min_latitude |
Optional Minimum latitude coordinate. |
max_latitude |
Optional Maximum latitude coordinate. |
min_longitude |
Optional Minimum longitude coordinate. |
max_longitude |
Optional Maximum longitude coordinate. |
limit |
Optional Number of results to return. The default value is 5. The maximum is 100. |
offset |
Optional Number of results to skip. The default value is 0. |
{"Example Response":"No response example available for now."}
curl --location --request GET 'https://zylalabs.com/api/10535/us+hospitals+data+api/20097/hospital+finder?city=los angeles' --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.
The Hospital Finder endpoint returns detailed information about hospitals, including their name, address, contact information, care types offered, ownership status, and bed count.
Key fields in the response data include hospital name, address, phone number, care type, ownership type, and total bed count, providing a comprehensive overview of each facility.
Users can search using parameters such as hospital name, city, state, ZIP code, county, and geographic coordinates (latitude and longitude) to refine their search results.
The response data is structured in a JSON format, with each hospital's details encapsulated in an object, making it easy to parse and utilize in applications.
The data is sourced from reliable healthcare databases and government health agencies, ensuring that the information is accurate and up-to-date.
Typical use cases include developing healthcare applications, emergency response systems, patient information portals, and research databases that require hospital information.
Users can customize requests by combining multiple parameters, such as searching for hospitals in a specific city while filtering by care type or ownership status.
If the search yields partial or empty results, users can broaden their search criteria or check for spelling errors in the hospital name or location parameters.
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:
455ms
Service Level:
100%
Response Time:
327ms
Service Level:
100%
Response Time:
1,675ms
Service Level:
100%
Response Time:
1,275ms
Service Level:
100%
Response Time:
1,296ms
Service Level:
100%
Response Time:
1,368ms
Service Level:
100%
Response Time:
1,368ms
Service Level:
100%
Response Time:
4,636ms
Service Level:
100%
Response Time:
1,162ms
Service Level:
100%
Response Time:
1,757ms
Service Level:
100%
Response Time:
260ms
Service Level:
100%
Response Time:
80ms
Service Level:
100%
Response Time:
458ms
Service Level:
100%
Response Time:
3,478ms
Service Level:
99%
Response Time:
3,529ms
Service Level:
100%
Response Time:
3,133ms
Service Level:
100%
Response Time:
163ms
Service Level:
100%
Response Time:
1,451ms
Service Level:
100%
Response Time:
1,035ms
Service Level:
100%
Response Time:
2,418ms