This endpoint is available in the Experimental version of the Retail Media API only.
Experimental endpoints may change without prior notice. See the versioning policy for details.
Overview
The change history endpoints return a time-ordered log of configuration changes made to Retail Media objects — campaigns, line items, and related entities. Each entry records what changed, on which entity, when it occurred, and the role of the actor who made the change. Two scopes are available: account-level (demand side) and retailer-level (supply side). Changes are returned in descending order by time. Only changes the caller has access to are returned; inaccessible entries are silently omitted.Prerequisites
- Authentication: a valid access token. See Authentication.
- App permissions: the
RetailMedia_Campaign_Readscope must be enabled on your app. See App Scopes. - Account or retailer access: the authenticated app must have access to the requested account or retailer. A
403is returned for unknown or inaccessible identifiers.
Endpoints
Get Change History Entries
Path Parameters
Query Parameters
Array parameters use repeated query keys. For example:
event-types=lineItemCreated&event-types=lineItemUpdated. A comma-separated list is treated as a single value and may silently return no results.
Response Attributes
Eachdata[] item has a type field (ChangeHistoryEntryResponse) and an attributes object:
Pagination metadata is returned in the
meta object:
Sample Request
200 OK
Get Change History Entries (Retailer)
Path Parameters
Query Parameters
Same as the account endpoint above.Response Attributes
Same shape as the account endpoint above.Campaign-level changes are not returned by this endpoint — only line-item and other retailer-scoped entity changes are included. This applies to both onsite and offsite campaign changes.
200 OK
Known Limitations
- The default time window is the last 7 days. There is no documented maximum lookback period.
- User identifiers are not returned — only the actor’s role (
api,internal, etc.). - The order of entries with identical
occurredAttimestamps is not defined. entity-typesandevent-typesenum values are not yet published in the spec. Unknown values are accepted but match no entries.
Error Codes
Unknown
event-types or entity-types values are not validation errors — they match no entries and return 200 with an empty result.