Skip to content
 

API Reference · Details

OfferInfo API

Read current public Offer details by canonical offer_id or aonlink using a Live API Key, with the same business information as Query and no new distribution instance.

Operations

GET/v1/offers/infoBearer required
Read Offer details
Curated overlay
Headers
Fields
1·1 required
Showing the complete documented schema.
Authorizationstring
required

Bearer followed by your application-owned Live API Key. Test Keys are not supported.

example: Bearer <LIVE_API_KEY>
Query Parameters

At least one parameter is required. When both are supplied, they must identify the same Offer.

Fields
2·0 required/2 conditional
Showing the complete documented schema.
offer_idstring
required when offerurl is absent

Canonical Offer UUID returned by Query. An upstream Offer ID or bare offer_instance_id is not a canonical Offer ID.

example: 11111111-1111-4111-8111-111111111111format: uuid
offerurlstring
required when offer_id is absent

Complete existing aonlink, URL-encoded as one query parameter. Supports root short codes, root historical instance UUIDs and /static/st_… links.

example: https://aon.link/Ab12Cd34?subid=demo#detailsformat: uri
Behavior, compatibility, and source notes

Read one current public Offer by canonical offer_id or an existing aonlink, using an application-owned Live API Key.

  • Send Authorization: Bearer <LIVE_API_KEY> from your server. Live and Live Limited applications can call this route; paused or suspended applications cannot. Offer Query and MCP search continue to use placement identity without a new API Key requirement.
  • Provide offer_id, offerurl, or both. Both must resolve to the same canonical Offer; otherwise the response is 409 OFFER_INFO_IDENTITY_CONFLICT. A missing link mapping returns 404. Empty or malformed input returns 400.
  • offerurl is a complete aonlink, not a merchant destination URL. Supported paths are an eight-character alphanumeric root short code, a historical offer_instance_id UUID at the root, or /static/st_… . Use the aonlink origin configured for the API environment. URL-encode the entire parameter, including its query and fragment, as in --data-urlencode below.
  • The URL query and fragment do not change Offer identity. The response preserves the exact submitted aonlink in action.payload.url, including its existing attribution. A link from another application may locate a public Offer; ownership, trace, placement and user context are not returned or rebound.
  • This reads stored local and remote data without calling Query, following redirects, or contacting suppliers. It creates no offer instance, impression, click or link binding, and consumes no serving quota. Catalog membership and placement selection are not required.
  • Local content uses the stored original snapshot, without intent localization. Remote content selects an active English snapshot first, otherwise the most recently updated active snapshot, with a stable tie-break. content_language reports only the selected content's known language; unknown language is omitted. Language selection, translation and historical versions are not supported.
  • Only current public non-test content is returned: active, undeleted and non-delisted local Offers, or active remote snapshots. Missing mappings or snapshots and withdrawn content return 404. Temporary serving unavailability or an expired quote does not by itself hide details. Stored content may be stale and is not a new serving or price guarantee.
  • Business fields use the Query v1.0 public Offer projection for the selected stored data, including commercial/details profiles, entity, material and goals. CPA/CPS retain Query units; CPS rate is a percentage string. Optional fields are omitted when absent. Internal credentials, settlement contracts and recommendation context are not exposed.
  • offer_instance_id is always omitted, never null or a synthetic UUID. ID-only reads omit action; URL reads retain public action metadata and use the submitted aonlink. A malformed stored snapshot returns 503 instead of an incomplete success object.
Implementation checklist · 4 items
  • Create a Live API Key in Developer Portal under your application's API & Webhooks → API Keys. The application must be Live or Live Limited.
  • Supply canonical offer_id, a complete URL-encoded offerurl (aonlink), or both identifying the same Offer.
  • Treat the response as stored public content, not a fresh supplier quote or a guarantee that the Offer can currently be served.
  • Preserve the existing action URL when provided. offer_instance_id is never returned; ID-only reads omit action.