Offer Fetch is the AON-to-Partner request and response flow for retrieving structured Partner Offers.
AON sends a signed request to the exact Offer Fetch URL configured by the Partner; the Partner verifies the request, selects eligible supply, and returns a valid Partner Offer response. AON then resolves source identity and projects eligible entries into Public Offers for the requesting AI product.
At a glance
| Step | Caller → receiver | Artifact / result | Identity owner |
|---|---|---|---|
| Query request | AI product → AON | Offer Query request | Caller may supply request_id; otherwise AON assigns it |
| Fetch request | AON → Partner | Signed Offer Fetch request | AON carries request_id into the Partner request |
| Supply response | Partner → AON | Partner Offer response | Partner owns source_offer_id and echoes request_id |
| Public response | AON → AI product | Public Offer response | AON owns offer_id + offer_instance_id |
Offer Fetch in AON
Offer Fetch is the supply-side connection that makes Partner catalogs available to AON's offer-discovery layer. It lets Partners own inventory and source identity while AON provides a consistent public projection and attribution path.
Implement Partner Offer FetchHow Offer Fetch works
Configure the endpoint
An approved Partner registers the exact HTTPS Offer Fetch URL and configures the credentials and signing material required for the environment.
Receive a signed request
AON sends the current query context to the configured endpoint using the active OfferProvider contract.
Verify and select supply
The Partner verifies request identity and signature, then returns only the eligible structured supply it can support.
Project for the Query
AON validates the response, resolves source identity, applies the applicable public projection, and returns Public Offers to the AI product when appropriate.
Implement Offer Fetch safely
Keep
- The direction distinction: AON → Partner for Fetch versus AI product → AON for Query.
- Request authentication, signature verification,
source_offer_id, and the closed Partner response envelope. - The separate boundary between Fetch readiness, production approval, and live delivery health.
Do not
- Returning an empty Offer result when signature or request authentication fails.
- Treating a Fetch response as a public Query response, checkout result, or price guarantee.
- Returning AON-owned
offer_idoroffer_instance_idfrom the Partner supply contract.
Offer Fetch trust boundaries
Offer Fetch separates endpoint authentication, Partner supply ownership, AON projection, and downstream outcome reporting.
| Concept | Meaning |
|---|---|
| Request authenticity | The Partner verifies the required headers, timestamp, request identity, and signature before parsing or applying the request. |
| Supply response | The Partner returns a closed response envelope with source_offer_id and the fields allowed by the Partner Offer schema. |
| Public projection | AON owns offer_id, offer_instance_id, public match context, and any other fields introduced during projection to the AI product. |
| Separate postback | Later conversion reporting uses the Partner postback contract, with its own endpoint, signature, idempotency, and validation rules. |
- Offer Fetch is not the public Offer Query endpoint and should not be described as an AI-product-facing search API.
- A fetch response is supply data, not a checkout result, price guarantee, or merchant order confirmation.
- A signature or request-authentication failure is an error; it must not be represented as an empty Offer result.
- Fetch readiness, a successful test, and live delivery health are separate operational states.
Offer Fetch vs Offer Query
Offer Fetch retrieves Partner supply for AON. Offer Query serves the AI product's discovery request and returns AON's Public Offer projection. The two flows have different callers, payloads, identities, and trust boundaries. See the Offer Query definition.
| Dimension | Offer Fetch | Offer Query |
|---|---|---|
| Caller and receiver | AON calls a Partner's registered endpoint. | An AI product calls AON. |
| Response | The Partner returns Partner Offers to AON. | AON returns Public Offers to the AI product. |
| Identity | The Partner supplies source_offer_id. | AON supplies offer_id and offer_instance_id. |
| Authentication | The Partner verifies AON's signed supply request. | The caller uses the access and authentication required by its AON deployment. |
Example in practice
An AI travel assistant queries AON for a Tokyo hotel. AON sends a signed request to the marketplace's registered Offer Fetch URL; the marketplace echoes request_id and returns eligible Partner Offers with source_offer_id values. AON then projects accepted entries into Public Offers for the assistant.
Common questions about offer fetch
Who calls an AON Offer Fetch endpoint?
AON calls the exact HTTPS endpoint registered by the Partner. The endpoint is not the same as the public Query API used by an AI product.
What does a Partner return from an AON Offer Fetch request?
The Partner returns a valid response envelope containing Partner Offers and stable source_offer_id values. It does not return AON-owned offer_id or offer_instance_id fields.
How is the request ID used in an AON Offer Fetch flow?
AON carries the Query request's request_id into the Partner request, and the Partner echoes the same value in its response so the exchange can be correlated.
How should a Partner verify an AON Offer Fetch request?
The Partner should verify the required headers, timestamp, request identity, and signature before parsing the request or applying business logic. A failed authentication or signature check is an error, not an empty Offer result.
Sources
- AON Partner Offer Fetch guideAON documentation
- AON Partner credentials and signingAON documentation
- AgentOffer Protocol OfferProvider specificationAON specification
- AON Partner postbacksAON documentation