Skip to content
 

API Reference · Lookup

Location Search

Search and normalize AON Location Registry ids for location pickers and Offer-side geographic targeting without treating lookup results as Query v1.0 viewer inputs.

Reference provenance and Query boundary

All three public Location operations on this page are implemented by the current runtime. They are documented here as a docs-curated runtime reference because the checked-in service OpenAPI does not yet include /v1/locations/*. That OpenAPI gap does not change their public runtime availability.

Use the results for registry lookup, normalization, verified ancestry, location pickers, or authoring Offer-side geographic targeting. Current Query v1.0 does not define a viewer-location input and rejects undeclared fields such as context.user_profile.location_ids.

Operations

Implementation checklist · 3 items
  • Use the static registry as the source of truth for supported ids.
  • Store numeric-string location_id values rather than display names.
  • Treat returned location_ids chains as registry ancestry; current Query v1.0 does not expose a viewer-location field.