The US Haunted Places API enables developers and researchers to retrieve curated data about haunted locations across U.S. states. Rather than exposing all data in a single request, the API is designed with modular endpoints that support state-level queries, place-level lookups, and paranormal phenomena descriptions. This design allows developers to: Retrieve a list of states that have haunted places. Query haunted places within a given state. Fetch details about what people reportedly see or experience at a particular location. It’s useful for building paranormal research apps, tourism platforms, or even for spooky seasonal projects like Halloween-themed mobile apps.
[
{
"states": [
"Alabama",
"Alaska",
"Arizona",
"Arkansas",
"California",
"Colorado",
"Connecticut",
"Delaware",
"Florida",
"Georgia",
"Hawaii",
"Idaho",
"Illinois",
"Indiana",
"Iowa",
"Kansas",
"Kentucky",
"Louisiana",
"Maine",
"Maryland",
"Massachusetts",
"Michigan",
"Minnesota",
"Mississippi",
"Missouri",
"Montana",
"Nebraska",
"Nevada",
"New Hampshire",
"New Jersey",
"New Mexico",
"New York",
"North Carolina",
"North Dakota",
"Ohio",
"Oklahoma",
"Oregon",
"Pennsylvania",
"Rhode Island",
"South Carolina",
"South Dakota",
"Tennessee",
"Texas",
"Utah",
"Vermont",
"Virginia",
"Washington",
"West Virginia",
"Wisconsin",
"Wyoming"
]
}
]
curl --location --request POST 'https://zylalabs.com/api/9845/us+haunted+places+api/18493/get+list+of+states+with+haunted+places' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[
{
"state": [
"Utah"
],
"places": [
"The Rio Grande Depot"
]
}
]
curl --location --request POST 'https://zylalabs.com/api/9845/us+haunted+places+api/18494/get+haunted+places+in+specific+state' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
[
{
"State": "Utah",
"Place Names": "The Rio Grande Depot",
"What People See": "A woman in a purple dress and hat, who was struck by a train and killed while retrieving her dropped engagement ring from the tracks. It is said she can also be heard singing from the women's restrooms."
}
]
curl --location --request POST 'https://zylalabs.com/api/9845/us+haunted+places+api/18495/get+details+of+paranormal+phenomena+at+specific+place' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"place":"Required"}'
| 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.
You can use the state-level query endpoint to retrieve a list of haunted places within a specified state. This allows you to focus your search based on geographic location.
The API can be used to build various applications such as paranormal research tools, tourism platforms highlighting haunted sites, or Halloween-themed mobile apps that provide spooky content to users.
The API returns data in a structured format, typically JSON, including fields such as state name, place name, and descriptions of reported paranormal experiences, allowing for easy integration into applications.
The US Haunted Places API provides structured data about haunted locations in the United States, including lists of states with haunted places, details of haunted places within specific states, and descriptions of paranormal phenomena reported at those locations. This data is organized in a modular format, allowing for targeted queries.
Each endpoint returns structured data in JSON format. The "get list of states" endpoint provides a list of states with haunted places. The "get haunted places in specific state" endpoint returns names of haunted locations within a specified state. The "get details of paranormal phenomena" endpoint offers descriptions of reported experiences at a specific place.
Key fields include "states" for the list of states, "places" for haunted locations within a state, and "What People See" for descriptions of paranormal phenomena. Each response is organized to provide clear and relevant information based on the endpoint used.
The primary parameter is the state name for the "get haunted places in specific state" endpoint, allowing users to specify which state's haunted locations they want to query. For the "get details of paranormal phenomena," the place name is required to retrieve specific experiences associated with that location.
The response data is organized in a structured JSON format. Each endpoint's response contains relevant fields, such as state names, place names, and detailed descriptions of paranormal phenomena, making it easy to parse and utilize in applications.
The "get list of states" endpoint provides a comprehensive list of states with haunted places. The "get haunted places in specific state" endpoint lists haunted locations in a chosen state. The "get details of paranormal phenomena" endpoint offers insights into specific experiences reported at those locations.
Users can integrate the returned data into applications by parsing the JSON responses. For example, they can display haunted locations on a map, create detailed profiles of each site, or generate content for tourism platforms based on reported experiences.
Typical use cases include developing apps for paranormal research, creating tourism guides that highlight haunted sites, and building Halloween-themed content that engages users with spooky stories and experiences from various locations.
Data accuracy is maintained through careful curation and sourcing from reputable accounts of paranormal experiences. Regular updates and quality checks ensure that the information remains relevant and trustworthy for users seeking insights into haunted locations.
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:
67ms
Service Level:
100%
Response Time:
36ms
Service Level:
100%
Response Time:
52ms
Service Level:
100%
Response Time:
3,061ms
Service Level:
100%
Response Time:
56ms
Service Level:
40%
Response Time:
124ms
Service Level:
100%
Response Time:
7,246ms
Service Level:
100%
Response Time:
5,476ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
11,295ms
Service Level:
100%
Response Time:
743ms
Service Level:
100%
Response Time:
452ms
Service Level:
100%
Response Time:
479ms
Service Level:
50%
Response Time:
176ms
Service Level:
100%
Response Time:
2,224ms
Service Level:
100%
Response Time:
1,779ms
Service Level:
100%
Response Time:
250ms
Service Level:
100%
Response Time:
130ms
Service Level:
100%
Response Time:
537ms
Service Level:
100%
Response Time:
3,656ms