Skip to main content
GET
reels
One page of reels as raw Instagram media objects under items[].media, with paging_info.max_id for the next page. Each reel carries code, caption, like_count, comment_count, video_versions, image_versions2 and clips_metadata. clips_metadata.original_sound_info.audio_asset_id is exactly the id get_instagram_song_reels takes — that is the practical way to get one without a /reels/audio/ URL in hand. Pass user_id rather than handle for a faster response. Measured at about 594 KB per page. For the whole timeline including photos and carousels, use get_instagram_user_posts.

Example

First time? Point any MCP client at https://mcp.aisa.one/mcp — Claude Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client opens a browser, you click Allow once, and there is no key to paste. Your agent then reaches every endpoint through five tools: search, list_categories and get_details are free, use and batch_use are billed per call. Setup per client is in Connect via MCP; the live tool list and what each call costs are on aisa.one/mcp.
Set this endpoint up in your agent →

Cost and request rules

Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.00188
  • Cost contract: response_count
  • Published reference multiplier: 1.0
  • Settlement evidence source: response_body

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

handle
string

Response

Successful response

success
boolean
credits_remaining
integer
items
object[]
next_max_id
string | null
max_id
string | null