Nexscope

Instagram Reels Search

Search Instagram Reels by keyword through REST or MCP. Read one page of available results, apply a posting-date filter and request pages 1 to 11 manually.

CostAt least 10 credits / call
Try online
POST · https://api.nexscope.ai/instagram/reelsSearchMCP · social_instagram_reels_search

What this API does

Search Instagram Reels by keyword through REST or MCP. Read one page of available results, apply a posting-date filter and request pages 1 to 11 manually. The request accepts keyword, datePosted, page. Its documented result includes fetchedAt, hasMore, author.handle, author.id, author.name, author.url, caption, commentCount.

Instagram Reels Search API use cases

Plan a Instagram Reels Search request

A researcher checks the published operation description and supplies keyword, datePosted, page for Instagram Reels Search. The request stays within the supported parameters rather than assuming other platform capabilities.

Inspect Instagram Reels Search results

An analyst reviews fetchedAt, hasMore, author.handle, author.id, author.name, author.url, caption, commentCount from Instagram Reels Search for the requested subject. Missing values remain explicit, and the response does not establish complete platform coverage.

Document Instagram Reels Search observations

A researcher records the inputs and available results from Instagram Reels Search alongside its published description. The record supports a scoped review without inferring unsupported actions, refresh intervals or broader conclusions.

Instagram Reels Search API FAQ

What does the Instagram Reels Search API return?

Search Instagram Reels by keyword through REST or MCP. Read one page of available results, apply a posting-date filter and request pages 1 to 11 manually. The documented output includes fetchedAt, hasMore, author.handle, author.id, author.name, author.url, caption, commentCount. It corresponds to the supplied keyword, datePosted, page. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Instagram Reels Search API cost?

The current documented cost is At least 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Instagram Reels Search API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/instagram/reelsSearch with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call social_instagram_reels_search. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/instagram/reelsSearch
MCP method
social_instagram_reels_search

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/instagram/reelsSearch

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/instagram/reelsSearch' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "keyword": "coffee"
}'

Code example

{
  "keyword": "coffee"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Social Data

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "social_instagram_reels_search",
    "arguments": {
      "keyword": "coffee"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can Instagram Search Reels provide, and how might I use it?

AI answer

Use this when you only want Google-indexed Instagram reels matching a keyword or phrase, with optional date filters and pagination. It returns reel media, engagement, owner, location, and audio details. Results are best-effort rather than a complete Instagram-native search. For Instagram-curated topic posts, use /v1/instagram/search/popular. For an exact hashtag across posts and reels, use /v1/instagram/search/hashtag. Pages 1 through 11 are supported; page 12 or greater returns a 400 response.

Data categoryDocumented fieldsHow to use them
Requestkeyword, page, datePostedProvide the required identifiers, filters, or paging inputs listed in the API document.
Responsedata.fetchedAt, data.hasMore, data.items[].author.handle, data.items[].author.id, data.items[].author.name, data.items[].commentCount, data.items[].likeCount, data.items[].viewCountInspect returned values and source references; availability depends on the request and upstream source.
  • Review Instagram Search Reels.
    • Prompt example: “Retrieve Instagram Search Reels for [search phrase]. Summarize only the information actually returned and preserve source links when available. Report private, restricted, missing or partial results explicitly; missing values are not zero.”
  • Collect a Bounded Set of Results.
    • Prompt example: “Retrieve Instagram Search Reels for [search phrase] across at most two pages within my approved credit budget. Use only the continuation information actually returned, with the same query and filters. Stop at the documented page limit, an absent continuation, an end indicator or a repeated page. Keep source references and report that the collection is bounded, not exhaustive.”
  • Focus the Review on a Selected Period.
    • Prompt example: “Retrieve Instagram Search Reels for [search phrase] for [a period supported by this tool]. Use the documented date meaning, format and limits, and show that scope with the results. Keep required date pairs together. Do not treat a search-index window as an exact publication-time filter or infer a complete historical archive.”
  • Prepare a Snapshot of Returned Public Counts.
    • Prompt example: “Retrieve Instagram Search Reels for [search phrase] and make a compact table of the public counts actually returned. Keep each count attached to its item or account, label estimates and preserve the observation time when supplied. Do not invent engagement rates, historical growth, unique audience size or missing values.”

These are suggested workflows, not completed lookups. Report missing, restricted, or partial data explicitly; verify the live response before making a decision.

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

One request fetches one page. Copy nextCursor into cursor, or nextPage into page (1–11 for Reels), then run manually. Repeated requests may purchase data again. Completed lookups have a minimum charge of 10 credits, including cached, no-caption, private, restricted and not-found results. Resource status and actual billing status are independent; null credits are unknown, never free. Check usage.billingStatus, usage.chargedCredits and API usage records for the actual charge.

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/instagram/reelsSearch
MCP method
social_instagram_reels_search
cURL
curl -X POST \
  https://api.nexscope.ai/instagram/reelsSearch \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "coffee" }'
Request estimate: Estimating…Usage based. The final charge depends on actual usage. Estimating does not run the API or charge credits.API usage records
Response
No response yet. Run the request to see the response here.

Related APIs