With-issues ad objects
Updated: Jul 6, 2026
Copy for LLM
Ads in WhatsApp Status are available via the Marketing API. Learn more about ads in WhatsApp Status.
The
with_issues_ad_objects webhook notifies you when an ad object enters an issue state, meaning something went wrong during its operation or publishing. The payload identifies the object, the level it sits at, and details about the error, so you can catch problems such as a rejection or a delivery block and fix them quickly.Webhook payload
{ "object": "ad_account", "entry": [ { "id": "<AD_ACCOUNT_ID>", "time": 1782862117, "changes": [ { "field": "with_issues_ad_objects", "value": { "id": "<OBJECT_ID>", "level": "AD", "error_code": "567", "error_summary": "error summary", "error_message": "error message" } } ] } ] }
| Field | Description |
|---|---|
id | The ID of the ad object that entered an issue state. |
level | The level of the object: CAMPAIGN, AD_SET, AD, or CREATIVE. |
error_code | The code identifying the issue. |
error_summary | A short summary of the issue. |
error_message | A human-readable description of the issue. |
Poll for more context
To understand what went wrong before acting, read the object’s status and review feedback:
GET /<OBJECT_ID>?fields=effective_status,configured_status,review_feedback,creative{id,name,thumbnail_url},adset{id,name,status},campaign{id,name,status}
review_feedback gives the rejection reason when an ad is disapproved, configured_status distinguishes an intended pause from an issue, and the creative, adset, and campaign fields give the context you need for escalation decisions.Example actions
Disapproved: fix the creative and resubmit.
curl -X POST "https://graph.facebook.com/<API_VERSION>/<AD_ID>" \
-d "creative={'creative_id': '<CREATIVE_ID>'}" \
-d "status=ACTIVE" \
-d "access_token=<ACCESS_TOKEN>"
Pause an ad set while you investigate an issue.
curl -X POST "https://graph.facebook.com/<API_VERSION>/<ADSET_ID>" \
-d "status=PAUSED" \
-d "access_token=<ACCESS_TOKEN>"