Instagram Reels API
Use the Instagram Reels API to read an account’s public Reel links, covers and available play, like and comment counts. Organize the returned content into a worksheet, then request another page when your task needs it.
1 credit per successful request, including empty results. Failures are free. Each page is billed separately.
https://api.goanyapi.com/api/v1/instagram/user/reelsRun a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Organize an account’s Reels and engagement data
An account review can begin with source links, covers and available interactions. The Instagram user Reels API returns those records with pagination values, letting an analyst assemble a worksheet and choose content for a report. Keep each resource attached to its available metrics and your own notes, then record which pages you requested so colleagues can understand how the working set was assembled.
Work through the saved @peggyzou89 page
The saved response for @peggyzou89 contains twelve Reel records. Start with that username or a supported profile URL in username; omit cursor for the first request. The first saved record has shortcode DcuF5s7BIUh and 1,174,904 plays, with likes and comments also present. Its caption is null. Every one of the twelve saved records has an empty video address array. A useful output is therefore a review table of actual resource links, covers and available interactions, with missing captions explicitly noted for your editorial or analysis workflow.
- data.result.posts[].code
- Keep each shortcode with the resource URL from the same record. Together they let a reviewer connect a worksheet entry to the content it describes.
- data.result.posts[].play_count
- The first saved record has 1,174,904 plays. Put available plays, likes and comments in separate columns, then explain any comparison or sorting you perform yourself.
- data.result.posts[].video_urls
- All twelve saved arrays are empty. Covers and resource links still support content selection, while the response supplies no direct video address for these records.
- data.result.posts[].size
- The saved arrays contain two null entries. Caption, publication time and audio status are also null. Keep those unknowns instead of deriving dimensions or dates from other fields.
- data.result.next_cursor
- Continue with the same account only when the more-results flag is exactly true and the next cursor is nonblank and different from the current one; otherwise stop.
Understand page size, continuation and cost
Each request asks for twelve records; fewer may be returned. There is no public page-size control, date range or guarantee of complete account coverage. Every successful request, including an empty page, uses the current configured rate; failures are free. Requesting another page is a separate chargeable request. Read the Reels documentation before adding continuation to your client.
Build a content worksheet from account Reels
Choose records, compare available counts and collect source links for the report your team is preparing.
Create an account content worksheet
A creator researcher can place each shortcode, resource link and cover in one row. Add project notes and capture context in their own sheet, giving colleagues a practical list of content to review.
Compare returned interaction counts
An analyst can group available play, like and comment values beside the matching content links. Sort the observed records using their own method to choose examples for a report, keeping the original counts available for review.
Browse a cover-based selection
A review tool can show actual covers beside their resource links, helping an editor select content for closer reading. Readable identifiers and image fallbacks keep the selection usable when an individual cover fails.
Inspect a selected Reel in detail
An editor can take a selected resource link to the separate post details endpoint for an additional observation. Add any returned caption or media information to their own content note, recording that request separately.
Collect to a chosen page limit
A developer can set a request limit in the client, follow valid returned cursors and store progress in their own system. This produces a collection whose requested pages and stopping condition are explicit.
Give an Agent a content task
An HTTP-capable Agent can request a chosen number of pages under the public POST contract, then summarize the observed records. Configure authorization securely and specify the permitted request count in the client workflow.
Questions about account Reels and pagination
This endpoint starts with an account and returns a page of Reel records. Post details starts with one known content link or shortcode. Choose the account list for a bounded review set, and use the detail endpoint for a specific resource you already identified.
Each request asks for twelve records and may return fewer. For more records, use a valid returned cursor with the same account. The request does not accept a custom page-size parameter or a numeric offset.
No. All twelve saved video address arrays are empty. The records still include resource links and covers. The interface can display those returned values, but cannot promise a downloadable file for every Reel or a permanent media URL.
Stop. Continue only when the more-results flag is exactly true and the returned cursor is a nonblank string different from the current cursor. Keep the same account input. Missing, empty or repeated cursors do not provide a valid next page.
Further pages require explicit client requests. Successful requests, including empty results, use the current configured rate; failed requests are free. Your client handles collection and persistence.
Keep null, empty strings, empty arrays and missing fields distinct from actual zero or false values. The saved captions, publication times and audio flags are null. Preserve those observations when producing your own summary or comparison.
Add context to the Reels you selected
Read one known post in detail, check the account’s public profile or inspect highlight collection metadata. Each request has its own scope and cost; assemble the resulting review in your own client.