Engineering guide

Planning an Apple Ads API migration

An API migration is complete only when authentication, request schemas, report semantics, pagination, rate handling, and operational dashboards work under the new version—not when the first request returns 200.

9 min readUpdated Aug 4, 2026
01

Inventory every endpoint and derived metric.

Map callers, jobs, tool definitions, response fields, enum values, and reports. Identify which dashboards or automations depend on each transformed field.

02

Run old and new paths against fixed fixtures.

Contract tests should cover pagination, empty results, partial errors, time zones, currencies, deleted or paused entities, and aggregation totals—not only happy-path campaign lists.

03

Deploy with comparison and rollback.

Shadow or dual-read a sample, compare totals, add version-specific telemetry, and keep a time-bounded rollback path. Update customer-facing tool descriptions when capabilities change.