Ads
Delete Meta Ads campaigns, ad sets and ads via API
Three DELETE routes remove an object from the customer's ad account: a campaign, an ad set or an ad. You use the id Ads Manager shows or the Connect uuid, and the customer's connection handles access, with no OAuth to build and no Meta app review.
The request
DELETE /api/ads/campaigns/120250000000000001?customer_integration=<connection uuid> Authorization: Bearer <merchant token> x-customer-token: <customer token> Idempotency-Key: <unique key>
What you can do
- Delete a campaign with DELETE /ads/campaigns/{id}, which takes its ad sets and ads with it, on the platform and in the Connect database.
- Delete an ad set with DELETE /ads/adsets/{id}, which takes its ads with it.
- Delete an ad with DELETE /ads/{id}, and the campaign and ad set remain.
- Delete any object in the account, including ones created outside Connect, using the platform's numeric id.
- List deleted objects too with include_deleted=true on source=connect, each one carrying deleted_at.
Rules and limits
- Deleting a campaign deletes its ad sets and ads. To keep the history, pause instead of deleting.
- The connection always goes in ?customer_integration= and the call needs Authorization and x-customer-token.
- Idempotency-Key is optional on DELETE. With it, repeating the call returns the first response.
- The object must belong to the connection's account: an id from another account answers 404 ads_object_not_found, and so does a uuid Connect does not store.
- The 200 response carries data with id and deleted. If the platform refuses, its status is mirrored and integration_error carries the code.
Main fields
| Field | Type | Required | Description |
|---|---|---|---|
| id | string | Yes | In /ads/campaigns/{id}, /ads/adsets/{id} or /ads/{id}: the numeric id the ad platform gave the object (the same as in Ads Manager) or the Connect uuid. |
| customer_integration | string | Yes | The uuid of the customer's connection. It defines the ad account. Always goes in the query. |
| Idempotency-Key | string | No | Optional header here (up to 255 characters). With it, repeating the call returns the first response instead of deleting again. |
| deleted | boolean | No | In the response, inside data: confirms the object was deleted, along with its id. |
Who it is for
Clean up draft campaigns
A traffic management platform deletes test campaigns created by mistake in one click, without the customer opening Ads Manager.
AI agent that tidies accounts
An agent finds rejected ads and deletes only those, keeping the ad set and campaign to receive new creatives.
End a customer promotion
An agency ends a promotion by deleting the campaign, and its ad sets and ads go with it in a single call.
Works with
Meta Ads
Frequently asked questions
Does deleting a campaign delete its ads?
Yes. DELETE /ads/campaigns/{id} takes the ad sets and ads with it, on the platform and in the Connect database. Deleting an ad set takes its ads, and deleting an ad leaves the ad set and campaign.
Can I still see what was deleted?
Yes. On lists with source=connect, include_deleted=true includes deleted objects, each with deleted_at. Without it they do not show up.
Can I delete an object created outside Connect?
Yes. The accepted id is the platform's numeric one, which works for any object in the account. It is only refused (404) if the object belongs to another account.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
