Developer API

A public, read-only API that returns registered location preferences as GeoJSON, so drone, AR, and UTM planning tools can surface them for an operating area at planning time.

Advisory, not authority

Preferences are informational and voluntary. They do not create legal restrictions, no-fly zones, or authority over airspace, and they do not override authorized operations (e.g. LAANC). AirspaceRegistry.org is a preference/advisory layer, not a USS or an authorization service.

Base URL

https://airspaceregistry.org/api/v1

No API key required. CORS is open. Responses are cacheable (60s).

Query preferences in an area

GET /preferences

Filter by a bounding box or a point + radius:

`bbox`	`minLng,minLat,maxLng,maxLat` — return entries inside this box
`lat`, `lng`	center point for a radius search
`radius_km`	radius in km (default 5), used with lat/lng
`verified`	`true` → only document-verified entries
`limit`	max features (default/max 2000)

Example — everything within 10 km of lower Manhattan:

GET https://airspaceregistry.org/api/v1/preferences?lat=40.7128&lng=-74.0060&radius_km=10

Look up one entry

GET /preferences/{location_id}   e.g. /preferences/asr_AbC123

Response (GeoJSON)

{
  "type": "FeatureCollection",
  "schema_version": "1.0",
  "generated_at": "2026-06-29T21:00:00.000Z",
  "count": 1,
  "disclaimer": "Preferences are informational and voluntary ...",
  "features": [
    {
      "type": "Feature",
      "geometry": { "type": "Point", "coordinates": [-74.0060, 40.7128] },
      "properties": {
        "location_id": "asr_AbC123",
        "title": "Example rooftop",
        "drone_preference": "sensitive",
        "ar_preference": "welcome",
        "authority_level": "informational",
        "legal_effect": "non_binding_preference",
        "source": "community_registry",
        "verified": false,
        "verification_status": "unverified",
        "altitude_floor_m": 0,
        "altitude_ceiling_m": 120,
        "radius_m": 50,
        "address": { "city": "New York", "state": "NY", "country": "USA" },
        "last_updated": "2026-06-29T18:30:00.000Z"
      }
    }
  ]
}

Field reference

`drone_preference`	`welcome` · `ask` · `notify` · `sensitive`
`ar_preference`	`welcome` · `coordinate` · `commercial` · `sensitive`
`authority_level`	`informational` (community) · `rule_linked` (points to an external rule)
`legal_effect`	`non_binding_preference` · `external_rule_reference`
`source`	`community_registry` · `municipal_code`
`verified` / `verification_status`	whether the registrant’s connection to the address was reviewed and approved
`altitude_*_m`	the claimed airspace band, metres above ground level
`rule_url`	present only on `rule_linked` entries — link to the referenced ordinance

How to use it (operators)

At mission planning, query your operating area, surface any returned preferences to the pilot, and use them for courtesy coordination and conflict reduction. A returned preference never changes the legal status of an authorized operation; it is a communication signal from the place to the operator.

Roadmap

Planned, not yet available: a municipal/government tier (authority_level: rule_linked, source: municipal_code, verified jurisdictions linking real ordinances), a richer per-activity category taxonomy, parcel-level snapping, and webhook subscriptions for changes within an operating area. Interested in a pilot or integration? partners@airspaceregistry.org.