The US Police Shootings Data API provides developers and researchers with in-depth statistics on fatal police shootings in the United States, categorized by race and year. It enables efficient data retrieval through targeted endpoints with filtering options, ensuring optimized access to specific datasets and facilitating detailed trend analysis over time.
[{"year":2024,"race":"White","total_incidents":308}]
curl --location --request POST 'https://zylalabs.com/api/6080/us+police+shootings+data+api/8278/get+police+shooting+stats+by+race+and+year' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"race":"Required","year":"Required"}'
[{"Gun":545,"Knife":199,"Vehicle":46,"Toy weapon":19,"Unarmed":23,"Other":44,"Unknown":101}]
curl --location --request POST 'https://zylalabs.com/api/6080/us+police+shootings+data+api/8279/obtain+dead+stats+by+weapon+type' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"year":"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 Police Shootings Data API provides structured statistical data on fatal police shootings in the United States, categorized by race and year.
The API offers targeted endpoints with filtering options, allowing users to efficiently retrieve specific datasets based on criteria such as race and year.
The API does not specify the frequency of updates, so users should verify the timeliness of the data before relying on it for analysis.
Yes, the API is designed to facilitate detailed trend analysis over time by providing access to historical data segmented by race and year.
Potential use cases include academic research, policy analysis, law enforcement studies, and public awareness campaigns focused on police shootings and racial disparities.
The "get police shooting stats by race and year" endpoint returns statistics on fatal police shootings categorized by race and year. The "obtain dead stats by weapon type" endpoint provides data on the number of fatalities by weapon type used in police shootings.
The response from "get police shooting stats by race and year" includes fields like "year," "race," and "total_incidents." The "obtain dead stats by weapon type" endpoint returns weapon types as keys with corresponding fatality counts as values.
The "get police shooting stats by race and year" endpoint accepts parameters for "race" (white, black, hispanic, other, unknown) and "year" (2017-2024). The "obtain dead stats by weapon type" endpoint does not require additional parameters.
The response data is structured as an array of JSON objects. Each object contains key-value pairs representing the year, race, and total incidents for the first endpoint, or weapon types and their corresponding fatality counts for the second endpoint.
The API aggregates data from various law enforcement agencies and public records related to police shootings in the United States, ensuring a comprehensive dataset for analysis.
Users can customize requests by specifying the desired race and year for the "get police shooting stats by race and year" endpoint, allowing for tailored data retrieval based on specific interests or research needs.
Typical use cases include analyzing racial disparities in police shootings, evaluating the effectiveness of law enforcement policies, and conducting academic research on public safety and community relations.
Users can analyze trends over time by comparing data across different years and races, or assess the impact of weapon types on fatal incidents, enabling informed discussions and policy recommendations.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
173ms
Service Level:
100%
Response Time:
2,429ms
Service Level:
100%
Response Time:
17ms
Service Level:
100%
Response Time:
105ms
Service Level:
100%
Response Time:
3,869ms
Service Level:
100%
Response Time:
299ms
Service Level:
100%
Response Time:
219ms
Service Level:
100%
Response Time:
935ms
Service Level:
100%
Response Time:
546ms
Service Level:
100%
Response Time:
83ms