Instagram search API

Find public videos for a keyword, then page through the returned results. Inputs, response fields and integration checks for Instagram.

What to build with it

  1. Start with a narrow phrase that describes the content you need, rather than a brand name alone.
  2. Save the result IDs, platform URLs and collection time. Use the next cursor only with the same search.
  3. Fetch selected videos individually before using their metrics in a report.
  4. Inspect the returned Reels before interpreting keyword relevance; do not treat this result set as an Instagram feed of every post format.

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

  • Public-data discovery is different from the authenticated Instagram publishing API. Do not use these endpoints to promise account management, private insights or posting.
  • Search ordering reflects the provider's retrieval at that moment. It is not an exhaustive crawl or a guaranteed global popularity ranking.

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.

For a deeper profile, compare the creator lookup with the ongoing tracking workflow.

Give this task to your coding agent

instagram-search-api agent prompt
Help me implement instagram search api using the documented Virlo API.

Reference: https://allthemapis.com/social-media-apis/instagram-search-api
Provider documentation: https://dev.virlo.ai/docs/raw
Base URL: https://api.virlo.ai
Starting operation: GET /v1/raw/instagram/search

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. Start with a narrow phrase that describes the content you need, rather than a brand name alone.
2. Save the result IDs, platform URLs and collection time. Use the next cursor only with the same search.
3. Fetch selected videos individually before using their metrics in a report.
4. Inspect the returned Reels before interpreting keyword relevance; do not treat this result set as an Instagram feed of every post format.

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.