The Instagram API for products and pipelines.
Retrieve supported public Instagram data — profiles, posts, reels, comments, story highlights, tagged posts, and location feeds — through REST endpoints that return one consistent response model.
- 13 supported endpoints
- Public data only
- Fetched at request time
/v1/instagram/users/{username}200OKWhat you can pull from Instagram.
Almost everything you can reach on Instagram hangs off a profile. A profile lookup returns bio, follower and post counts, and the links in the bio as normalized attachments. Posts, reels, and tagged posts are three separate cursor-paginated feeds, so a workload that only wants reels does not have to filter a mixed feed. A carousel arrives as one post with its children nested inside it rather than as several posts.
Story highlights are two calls, not one: the highlights endpoint lists the reels on a profile, and the highlight endpoint returns the story items inside one of them. Location feeds take a numeric Facebook Places ID, which is worth resolving once and storing rather than looking up per run.
Every response uses the same ActivityStreams 2.0-based model as the other supported platforms, so a Instagram integration reuses the parsing you already wrote. Fields specific to Instagram stay as documented first-class fields rather than being flattened away.
- Profiles with normalized bio links
- Post, reel, and tagged-post feeds
- Single posts, including carousels
- Post comments
- Story highlights and their items
- Trending media search and location feeds
All 13 Instagram endpoints.
Grouped by what they return. Every one has its parameter contract, a request you can copy, and an example response.
Profiles
1The account record: bio, follower and post counts, and the bio links as normalized attachments.
Feeds
4Posts, reels, tagged posts, and highlight reels as separate feeds, so a run that only wants reels never filters a mixed one.
Posts
2One post by shortcode, with a carousel arriving as one object with its children nested inside — and the story items inside a highlight.
Comments
1The comments on a single post, 15 to a page.
Discovery
5The two ways in without a username: trending media for a keyword, and the posts attached to a Places ID.
How the calls fit together.
Few Instagram jobs are a single request. Most are two or three chained, each call keyed by an id the one before it returned.
Benchmark an account
Read the profile for the denominator, then a page of posts for what a typical post actually does.
Read a post’s response
Take the post for its media and counts, then its comments for what the audience said.
Mine story highlights
List the highlight reels on a profile, then open one for the story items inside it.
What shapes your Instagram integration.
Page sizes, ordering, and what the platform itself withholds — the details that decide how you build, settled before you write a line of code.
- 01Feeds page 12 at a time
- Posts, reels, and tagged posts return at most 12 items per page. Comments have a fixed page size of 15 and location feeds a fixed 21 — both are the platform’s own limits, not options.
- 02Search surfaces trending media, not everything
- The search endpoint returns trending reels and videos matching a keyword, up to 24 per page. It is not a full-text index: a perfectly valid keyword can return nothing because nothing is currently trending for it.
- 03Highlights are a two-step read
- The highlights endpoint returns the reels on a profile. The story items inside one come from the highlight endpoint, keyed by an id from that list.
- 04Posts are addressed by shortcode
- A single post is fetched by its shortcode — the segment in its permalink — rather than by a numeric id.
Other platforms
Build on Instagram data.
Get a free API key and call any of these endpoints in minutes. No credit card required.