The API will receive latitude, longitude of the location you want to query. Also it will receive date and hour and you'll get a list of incidents.
City Planning: Urban planners can utilize the Crime Data API to analyze crime trends in various neighborhoods, aiding in the development of safer urban environments and efficient allocation of resources.
Real Estate Research: Real estate agents and prospective homebuyers can use the API to assess the safety of neighborhoods before making property investments, enhancing decision-making and peace of mind.
Community Policing: Law enforcement agencies can employ the API to monitor crime hotspots, strategize patrols, and allocate resources effectively, contributing to proactive crime prevention and community safety.
Travel Safety: Travelers can access crime incident data through the API to make informed decisions about destination choices, accommodation selections, and travel routes, promoting personal safety during journeys.
Academic Research: Researchers and academics can utilize the API to study crime patterns, investigate sociodemographic correlates, and develop insights into the underlying factors influencing criminal behavior, contributing to advancements in criminology and public policy.
This is a request of the Crime Data API access point get crime incidents for a specific location.
Distance in MILES. Example: 5mi, 10mi, etc.
Object | Description |
---|---|
lon |
[Required] Longitude |
distance |
[Required] Distance |
datetime_ini |
[Required] Initial date |
datetime_end |
[Required] End date |
lat |
[Required] Latitude |
{
"total_incidents": 2,
"total_pages": 1,
"incidents": [
{
"city_key": "AUS",
"incident_code": "20191010131",
"incident_date": "2019-04-11T01:40:00.000Z",
"incident_type": "Alcohol-related offense",
"incident_official_type": "DWI",
"incident_source_name": "Austin_Police_Department_Crime_Reports",
"incident_description": "DWI at 816 LAVACA ST",
"incident_latitude": 30.27146322,
"incident_longitude": -97.74426176,
"incident_address": "816 LAVACA ST"
},
{
"city_key": "AUS",
"incident_code": "20183640046",
"incident_date": "2018-12-30T02:48:00.000Z",
"incident_type": "Alcohol-related offense",
"incident_official_type": "DWI",
"incident_source_name": "Austin_Police_Department_Crime_Reports",
"incident_description": "DWI at W 9TH ST / LAVACA ST",
"incident_latitude": 30.27154076,
"incident_longitude": -97.74415195,
"incident_address": "W 9TH ST / LAVACA ST"
}
]
}
curl --location --request GET 'https://zylalabs.com/api/3976/crime+data+api/4728/crime-incidents?lon=-87.6472903440513&distance=5mi&datetime_ini=2024-01-01T00:00:00.000Z&datetime_end=2024-02-01T00:00:00.000Z&lat=41.9777476245164' --header 'Authorization: Bearer YOUR_API_KEY'
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 Crime Data API REST 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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
We use the FBI-NIBRS standard (more details below in the FBI-NIBRS section) and we offer the following output attributes for each incident.
US, LATAM: Sao Paulo (Brazil), Rio de Janeiro (Brazil), Buenos Aires (Argentina), Santiago (Chile), Montevideo (Uruguay), León (Mexico) and others.
1- Crime Data API: To get instant crime data around a specific location. 2- Crime Map API: To enrich your maps with our crime maps overlays. 3- Embeddable Crime Map: To embed our crime maps into your solution. 4- Sex Offenders API: To search sex offenders for background checks. 5- 911 Calls API: To get instant near real-time 911 cal
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
4,289ms
Service Level:
100%
Response Time:
252ms
Service Level:
100%
Response Time:
816ms
Service Level:
100%
Response Time:
733ms
Service Level:
100%
Response Time:
216ms
Service Level:
100%
Response Time:
3,042ms
Service Level:
100%
Response Time:
3,451ms
Service Level:
100%
Response Time:
317ms
Service Level:
100%
Response Time:
412ms
Service Level:
100%
Response Time:
474ms
Service Level:
100%
Response Time:
2,073ms
Service Level:
100%
Response Time:
447ms
Service Level:
100%
Response Time:
567ms
Service Level:
100%
Response Time:
412ms
Service Level:
100%
Response Time:
120ms
Service Level:
100%
Response Time:
470ms
Service Level:
100%
Response Time:
292ms