# API Reference

Source: https://docs.aon.pro/api

> Derived from the same AON Docs release as the source page.

HTTP API

Query offers from user intent with Offer Query. Separately, use Location Search for registry lookup and normalization. For an enabled account, manage issued keys in [Developer Portal](https://developer.aon.pro/).

Base URL

https://api.aon.pro

Authentication

Bearer API key

Contract

OpenAPI connected

## API surfaces

Choose an operation and work directly from its schema and examples. Location lookup results are not Query v1.0 viewer context.

2 public surfaces

[

Query

### Offer Query

Send intent, context, constraints, and pagination fields to discover offers for AI product or agent experiences.

POST`/v1/offers/query`Bearer required



](https://docs.aon.pro/api/offer-query)[

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.

GET`/v1/locations/search`Public

GET`/v1/locations/resolve`Public

GET`/v1/locations/{location_id}`Public



](https://docs.aon.pro/api/location-search)

First request

## Start with a bounded query

1.  Without an issued key, run the Public Test Sandbox to inspect a fixed v1.0 Query and response.
2.  For production traffic, use an issued API key as the bearer token.
3.  Send structured intent and only v1.0-declared context, then preserve returned actions and tracking data.

[Run the Public Test Sandbox →](https://docs.aon.pro/quickstart/public-test-sandbox)[Read the production first-call guide →](https://docs.aon.pro/quickstart/first-api-call)

First offer query

curl

```
curl -X POST https://api.aon.pro/v1/offers/query \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "AON-Protocol-Version: 1.0" \
  -d '{
    "intent": {
      "content": [
        { "type": "input_text", "text": "noise cancelling headphones under $200" }
      ],
      "provenance": "user_expressed",
      "signals": {
        "budget": { "max": 200, "currency": "USD" }
      }
    },
    "context": {
      "platform": { "name": "api-client", "channel": "api" },
      "session": { "recent_topics": ["headphones"] }
    },
    "placement_id": "plc_A1b2C3d4E5f6G7h8",
    "constraints": {
      "category_ids": ["computers_electronics.consumer_electronics"]
    },
    "force_offer": false,
    "response_options": { "thinking_mode": true }
  }'
```

### Reference provenance and coverage

Services OpenAPI source connected. This page renders from a checked-in services-side OpenAPI artifact, then layers partner-oriented guidance on top of the generated contract.

This checked-in artifact now prioritizes field-level detail for the main developer and partner onboarding routes. Less frequently used endpoints still render from the generated source, but may expose lighter request or response depth until future documentation passes.