Instagram Content discovery API

Q: Is keyword a full-text search?

No. In Instagram Content discovery, keyword is a hashtag: a leading # is removed and the tag itself is looked up, so coffee and #coffee make the same request. Words that appear only in captions are not searched. The Instagram Hashtag capability also lists a tag's posts or reels, synchronously and under a different parameter name.

Q: How do I get Reels instead of regular posts?

Set results_type to reel or reels; both switch Instagram Content discovery to short-video results. Leave the parameter out for regular posts: posts is not a value you can send, and any other value is rejected with a 422 error when parameters are checked. The parameter picks the kind of content, not an output format such as JSON or CSV.

POST

API health

24h health: 100%
24h average time: 35.87 s

Healthy / normal
Available
Limited
Mostly down

Healthy

Last 24 hours

Last 30 days

Track posts under an Instagram hashtag passed in keyword, with caption, media type, engagement counts, author follower count, location and post time. Set results_type to reels for short videos; the results do not explain Explore ranking or prove a trend.

Instagram Content discovery lists public posts under one hashtag, which you pass as keyword, and returns each post's caption in text, its media_type (image, video or carousel), like, comment and view counts, the author's handle, display name and follower count, the publish time and location text. Marketers and trend researchers use it to see what people post under a tag, which formats draw engagement and which accounts post under it most.

keyword is a hashtag word such as coffee, with or without the leading #, not a free-text search phrase. Leave out results_type for regular posts, or set it to reel or reels for short-video results. The capability is async: the call returns a job_id instead of rows, and you fetch the results with that ID later. A null like_count, comment_count or view_count means the number was not disclosed, not that it is zero.

Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Asynchronous by default: returns a job_id first; poll GET /api/v1/jobs/{job_id}.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Instagram Content discovery endpoint (instagram/discover).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to instagram and action to discover, and put the parameters inside params.
- Required parameters:
  - keyword: Specifies the target hashtag string for the discover action, automatically stripping leading # symbols.
- Optional parameters:
  - results_type: Selects the content type for discover and hashtag: omit it for regular posts, or pass reel or reels for short videos. posts cannot be passed explicitly, and any other value returns 422. (allowed: reel / reels)
  - limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 30)
- Returns a list of records. Main fields of each record: post_id, url, text, media_type, like_count, comment_count, view_count, author_username, author_name, posted_at, location, author_follower_count; 14 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=instagram.
- Example request body:
{
  "platform": "instagram",
  "action": "discover",
  "params": {
    "keyword": "coffee"
  }
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- This endpoint is asynchronous by default: it returns 202 and a job_id, then you poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} until the status is succeeded or failed.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`instagram`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`discover`	Capability identifier, fixed value.
`keyword`	body.params	Not declared	Yes	-	Specifies the target hashtag string for the discover action, automatically stripping leading # symbols. This parameter queries hashtags rather than executing general full-text searches, and differs from the tag parameter in the hashtag action.
`results_type`	body.params	`enum`	No	-	Selects the content type for discover and hashtag: omit it for regular posts, or pass reel or reels for short videos. posts cannot be passed explicitly, and any other value returns 422. It does not choose the response file format.Allowed values`reelreels`
`limit`	body.params	`integer (1–200)`	No	`30`	The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "instagram",
  "action": "discover",
  "params": {
    "keyword": "coffee"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "instagram",
  "action": "discover",
  "results": [
    {
      "post_id": …,
      "url": …,
      "text": …,
      "media_type": …,
      "like_count": …,
      "comment_count": …,
      "view_count": …,
      "author_username": …,
      "author_name": …,
      "posted_at": …,
      "location": …,
      "author_follower_count": …,
      "hashtags": …,
      "top_comments": …
    }
  ],
  "count": …,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`post_id`	Keeps the platform's own meaning
`url`	Link to the record on the platform.
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`media_type`	Keeps the platform's own meaning
`like_count`	Likes. null means the platform or this capability does not disclose it; it is not 0.
`comment_count`	Comments. null means not disclosed, not 0.
`view_count`	Views or plays. null means not disclosed, not 0.
`author_username`	Author's username (@handle), usually usable in URLs.
`author_name`	Author's display name.
`posted_at`	Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
`location`	Location description passed through as is; the format varies by platform.
`author_follower_count`	Author's follower count. null means not disclosed.
`hashtags`	Hashtags in the text, in order of appearance; absent when there are none.
`top_comments`	Keeps the platform's own meaning

FAQ

How do I get the results of an async discovery call?

Instagram Content discovery is async, so the call answers with a job_id rather than rows. Store that ID and use it to fetch the results later; your code makes two steps, submitting the hashtag and then collecting the rows. Keep the keyword and results_type you sent beside the job_id, so each result set stays tied to its request.

Is `keyword` a full-text search?

No. In Instagram Content discovery, keyword is a hashtag: a leading # is removed and the tag itself is looked up, so coffee and #coffee make the same request. Words that appear only in captions are not searched. The Instagram Hashtag capability also lists a tag's posts or reels, synchronously and under a different parameter name.

How do I get Reels instead of regular posts?

Set results_type to reel or reels; both switch Instagram Content discovery to short-video results. Leave the parameter out for regular posts: posts is not a value you can send, and any other value is rejected with a 422 error when parameters are checked. The parameter picks the kind of content, not an output format such as JSON or CSV.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).