[{"year":2024,"race":"White","total_incidents":308}]
curl --location --request POST 'https://pr213-testing.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://pr213-testing.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"}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the US Police Shootings Data API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
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.
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, 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