Get an Ad Using Only its Archive ID
View all Facebook Public Data API endpoints →Pass ad_archive_id when only a saved public ad archive identifier is available. Documentation warns that this convenience route can be less reliable; use get-ad-details with the matching country and Page ID when available. No response for this endpoint was sampled, so neither creative fields nor an equivalence with the contextual detail route is guaranteed. A failure here alone must not be interpreted as evidence that an ad was deleted.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/facebook-scraper/get-ad-details-by-just-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/get-ad-details-by-just-id?key=<API_KEY>&ad_archive_id=<ad_archive_id>'
Query Result
Use Cases
- Inspect an imported archive-ID list before advertiser context has been reconciled.
- Offer an archive-ID-only search box in an internal ad review tool.
- Measure ID-only resolution separately from contextual detail resolution during client evaluation.
- Send unresolved archive IDs to a context-enrichment queue instead of marking them deleted.
Frequently asked questions
Can I look up details with only ad_archive_id?
You can try this endpoint, but the documentation warns that reliability may be lower. Its result structure has not been independently validated either.
When should I switch to the full ad-detail endpoint?
When you know page_id and country for the same ad, use them with ad_archive_id for the contextual lookup, especially if the ID-only lookup fails.
Does a failed lookup mean that the ad no longer exists?
No. Failure of this convenience endpoint is not enough to establish deletion. Supply the missing context and preserve an uncertain state.