Nearby Incidents API

Get nearby incidents without a raw incident dump.

Some products need a fresh local pulse next to long-term neighborhood risk. CrimeScore separates the score API from a bounded recent-activity endpoint so teams can use each signal honestly.

recent crime activity APIcrime incident APIcrime data APInearby incidents API24 hour crime API
Open Playground Nearby Incidents API

What the endpoint is for

The nearby incidents route returns sanitized, normalized incident context near a coordinate. It is useful when a product needs a short-term local signal, such as a 24-hour pulse around a selected area.

It is not a bulk export, raw source feed, emergency response tool, or public safety dispatch system.

  • Coordinate-based lookup
  • Rolling 24-hour context
  • Sanitized labels and categories
  • Strict radius and result limits

Why it is separate from the score

A long-term neighborhood score should not swing because of one recent incident. Keeping recent activity separate makes the product easier to explain.

Use the score for baseline neighborhood context. Use recent activity when a current local pulse helps the user understand what is happening nearby.

FAQ

Common questions

Is this raw crime incident data?

No. The endpoint returns bounded, sanitized recent activity context and omits raw payloads, media, user data, and source identifiers.

Is the recent activity endpoint public?

No. Live nearby incident calls require an API key. Public pages show static examples and link to the playground.

Can developers test it?

Yes. Developers can review the OpenAPI docs and run authenticated examples in the CrimeScore playground.