Crime Score API

API ID 12945

CrimeScore returns higher-is-safer Safety Scores, grades, component scores, model factors, and nearby incident context for US real estate, PropTech, and location products.

1,867 ms avg response

API Documentation

Endpoints

Request
Returns a higher-is-safer neighborhood Safety Score, A-F grade, four component scores, resolved Census geography, and release metadata for the supplied US coordinates.
Endpoint ID: 25838
GET https://api-sneakers-database.zylalabs.com/api/12945/crime+score+api/25838/get+safety+score
INPUT PARAMETERS

Get Safety Score — Endpoint Features

Object Description
lat Required NYC latitude
lng Required NYC longitude

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

lat
lng
API EXAMPLE RESPONSE
JSON
{
    "geoid": "360610031002",
    "resolved": {
        "lat": 40.7128,
        "lng": -74.006,
        "state": "NY",
        "county_fips": "061"
    },
    "safety_score": 94,
    "safety_grade": "A",
    "components": {
        "property_crime": 93,
        "violent_crime": 92,
        "disorder": 48,
        "frequency": 93
    },
    "data": {
        "census_vintage": "2024",
        "model_version": "2.0"
    }
}
Get Safety Score — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12945/crime+score+api/25838/get+safety+score?lat=40.7128&lng=-74.006' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Returns sanitized, normalized recent incident context around US coordinates. Control the bounded search with radius_m, hours, and limit. Available on Pro and Enterprise.
Endpoint ID: 25839
GET https://api-sneakers-database.zylalabs.com/api/12945/crime+score+api/25839/get+nearby+incidents
INPUT PARAMETERS

Get Nearby Incidents — Endpoint Features

Object Description
lat Required NYC latitude
lng Required NYC longitude
radius_m Optional Search radius in meters, 100 to 16000.
hours Optional Lookback window in hours, 1 to 24.
limit Optional Maximum results, 1 to 100.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

lat
lng
radius_m
hours
limit
API EXAMPLE RESPONSE
JSON
{
    "capturedAt": "2026-07-20T22:28:52.512Z",
    "center": {
        "lat": 40.7128,
        "lng": -74.006
    },
    "radius_m": 5000,
    "hours": 24,
    "limit": 25,
    "count": 25,
    "scannedCells": 1,
    "incidents": [
        {
            "id": "crimescore_73db130dc7e744b7fdb6d465",
            "label": "Fire activity · Newyorkcity area",
            "categories": [
                "Fire"
            ],
            "latitude": 40.754625,
            "longitude": -74.001825,
            "cityCode": "us-ny-newyorkcity",
            "reportedAt": "2026-07-20T15:23:31.000Z",
            "level": 0,
            "rank": 12,
            "distance_m": 4664
        },
        {
            "id": "crimescore_3d64abe813d0a609345009db",
            "label": "Police activity · NYC area",
            "categories": [
                "Police Related"
            ],
            "latitude": 40.715565989127,
            "longitude": -74.003010007554,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T15:23:24.000Z",
            "level": 2,
            "rank": 907,
            "distance_m": 398
        },
        {
            "id": "crimescore_b900864d8baacc659f282b88",
            "label": "Traffic incident · NYC area",
            "categories": [
                "Traffic Related"
            ],
            "latitude": 40.689942008206,
            "longitude": -73.981558035119,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T15:19:55.000Z",
            "level": 1,
            "rank": 151,
            "distance_m": 3272
        },
        {
            "id": "crimescore_b5b385b32d4a966a1ad0e788",
            "label": "Fire activity · NYC area",
            "categories": [
                "Fire"
            ],
            "latitude": 40.713311,
            "longitude": -73.982807,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T15:04:02.000Z",
            "level": 0,
            "rank": 246,
            "distance_m": 1956
        },
        {
            "id": "crimescore_560c950edf0c2d2e3eb00617",
            "label": "Incident activity · Hudson area",
            "categories": [],
            "latitude": 40.720153,
            "longitude": -74.041583,
            "cityCode": "us-nj-hudson",
            "reportedAt": "2026-07-20T14:54:01.000Z",
            "level": 0,
            "rank": 326,
            "distance_m": 3108
        },
        {
            "id": "crimescore_53cd9f4ce3e9a5ef66ebb239",
            "label": "Property incident · NYC area",
            "categories": [
                "Robbery / Theft"
            ],
            "latitude": 40.7158379,
            "longitude": -73.9872649,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T14:50:21.000Z",
            "level": 0,
            "rank": 359,
            "distance_m": 1615
        },
        {
            "id": "crimescore_74eebde8158abce46eb9f524",
            "label": "Fire activity · NYC area",
            "categories": [
                "Fire"
            ],
            "latitude": 40.683301,
            "longitude": -73.966147,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T14:48:30.000Z",
            "level": 0,
            "rank": 366,
            "distance_m": 4695
        },
        {
            "id": "crimescore_2072b57c7bc1629199031cb2",
            "label": "Property incident · Hudson area",
            "categories": [
                "Robbery / Theft"
            ],
            "latitude": 40.728363,
            "longitude": -74.031884,
            "cityCode": "us-nj-hudson",
            "reportedAt": "2026-07-20T14:47:00.000Z",
            "level": 0,
            "rank": 371,
            "distance_m": 2784
        },
        {
            "id": "crimescore_9c549485d3e36419ba2232e3",
            "label": "Traffic incident · NYC area",
            "categories": [
                "Traffic Related"
            ],
            "latitude": 40.708141,
            "longitude": -73.999467,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T14:40:27.000Z",
            "level": 0,
            "rank": 406,
            "distance_m": 756
        },
        {
            "id": "crimescore_9cc7818c195575e1ecdea109",
            "label": "Hazardous Condition activity · NYC area",
            "categories": [
                "Hazardous Condition"
            ],
            "latitude": 40.72266,
            "longitude": -73.984905,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T14:38:30.000Z",
            "level": 0,
            "rank": 433,
            "distance_m": 2089
        },
        {
            "id": "crimescore_fc0eec5b65327a65054b512e",
            "label": "Harassment activity · NYC area",
            "categories": [
                "Harassment"
            ],
            "latitude": 40.71877410000002,
            "longitude": -74.0022896,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T14:29:12.000Z",
            "level": 0,
            "rank": 479,
            "distance_m": 734
        },
        {
            "id": "crimescore_004ddad3924bd01f0b7b2b04",
            "label": "Police activity · NYC area",
            "categories": [
                "Police Related"
            ],
            "latitude": 40.72042,
            "longitude": -74.01399,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T14:27:19.000Z",
            "level": 1,
            "rank": 822,
            "distance_m": 1082
        },
        {
            "id": "crimescore_c7b2e5a18f47a16abf7f8e51",
            "label": "Gun-related report · NYC area",
            "categories": [
                "Weapon"
            ],
            "latitude": 40.693345773357,
            "longitude": -73.990858594883,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T14:20:38.000Z",
            "level": 1,
            "rank": 532,
            "distance_m": 2512
        },
        {
            "id": "crimescore_40e6142f8230183a7145c05b",
            "label": "Incident activity · NYC area",
            "categories": [],
            "latitude": 40.751831592411,
            "longitude": -73.984274358481,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:43:41.000Z",
            "level": 0,
            "rank": 681,
            "distance_m": 4710
        },
        {
            "id": "crimescore_a696b0ed1854dd89560ece7b",
            "label": "Fire activity · NYC area",
            "categories": [
                "Fire"
            ],
            "latitude": 40.707846,
            "longitude": -73.956176,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:42:30.000Z",
            "level": 0,
            "rank": 693,
            "distance_m": 4236
        },
        {
            "id": "crimescore_a4ca63846ea926dc0524d4fe",
            "label": "Fire activity · NYC area",
            "categories": [
                "Fire"
            ],
            "latitude": 40.674979,
            "longitude": -74.003432,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:19:30.000Z",
            "level": 0,
            "rank": 785,
            "distance_m": 4211
        },
        {
            "id": "crimescore_7a6b11d5a9045343e8de62a4",
            "label": "Traffic incident · NYC area",
            "categories": [
                "Traffic Related"
            ],
            "latitude": 40.673884628654,
            "longitude": -73.999540654011,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:19:25.000Z",
            "level": 0,
            "rank": 798,
            "distance_m": 4361
        },
        {
            "id": "crimescore_16ed6309cca8a8423690c121",
            "label": "Police activity · NYC area",
            "categories": [
                "Police Related"
            ],
            "latitude": 40.749783306732,
            "longitude": -73.987756703975,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:15:14.000Z",
            "level": 0,
            "rank": 792,
            "distance_m": 4390
        },
        {
            "id": "crimescore_6915f3f5547c8a0b8709030a",
            "label": "Hazardous Condition activity · NYC area",
            "categories": [
                "Hazardous Condition"
            ],
            "latitude": 40.69581689999999,
            "longitude": -73.9806598,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:13:45.000Z",
            "level": 0,
            "rank": 799,
            "distance_m": 2851
        },
        {
            "id": "crimescore_d89a745bae7b429501d382c4",
            "label": "Fire activity · NYC area",
            "categories": [
                "Fire"
            ],
            "latitude": 40.715874,
            "longitude": -74.003609,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:07:38.000Z",
            "level": 1,
            "rank": 913,
            "distance_m": 397
        },
        {
            "id": "crimescore_886b8b8c0dd57cc6e1b14c86",
            "label": "Assault report · NYC area",
            "categories": [
                "Assault / Fight"
            ],
            "latitude": 40.73987226200006,
            "longitude": -73.98660044399998,
            "cityCode": "nyc",
            "reportedAt": "2026-07-20T13:00:26.000Z",
            "level": 1
        }
    ],
    "_note": "Response truncated for documentation purposes"
}
Get Nearby Incidents — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12945/crime+score+api/25839/get+nearby+incidents?lat=40.7128&lng=-74.006&radius_m=5000&hours=24&limit=25' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

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 Score API simply include your bearer token in the Authorization header.

Headers
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 🎉)

🚀 Enterprise Plan

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring
zeiss-logo amazon-logo zoom-logo decathlon-logo

Trusted by leading companies

Overview

CrimeScore returns higher-is-safer Safety Scores, grades, component scores, model factors, and nearby incident context for US real estate, PropTech, and location products.

Crime Score API FAQs

/score returns a Safety Score, grade, resolved geography, four component scores, and release metadata. /score/details adds local model factors. /incidents/nearby returns bounded recent incident context around coordinates.

Safety_score is a 0-100 value where higher is safer. safety_grade is the matching A-F grade. components contains the four component scores, resolved contains location details, and data contains release metadata.

Responses use JSON. Coordinate score responses include a Census block-group geoid and resolved coordinates. ZIP responses include zcta, resolved.zip, and block_group_count metadata.

The score-details endpoint returns a selected overall or component Safety Score and grade plus contributors with a label, direction, and relative impact. Model-factor influence is not certainty or causation.

/score and /score/details accept either lat and lng together or a 5-digit zip, using exactly one location mode. /incidents/nearby requires lat and lng.

The Crime Score API aggregates data from various public safety and crime reporting sources across the United States. Data accuracy is maintained through regular updates and normalization processes to ensure consistency and reliability.

Common uses include real estate and PropTech products, property and neighborhood pages, location intelligence, portfolio research, embedded safety maps, and internal property analysis. Responsible-use limitations apply.

A Safety Score is a relative neighborhood estimate where higher values are safer and A is the best grade. It is not a property-specific or person-specific prediction and does not guarantee that an incident will or will not occur.

The Crime Score API provides crime data and safety scores for locations across the entire United States, including urban, suburban, and rural areas. Users can obtain scores for specific coordinates within these regions.

Nearby requests require lat and lng. Set radius_m from 100 to 16000, hours from 1 to 24, and limit from 1 to 100. Defaults are 5000 meters, 24 hours, and 25 results.

Safety grades use the same higher-is-safer convention: A is 80-100, B is 60 to below 80, C is 40 to below 60, D is 20 to below 40, and F is below 20.

Nearby incidents are constrained to the requested coordinates, radius, lookback window of up to 24 hours, and result limit. Returned records are sanitized and normalized recent context.

Nearby incident records can include an id, label, categories, coordinates, reportedAt timestamp, and distance_m. CrimeScore does not expose raw source payloads, media, user data, or internal source identifiers.

Scores use a shared release, component definitions, grade thresholds, and Census geography. Recent-incident refresh timing is separate from the score-data release.

The components object contains violent_crime, property_crime, disorder, and frequency. Every component uses the same 0-100 higher-is-safer convention as the overall score.

Model factors are available from /score/details. direction is raises_safety_score or lowers_safety_score, and impact is high, medium, or low. They describe relative model influence, not certainty or a causal relationship.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
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.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs