Meta Marketing API vs Snapchat Ads API

Meta Marketing API

Reporting, campaign, budget, audience and creative endpoints sit behind ads_read and ads_management scopes, with a validate_only option and sandbox ad accounts for checking a change before it spends. New apps are held to a score of 60 per ad account, with a 300-second block at the limit, and the documented requests pass the access token as a parameter.

Snapchat Ads API

The docs are served as Markdown with an llms.txt index, rate limits are published as 20 requests a second per app and 10 per token, and test ad accounts never serve live ads. No OpenAPI specification, status page, SLA, idempotency key or Ads API SDK was found, and one OAuth scope covers both reads and writes.

Meta Marketing API

1. Put a version in every path, such as /v26.0/act_<AD_ACCOUNT_ID>/campaigns. Unversioned Marketing API calls fail
2. Create campaigns, ad sets and ads with status=PAUSED, and send execution_options=["validate_only"] first to test a write without making it
3. Ask for ads_read alone when the task is reporting. ads_management can change budgets and activate spend
4. Read X-Business-Use-Case-Usage and X-Ad-Account-Usage after each call and wait for estimated_time_to_regain_access on errors 17, 613 and 80004
5. Change an ad set budget at most four times an hour and an account spending limit at most ten times a day

Snapchat Ads API

1. Refresh the access token every 60 minutes with the refresh token. An expired token returns 401 with WWW-Authenticate: Bearer error="invalid_token"
2. Create a test ad account with "test": true and build there first, and create campaigns with "status": "PAUSED"
3. Change one field with PATCH (JSON Patch). A PUT that omits attributes resets them to their defaults
4. Send money as micro-currency, where 1.00 of the account currency is 1,000,000
5. Page lists with limit (50 to 1,000) and follow paging.next_link. Use async=true for large stats pulls, since an oversized response fails with E9001 and a retry does not help