The US Serial Killer API allows users to retrieve lists of U.S. states and detailed statistics such as total victims, best-known serial killers, and more. Each data point can be queried via dedicated endpoints, enabling granular exploration, filtering, and comparative analytics. This API is particularly useful for criminology researchers, journalists, educators, and data analysts who need structured, on-demand access to crime statistics in the U.S.
{"states":["California","Texas","Florida","Illinois","New York","Ohio","Pennsylvania","Michigan","Georgia","Washington","Missouri","Indiana","Louisiana","North Carolina","Virginia","New Jersey","Maryland","Kentucky","Tennessee","Massachusetts","Oklahoma","Alabama","South Carolina","Arizona","Kansas","Oregon","Colorado","Arkansas","Connecticut","Wisconsin","Nevada","Mississippi","Utah","Nebraska","Minnesota","New Mexico","Alaska","Iowa","Montana","Idaho","West Virginia","Maine","Wyoming","Rhode Island","Delaware","New Hampshire","Hawaii","North Dakota","Vermont","South Dakota"]}
curl --location --request POST 'https://zylalabs.com/api/6677/us+serial+killer+api/9855/get+us+state+with+serial+killers' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"state":"California","total_known_serial_killers_victims":1777}
curl --location --request POST 'https://zylalabs.com/api/6677/us+serial+killer+api/9856/get+total+known+serial+killers+victims' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
{"state":"California","best_known_serial_killer":"The Zodiac Killer"}
curl --location --request POST 'https://zylalabs.com/api/6677/us+serial+killer+api/9857/get+best-known+serial+killer+by+state' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
{"name":"The Zodiac Killer","best_known_killers_victims":37}
curl --location --request POST 'https://zylalabs.com/api/6677/us+serial+killer+api/9858/get+best-known+killer%27s+victims+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"name":"Required"}'
{"serial_killer_name":"The Zodiac Killer","final_status":"Never found"}
curl --location --request POST 'https://zylalabs.com/api/6677/us+serial+killer+api/9859/get+best-known+killer%27s+final+status' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"name":"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.
The US Serial Killer API provides access to structured statistics about serial killers by U.S. state, including total victims, best-known serial killers, and other relevant crime data.
This API is particularly useful for criminology researchers, journalists, educators, and data analysts who require structured, on-demand access to crime statistics in the U.S.
The API allows for granular exploration and filtering of data through dedicated endpoints, enabling users to compare statistics based on various parameters.
Yes, the US Serial Killer API enables users to compare serial killer statistics across different states, allowing for comprehensive analysis and insights.
To use the US Serial Killer API, you need to have a basic understanding of API requests, familiarity with JSON format, and the ability to handle HTTP requests to access the data.
Each endpoint returns specific data related to serial killers in the U.S. For example, the "get total known serial killers victims" endpoint returns the total number of victims for a specified state, while the "get best-known serial killer by state" endpoint provides the name of the most infamous serial killer in that state.
Key fields include "state" for the state name, "total_known_serial_killers_victims" for victim counts, "best_known_serial_killer" for the killer's name, and "final_status" for the killer's status. Each endpoint has tailored fields relevant to the data it provides.
The response data is structured in JSON format, with each endpoint returning a clear key-value pair. For instance, the response from "get total known serial killers victims" includes the state and the corresponding victim count, making it easy to parse and utilize.
Each endpoint provides distinct information: the list of states, total victims per state, best-known serial killers by state, victims' names for specific killers, and the final status of those killers. This allows for comprehensive data retrieval based on user needs.
Users can specify a U.S. state or a serial killer's name as parameters. For example, when using "get total known serial killers victims," you must provide a state name, while "get best-known killer's victims by name" requires the killer's name.
Users can customize requests by selecting specific states or serial killer names as parameters. This allows for targeted queries, such as retrieving victim statistics for a particular state or details about a specific serial killer.
Typical use cases include academic research in criminology, journalism focused on crime statistics, educational projects analyzing serial killer trends, and data analysis for public safety assessments. The structured data supports various analytical needs.
Data accuracy is maintained through rigorous sourcing from credible crime databases and historical records. Regular updates and quality checks ensure that the information remains reliable and reflects the most current statistics available.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
99%
Response Time:
1,045ms
Service Level:
100%
Response Time:
1,476ms
Service Level:
100%
Response Time:
52ms
Service Level:
100%
Response Time:
8,683ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
6,970ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
63ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
5,659ms
Service Level:
100%
Response Time:
323ms
Service Level:
100%
Response Time:
1,610ms
Service Level:
100%
Response Time:
1,552ms
Service Level:
100%
Response Time:
229ms
Service Level:
100%
Response Time:
110ms
Service Level:
100%
Response Time:
697ms
Service Level:
100%
Response Time:
429ms
Service Level:
100%
Response Time:
276ms
Service Level:
100%
Response Time:
692ms
Service Level:
100%
Response Time:
1,269ms