HomeMonetizeAdvertise
Start now →Sign in
Core glossary term

What is the OfferProvider API?

AON's OfferProvider API lets a supply-side Partner receive signed requests, match its catalog, and return eligible Partner-authored Offers through the v1.0 Offer Fetch contract.

By AON Editorial Team · Published September 6, 2026

A signed OfferProvider API exchange between AON and a supply Partner
OfferProvider API
Partner · fetch · supplySigned supply exchange between AON and Partners
Definition

AON's OfferProvider API is the Partner-facing supply contract in AgentOffer Protocol v1.0.

AON sends a signed request to the exact Offer Fetch URL configured by the Partner; the Partner validates the request, matches eligible catalog entries, and returns a Partner Offer response envelope. The Partner returns source_offer_id and Partner-authored fields, while AON resolves public offer_id, creates offer_instance_id, and adds public delivery context after identity and eligibility processing.

AON context

OfferProvider integrations in AON

AON uses the OfferProvider API to connect Partner catalogs with the public offer-discovery layer. The Partner owns its source supply; AON owns the public Query projection and attribution behavior.

Read the Offer Fetch implementation guide
Supply-side integration

How the OfferProvider API works

Register the endpoint

The approved Partner registers the exact HTTPS Offer Fetch URL in Partner Portal.

Verify the request

The Partner validates the timestamp window, HMAC signature, nonce, protocol selector, and test mode before business processing.

Match supply

The Partner applies constraints and current catalog rules to identify eligible inventory for the request.

Return Partner Offers

The Partner returns the v1.0 envelope and Partner-authored Offer fields, including a stable source_offer_id.

Project the public Offer

AON resolves source identity, applies its own eligibility and relevance behavior, and creates public delivery identity for the Agent-facing response.

Term anatomy

OfferProvider boundaries

The OfferProvider API is a supply carrier, not the public Query response and not a Partner operations portal.

ConceptMeaning
Request directionAON calls the Partner endpoint with signed AON-to-Partner headers and a supply-side request body.
Partner OfferThe Partner owns source identity and Partner-authored offer content, entity data, action, and Goals.
Public projectionAON owns public offer_id, per-dispatch offer_instance_id, and public match context added after source identity resolution.
Operational boundaryPartner Portal manages approval, credentials, endpoint configuration, and operational access; the API contract defines wire behavior.
A structured comparison of the concepts that define offerprovider api.
Important boundaries
  • The OfferProvider API is not the Developer-facing Offer Query API.
  • A Partner Offer is not identical to the public Agent-facing Offer projection.
  • Offer Fetch readiness or a successful test request does not by itself mean the Partner is approved and live in production.
  • Partner-to-AON postbacks use a separate contract and must not reuse Offer Fetch signing assumptions.
Do not confuse

OfferProvider API vs Offer Query API

The OfferProvider API supplies eligible inventory from a Partner to AON. The Offer Query API returns AON's public Offer projection to an Agent or Developer product. They have different callers, payloads, identities, and trust boundaries. See the Offer Query definition.

Applied definition

Example in practice

A marketplace registers an Offer Fetch URL. AON sends a signed v1.0 request for Tokyo hotel inventory, the marketplace returns eligible Partner Offers with stable source_offer_id values, and AON resolves those entries into public Offers for an AI travel assistant.

Common questions about offerprovider api

What does a Partner return through OfferProvider API?

The Partner returns the v1.0 supply envelope and Partner-authored Offer fields, including a stable source_offer_id. AON adds its own public identity and delivery fields later.

Should a Partner return offer_id or offer_instance_id?

No. Partners return source_offer_id. AON resolves the public offer_id and creates offer_instance_id for a particular public dispatch.

Is Offer Fetch the same as Offer Query?

No. Offer Fetch is AON-to-Partner supply retrieval. Offer Query is the Agent or Developer-facing request that returns AON's public Offer projection.

Does a successful Offer Fetch test make a Partner live?

No. The test verifies the endpoint and response contract. Production status also requires approval and healthy operational state in the Partner environment.

Sources

  1. AgentOffer Protocol v1.0 OfferProvider APIAON specification
  2. AgentOffer v1.0 Partner Offer schemaAON specification
  3. AON Partner Offer Fetch guideAON documentation
  4. Review Partner postbacksAON documentation
← Back to the full AON glossary