Partner Portal setup
Partner docs are supply-side: they help teams expose offers to AON. Partner Portal is where your team manages account setup, Offer Fetch URL, credentials lifecycle, and operational settings; your backend still owns endpoint behavior.
Begin here for a new Partner account. Partner Portal is the system of action for profile and operational setup; it comes before Credentials & Signing. If the Partner has not been approved, stop after resolving Portal Setup and do not continue to credential configuration.
Partner Portal is the system of action
This page explains the setup boundary. Make configuration changes in Partner Portal, and keep implementation details in your own service and the Partner docs.
Setup responsibilities
| Area | Partner Portal owns | Your backend owns |
|---|---|---|
| Account setup | Partner profile, organization access, contacts | Operational owner and escalation process |
| Endpoint registration | The Offer Fetch URL AON should call | A stable HTTPS endpoint at that URL |
| Credentials | AppKey/AppSecret lifecycle and rotation workflow | Secure storage, signature verification, runtime reload |
| Operations | Contact, allowlist, routing, or health settings when available | Logging, alerts, test handling, and recovery playbooks |
Do not treat docs-site as the system of action for partner configuration. If the Portal and this summary differ, follow Partner Portal and contact AON support through your normal onboarding channel.
Offer Fetch URL
The Offer Fetch URL is the exact URL AON calls. If your endpoint path is
https://api.example.com/aon/v1/offers/query, register that complete URL.
AON does not append an extra path.
After saving the URL, use Offer Fetch to implement the
signed POST {offer_fetch_url} handler and response envelope.
Credentials lifecycle
Partner Portal manages AppKey/AppSecret lifecycle tasks such as issuing, rotating, and revoking credentials. Your backend should store secrets outside source control, verify every signed request, and support rotation without a long deploy window.
Read Credentials & Signing before enabling live traffic.
Operational settings
Operational settings vary by account and rollout stage. Treat the Portal as the place to manage setup state, contacts, endpoint ownership, and routing-related settings when they are available.
Your backend should still keep independent logs for request_id, timestamp
validation, signature failures, test-mode traffic, and response latency.
Portal Setup completion
Portal Setup is complete when the required profile material and operational owner are present, the exact Offer Fetch URL has been checked in Partner Portal, and the Partner status has been reviewed. This is a documentation and setup step, not a claim that the integration is live. If the status is not approved, stop here; continue to Credentials & Signing only after the Partner is approved.