Instagram API

Instagram Post API

A single Instagram post or reel by URL: id, shortcode, type, owner, like count and media URLs.

POST/v1/run/instagram.post
Uptime
99.90%
30d · 15,524 calls
Requests
15,571
30d · weekly, last 12 wks
Response
3.7s
median · 30d

Provider network

Providers ranked by traffic

Providers
Lynx8,103 served99.98% uptime970ms p5054.1%$1.50/1k reqflatBadgerTried first4,753 served76.02% uptime7114ms p5031.7%$0.50/1k reqflatGiraffe2,095 served97.76% uptime2180ms p5014.0%$1.20/1k reqflatQuokka22 served68.75% uptime4140ms p500.1%$0.80/1k reqflat

Try it

Make your first request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `plays`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a post that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
  "found": true,
  "data": {
    "id": "3401000000000000000",
    "shortcode": "C8aBcDeFgHi",
    "type": "XDTGraphVideo",
    "owner": "nasa",
    "likes": 1840000,
    "displayUrl": "https://instagram.com/p/C8aBcDeFgHi/media.jpg",
    "videoUrl": "https://instagram.com/p/C8aBcDeFgHi/media.mp4"
  }
}
Response interface
interface InstagramPostResponse {
  data: {
    bytes?: number;
    displayUrl: string;
    expiresUtc?: number;
    hostedUrl?: string;
    id: string;
    likes: number;
    owner: string;
    plays?: number;
    shortcode: string;
    type: string;
    videoUrl: string;
  } | null;
  found: boolean;
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

Request, response, and price

Last verified 2026-09-17 · uptime and latency measured over 30d
POST /v1/run/instagram.post
curl -X POST https://api.getanyapi.com/v1/run/instagram.post \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.instagram.com/p/C8aBcDeFgHi/"}'
FieldTypeExample value
Request body
urlstring"https://www.instagram.com/p/C8aBcDeFgHi/"Full Instagram post or reel URL, carrying the media shortcode: /p/, /reel/, /reels/, or /tv/. A profile URL such as https://www.instagram.com/username names no post, so it is rejected instead of charged for an empty result - send that account's handle to instagram.profile, or its posts to instagram.user_posts.
hostVideobooleanSet true to also get the post's video on a hosted MP4 link that plays without an Instagram session. The file is downloaded and stored for you, and the response adds `hostedUrl`, `expiresUtc` and `bytes`. It is charged as an extra on top of the price, and it never changes which source serves you: every source offers it at the same price. A post with no video, or a post that does not exist, is refused with no charge rather than billed for a file that cannot exist. Omit it and nothing is downloaded, nothing is stored, and nothing extra is charged.
requireFieldsarrayOptional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `plays`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a post that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
requirePlayCountbooleanDeprecated; send `requireFields: ["plays"]` instead, which does exactly the same thing. Set true to be served only by a source that reports a reel's play count. Omit it and routing is unchanged, with the cheapest source serving, which does not carry play counts, so `plays` is absent from its responses. This can raise your price: opting in routes to a source that reports the count, and you are quoted and charged its price. It stays accepted so callers that already send it keep working.
Response
foundbooleantrue
dataobject
data.idstring"3401000000000000000"
data.shortcodecan requirestring"C8aBcDeFgHi"
data.typecan requirestring"XDTGraphVideo"
data.ownerstring"nasa"
data.likescan requirenumber1840000
data.displayUrlstring"https://instagram.com/p/C8aBcDeFgHi/media.jpg"
data.videoUrlcan requirestring"https://instagram.com/p/C8aBcDeFgHi/media.mp4"
Price
Price per requestUSD$0.0005
Price /1k reqUSD$0.50

FAQ

About the Instagram Post API

The AnyAPI Instagram Post API returns Instagram post data as normalized JSON from one POST call to /v1/run/instagram.post. A single Instagram post or reel by URL: id, shortcode, type, owner, like count and media URLs. AnyAPI routes each request across 4 sources and falls back automatically when one fails. It costs from $0.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 99.9% of Instagram post calls through AnyAPI succeeded, with a median response time of 3.7 seconds across 15,524 measured calls.

It costs from $0.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

A single Instagram post or reel by URL: id, shortcode, type, owner, like count and media URLs. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 99.9% of Instagram post calls through AnyAPI succeeded, with a median response time of 3.7 seconds across 15,524 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.
More to call

Other Instagram endpoints

Profilefrom $1.20 /1k reqUser postsfrom $0.80 /1k reqUser reelsfrom $0.80 /1k reqPost commentsfrom $0.80 /1k reqHashtag searchfrom $1.20 /1k reqAudio reelsfrom $1.20 /1k reqBasic profilefrom $1.20 /1k reqComment repliesfrom $1.20 /1k reqEmbedfrom $1.20 /1k reqFollowersfrom $1.50 /1k reqFollowingfrom $1.50 /1k reqHashtag analyticsfrom $1.93 /1k resultsHashtag recent postsfrom $1.50 /1k reqHashtag top postsfrom $1.50 /1k reqHighlight detailfrom $1.20 /1k reqLocation postsfrom $1.20 /1k reqMedia transcriptfrom $1.20 /1k reqPost likersfrom $2.40 /1k reqProfile contactfrom $2.57 /1k reqReel transcriptfrom $5.94 /1k audio minutesReels searchfrom $1.50 /1k reqSearchfrom $3.60 /1k reqSearch locationsfrom $2.40 /1k reqSearch profilesfrom $1.20 /1k reqSimilar profilesfrom $2.40 /1k reqStories fullfrom $2.40 /1k reqStories thinfrom $1.50 /1k reqTagged postsfrom $1.50 /1k reqTrending reelsfrom $1.20 /1k reqUser highlightsfrom $1.20 /1k reqUser repostsfrom $1.20 /1k reqWeb reels searchfrom $1.20 /1k req