Collection metadata, clearly separated

Instagram Highlights API

Use the Instagram Highlights API to read public collection names, identifiers and covers for an account. Create a title-and-cover inventory for a brand profile review, with each label linked to its original collection record.

1 credit per successful request, including empty results. Failures are free.

POSTExample response
https://api.goanyapi.com/api/v1/instagram/user/highlights
Visual

Run 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.

Create an inventory of an account’s highlight collections

For a brand profile review, highlight collection names and covers can provide useful organizational context. The Instagram highlight collections API returns that directory in a structured form so a researcher can make a clear inventory. Your own review can discuss naming or presentation, while the source record remains limited to the collection metadata actually returned. The endpoint does not inspect the Stories inside those collections.

Inspect seven saved collections from @instagram

The saved example belongs to @instagram and contains seven collection records. To request this account, supply instagram, @instagram or a supported full profile URL in username. In the saved result, one collection is named creatives, another what’s new, and others use emoji titles. Each record has a collection identifier and a cover address. Use these relationships to make your own title-and-cover inventory, keeping the original title beside any internal category you assign. Seven is the count in this historical sample, not a fixed response size or a promise about the account today.

data.result.username
The username attaches the inventory to its account. In the saved example it is instagram. Keep that context when placing collections from several accounts in your own worksheet.
data.result.count
The saved count of seven describes collections in this response. Retain it beside the observed list; it is neither a Story count nor an all-time collection total.
data.result.highlights[].id
Each identifier references a collection. Preserve the exact string with its title and account so similarly named collections remain separate in your own records.
data.result.highlights[].title
Keep text and emoji titles exactly as returned. Put any translation or internal category alongside the original, making your own interpretation easy to distinguish from the source label.
data.result.highlights[].cover
The address can supply a cover preview beside the matching name and identifier. Handle unavailable images with a text fallback; the cover is not the collection’s individual Story media.

A collection directory with no pagination

This endpoint returns collection metadata only: no individual Story media, playback, view counts or expired Story retrieval. It has no cursor or next page operation. All successful requests, including empty results, use the current configured rate; failures are free. URL parsing is included within the same request. The highlights documentation explains the supported account input and response fields.

Use collection names and covers in a profile review

Create an inventory first, then add the naming, visual or organizational observations your team wants to discuss.

Prepare a brand presentation review

A brand reviewer can place returned names and covers in a reference sheet, then add their own notes about naming consistency and presentation. The collection inventory supplies concrete material for that discussion.

Retain original collection titles

An editor can preserve text and emoji labels while adding a translation or explanation in a separate column. Colleagues can see the wording used by the account and the context the team added.

Create a cover contact sheet

A developer can pair each actual cover address with the title and identifier from the same record. This gives a reviewer a visual directory with readable labels when an image is unavailable.

Organize similarly named collections

A researcher can group records by account and collection identifier before adding internal topics. Keeping those references together helps distinguish collections with shared names in the researcher’s own inventory.

Review captured inventories over time

A team can make separate queries, store its own observations and compare captured labels or cover references. Keeping each capture’s context makes the resulting comparison traceable to the records the team actually saved.

Ask an Agent to summarize labels

An HTTP-capable Agent can query the public POST endpoint and group returned titles for a profile brief. Configure authorization securely in the client, then keep the original labels beside the Agent’s suggested categories.

Questions about highlight collections

No. It provides the collection directory: identifiers, titles and covers. It does not return the collection’s individual Story images or videos, frames, playback information or viewing metrics. Use the response for metadata review rather than a Story archive or downloader.

This endpoint takes an account input, not a highlight identifier. A returned collection ID can be kept in your own inventory, but should not be presented as a supported input to another Story retrieval operation. No such capability is included here.

No. Seven is the number in the saved @instagram sample. Another account or another request may return a different count or an empty result. This endpoint has no pagination and the sample does not establish complete coverage of an account’s historical collections.

Keep the actual value and show a clear text fallback. Null, empty strings, empty arrays and missing fields are distinct, while zero and false remain actual values if supplied. An unavailable cover image does not justify replacing or discarding the collection identifier.

No. The initial example is a saved response. Only an explicit query sends a new request, and every successful request, including an empty response, uses the current configured rate. Failed requests are free. Confirm that rate before repeating queries in your own workflow.

RELATED APIS

Continue from collections to account or content context

Request an account profile, inspect one known post or retrieve an account’s Reels through their separate endpoints. Combining these observations can inform your own review, but does not turn highlight metadata into Story contents.