1. Official Instagram Graph API (Business Discovery) vs ShortVid Instagram API
Meta's Graph API was engineered for brands managing their own connected accounts — not for creator discovery, UGC analytics, social listening, or competitive Reel benchmarking.
| Capability / Requirement | ShortVid Instagram API | Meta Graph API (Business Discovery) | DIY Playwright / Session Cookies |
|---|---|---|---|
| Setup & Authentication | Instant x-api-key (10,500 free credits on signup) | Meta App Review + Facebook Page + IG Business OAuth | Burner IG accounts + rotating residential proxies |
| Personal Creator Accounts | Supported (any public @username) | Blocked (Error #110: Business/Creator accounts only) | Supported until session checkpointed |
| Public Reel Play Counts (play_count) | Included in /v1/instagram/reels | Omitted on third-party Business Discovery | Requires GraphQL doc_id reverse engineering |
| Direct CDN MP4 Stream (video_url) | Included in /v1/instagram/post & Reels | Omitted on third-party media objects | Expires quickly; triggers 429 checkpoint bans |
| Post & Reel Comments (/comments) | Paginated top-level comments ($0.10/1K) | Restricted to your own authenticated media | Strict login wall after 1-2 requests |
| Burst Rate Limit Handling | 60–600 RPM + multi-source automatic failover | 200 calls / user / hour rolling bucket | Frequent HTTP 429 & SMS challenge locks |
2. All 4 Standardized Instagram Endpoints & Credit Pricing
Every Instagram route normalizes upstream payloads into a clean, predictable JSON schema under the standard ShortVid envelope (code === 0) and shares your existing credit balance ($1 = 10,000 Credits).
| Canonical Endpoint | Accepted Route Aliases | Key Parameters | Edge Cache TTL | Credit Rate & USD Cost |
|---|---|---|---|---|
| GET /v1/instagram/profile | /v1/instagram/user, /v1/ig/profile | username (@handle or URL) | 3,600s (1h) | 10 Credits / call ($1.00 / 1K) |
| GET /v1/instagram/reels | /v1/instagram/user/reels, /v1/ig/reels | username, count (<=50), cursor | 900s (15m) | 2 Credits / reel ($0.20 / 1K, min 10) |
| GET /v1/instagram/post | /v1/instagram/media, /v1/ig/post | shortcode, url, or media_id | 1,800s (30m) | 10 Credits / call ($1.00 / 1K) |
| GET /v1/instagram/comments | /v1/instagram/post/comments, /v1/ig/comments | shortcode, count (<=50), cursor | 900s (15m) | 1 Credit / comment ($0.10 / 1K, min 10) |
3. Production Code: Fetch Instagram Profile, Reels Feed & Direct MP4 URL
Below are runnable cURL, Python, and TypeScript examples that paginate a creator's Reels feed and resolve direct MP4 video streams by shortcode.
Fetch Instagram Reels & Post MP4 Stream
Query @nike's public Reels feed at $0.20/1K reels, then inspect a single Reel shortcode for full caption and CDN MP4 stream.
# 1) Paginated Reels feed (2 Credits / reel)
curl -sS "https://api.shortvidapi.com/v1/instagram/reels?username=nike&count=12" \
-H "x-api-key: $SHORTVID_API_KEY"
# 2) Single Reel / Carousel detail + direct MP4 video_url (10 Credits)
curl -sS "https://api.shortvidapi.com/v1/instagram/post?shortcode=DfpU4xcsnw8" \
-H "x-api-key: $SHORTVID_API_KEY"Interactive Engineering Workbench · GET /v1/instagram/reels
Verify real-time latency, pagination math & JSON schema
Frequently Asked Questions
- Do I need an Instagram account, sessionid cookie, or Meta App Review to use the Instagram Reels API?
- No. ShortVid API handles upstream session rotation and multi-source failover internally. You only pass your x-api-key header over standard HTTPS GET.
- What happens if an Instagram handle is private, deleted, or has zero Reels?
- Non-existent handles, private profiles, and empty Reels pages deduct 0 Credits. You are only billed when HTTP 200 is returned with code === 0 and non-empty items.
- Can I pass full Instagram URLs instead of extracting shortcodes or usernames manually?
- Yes. /v1/instagram/profile and /v1/instagram/reels automatically clean @handles and https://www.instagram.com/<username>/ URLs, while /v1/instagram/post and /v1/instagram/comments accept shortcodes, numeric media_ids, or full /reel/<shortcode>/ and /p/<shortcode>/ URLs.