Apple Ads Platform API vs FetchIQ

Apple Ads Platform API

Every response carries RateLimit-* headers and a 429 carries Retry-After, Apple maintains MIT client libraries in four languages, and read-only API roles exist. The API was first released in August 2026. No status page, SLA, published OpenAPI file, idempotency key or test account was found, and a person must create the credentials in the Apple Ads interface.

FetchIQ

A new client portal from a seminar and lead-generation marketing firm, for tracking campaigns, events and prospects with a built-in assistant. Only people signed in through the company's single sign-on can use it. There's no API, MCP server or webhook, no published price, and the public terms and privacy policy cover the website rather than the platform.

Apple Ads Platform API

1. Send Authorization: Bearer {access_token} and X-AP-Context: adAccountId={adAccountId} on every ad account call. Get the account id from GET /v1/acls
2. Request a new access token every 3,600 seconds from https://appleid.apple.com/auth/oauth2/token with scope searchadsorg. The signed client secret lasts at most 180 days
3. Read RateLimit-Remaining on each response. On a 429 wait the Retry-After seconds, then double the wait up to 16 seconds
4. List and filter with POST to a /query endpoint, not GET with query parameters. Deleted entities return only when a filter asks for them
5. On PUT send only the fields to change, and send the complete desired array for any array field. Create campaigns with "status": "PAUSED" before review

FetchIQ

1. Don't try to call FetchIQ. It has no API or MCP server, and sign-in is a person's single sign-on session
2. Ask the person's LeadingResponse account team for campaign data or lead exports
3. Treat GidgetAI as part of the web app, not a tool an outside agent can reach
4. Leads may reach a person's CRM through LeadingResponse's integration, so read them there