BikeWise API v2

Tools (6)

Extracted live via the executor SDK.

• incidents.getVersionIncidentsFormat

  If you’d like more detailed information about bike incidents, use this endpoint. For mapping, locations is probably a better bet.

  Notes on location searching:
  - proximity accepts an ip address, an address, zipcode, city, or latitude,longitude - i.e. 70.210.133.87, 210 NW 11th Ave, Portland, OR, 60647, Chicago, IL, and 45.521728,-122.67326 are all acceptable
  - proximity_square sets the length of the sides of the square to find matches inside of. The square is centered on the location specified by proximity. It defaults to 100.

• incidents.getVersionIncidentsIdFormat

  GET /v2/incidents/{id}

• locations.getVersionLocationsFormat

  This endpoint behaves exactly like incidents, but returns a valid geojson FeatureCollection that looks like this:

  {  type: "FeatureCollection",  features: [    {      type: "Feature",      properties: {      id: 4474199,      type: "Theft",      occurred_at: 1428536937    },      geometry: {      type: "Point",      coordinates: [ -122.6244177, 45.5164386 ]    }  }}

  It doesn’t paginate. If you pass the all parameter it returns all matches (which can be big, > 4mb), otherwise it returns the 100 most recent.

  Go forth and make maps!

  ](streamdown:incomplete-link)
• locations.getVersionLocationsMarkersFormat

  This behaves exactly like the root locations endpoint, but returns simplestyled markers (mapbox styled markers)

  Go forth and make maps!

• openapi.previewSpec

  Preview an OpenAPI document before adding it as a source

• openapi.addSource

  Add an OpenAPI source and register its operations as tools