Meta ads research API

Explore ads collected by a content research agent. Understand the difference between sampled ad research and the official Meta Ad Library API.

What to build with it

  1. Enable Meta ad collection only for a research job that needs it.
  2. Read collected ad records and retain advertiser, source link and observation time when available.
  3. Inspect the original ad before making claims about its creative or campaign.

Provider reference: Virlo documentation. Authentication uses a provider-issued Bearer token, stored on your server.

Endpoints and inputs

1 documented operation. Query and path fields are listed separately from JSON request-body fields.

Before you integrate

  • This is a provider's agent-collected ad dataset, not a claim of direct Meta authorization or complete Ad Library coverage. Do not infer spend, targeting or conversion rates from creative records.

Check the provider's current price, allowed use and retention terms before sending requests. An optional field can be absent; the schema alone does not establish its completeness or accuracy.

Give this task to your coding agent

meta-ads-research-api agent prompt
Help me implement meta ads research api using the documented Virlo API.

Reference: https://allthemapis.com/social-media-apis/meta-ads-research-api
Provider documentation: https://dev.virlo.ai/docs/agents
Base URL: https://api.virlo.ai
Starting operation: GET /v1/agents/{id}/ads

Read the current provider docs and confirm the required inputs before writing code. Load VIRLO_API_KEY from a server-side environment variable and use Bearer authentication. Do not put the key in client code, logs, analytics, or the chat.

Ask me for any missing video URL, creator handle, research intent, or job ID. Do not invent a result. Ask for approval before starting billable lookups, recurring jobs, or destructive changes. For jobs, keep the returned ID and poll with the documented delay instead of starting the job twice. Handle pagination, rate limits, partial results, and missing fields explicitly.

Build the smallest integration for this task:
1. Enable Meta ad collection only for a research job that needs it.
2. Read collected ad records and retain advertiser, source link and observation time when available.
3. Inspect the original ad before making claims about its creative or campaign.

Return the code, the environment variables I need, and a short explanation of what was actually retrieved versus inferred. Do not execute paid requests until I approve.

Sources and review dates

Virlo's public documentation and OpenAPI schema reviewed October 27, 2026. Endpoint paths and field names below refer to that provider's API. This is an integration reference, not a measured performance ranking.

Corrections: email faizank@docsalot.dev with an official source.