Supply offers to AON with Protocol v1.0
Partner Integration is the supply-side path for the AgentOffer Protocol. It is for teams that publish offers to the AON network. You host a stable Offer Fetch endpoint, configure it in Partner Portal, and AON calls your endpoint whenever an agent query needs eligible offers. Partner Portal owns account setup and operational access; this section explains the protocol and backend responsibilities that stay with your team.
Start in Partner Portal to set up this supply-side integration. Complete Portal Setup first, and check that the Partner has been approved before continuing to Credentials & Signing. If the Partner is not approved, stay in Portal Setup and resolve the account or profile state; do not proceed to credential configuration yet.
Protocol v1.0 contract
Use the exact AON-Protocol-Version: 1.0 selector and response echo. Implement
Offer fields, requiredness, validation, signing, retry, and postback behavior
from the canonical v1.0 sources linked below.
Building an AI agent instead?
If you are integrating AON into Claude, ChatGPT, a custom agent, or an app, start with Integration Guides, API Reference, or SDKs. Partner docs are the opposite direction: you expose offers to AON.
Partner tasks
| Task | Where to go | What you do |
|---|---|---|
| Configure Partner Portal | Portal Setup | Understand which onboarding tasks live in Partner Portal and which stay in your backend. |
| Handle credentials & signing | Credentials & Signing | Manage AppKey/AppSecret responsibilities and verify signed AON requests safely. |
| Implement Offer Fetch | Offer Fetch | Host the signed POST {offer_fetch_url} endpoint AON calls to fetch offers. |
| Set up postbacks & attribution | Postbacks & Attribution | Understand tracking, conversion, and postback responsibilities after offers are served. |
| Review protocol source | OfferProvider API spec | Check the normative v1.0 contract, schemas, examples, and conformance requirements. |
The document path is Portal Setup → Credentials & Signing → Offer Fetch → Postbacks & Attribution. Tracking Macros is not part of that path.
Supply Offer Profile reference
Use the Supply Offer Profiles reference when an Offer includes registered domain details. The first published profiles cover Flight and Hotel Rate, with searchable field paths, requirement rules, semantics, and complete Partner Offer examples.
This is a reference branch, not another onboarding step. The Partner task flow remains Portal Setup → Credentials & Signing → Offer Fetch → Postbacks & Attribution.
Partner readiness and completion
Use Partner Portal to check these six required readiness items:
| Required item | What “ready” means |
|---|---|
| Profile material | Partner name, website, supported categories, and a contact email are complete. |
| Valid credentials | An active or rotating AppSecret is available and your backend can verify signed requests. |
| Offer Fetch URL | The exact HTTPS URL AON should call is registered. |
| Fetch test | A signed Offer Fetch test returns a valid v1.0 response without production side effects. |
| Click/Postback test | Provider click and postback test evidence is recorded and can be reconciled. |
| Production health | The Partner integration reports healthy operational status. |
Completing the document path means these responsibilities are documented and
their checks are understood. ready_for_review means the required setup is
ready to submit for review; it does not mean the Partner is live. Describe the
integration as live only when the Partner is approved and healthy in production.
If the Partner is approved and credentials are ready, you may jump directly to Offer Fetch to implement the endpoint AON will call.
What this section covers
- The AON -> Partner request direction.
- The
POST {offer_fetch_url}contract and required signed headers. - Request/response envelope expectations for OfferProvider integrations.
- Links to protocol and schema source-of-truth documents.
Partner Portal mapping
Partner Portal surfaces link back to this section from the setup flow:
| Portal surface | Docs destination | Purpose |
|---|---|---|
| Integration Readiness - profile | Portal Setup | Understand the account and operational setup boundary. |
| Integration Readiness - credentials | Credentials & Signing | Verify how AppKey/AppSecret are used for signed requests. |
| API Endpoint and Testing | Offer Fetch | Implement and test the exact POST {offer_fetch_url} contract. |
| Click/Postback testing | Postbacks & Attribution | Confirm tracking, conversion, and postback responsibilities. |
| Monitoring, Quality, and Activity | Partner overview | Use the Partner overview as the nearest published docs hub; this row does not claim separate Monitoring, Quality, or Activity operations-guide coverage. |
This section does not replace Partner Portal. Use Partner Portal Setup to understand the setup boundary, then continue with Credentials & Signing and Offer Fetch.
Next step
Start with Portal Setup when you are preparing a new Partner account.