Public identity, useful context

Instagram Profile API

Use the Instagram Profile API to read public account identity, bio, avatar and available follower counts from a username or profile link. Create a reference row for a creator shortlist or an account directory.

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

POSTExample response
https://api.goanyapi.com/api/v1/instagram/user/profile
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.

Build an account reference for your research

A creator shortlist needs more than a display name: a name may be shared by several accounts, a bio may be empty and a follower count is only one observation. The Instagram user profile API helps a researcher keep those distinctions in a consistent record. Start with the account you intend to review, read its available public fields, and add your own evaluation alongside the source data.

Read Wudang story, @peggyzou89

The saved response is for @peggyzou89, with the full name Wudang story. A request for this resource can use its username, @username or full profile URL in username. The saved sample contains 23,722 followers and 66 following, an empty biography and a false verification value. Treat the numbers as saved observations, not live totals. A useful output is an account reference row containing the returned identity, available counts and an explicit note that the bio was empty. Any creator category or suitability judgment belongs in your own analysis column.

data.result.username
The returned handle is peggyzou89 in the sample. Put it beside the full name so a reader can identify which public account the reference concerns.
data.result.full_name
Wudang story is the saved full name. It makes the directory readable while the handle and returned identifiers retain the account context for your records.
data.result.biography
The sample biography is an empty string. Display that absence explicitly and keep the original value, rather than writing a description inferred from the account name.
data.result.follower_count
The saved account has 23,722 followers and a separate following count of 66. Put the observations in separate columns and record your own capture context for later comparisons.
data.result.is_verified
False is a returned verification value. It belongs alongside the other account facts and remains distinct from null or a field that was never supplied.

Public profile data and clear billing

This is a single account response with no pagination. It does not include private information, contact details, follower identities or a post list. Each successful request, including an empty result, is charged at the current configured rate; failures are free. Opening the saved example does not make a new query. Use the profile documentation for the POST contract and accepted inputs.

Turn profile facts into useful account references

Choose a shortlist, directory or research brief, and keep your own selection criteria beside the returned facts.

Prepare a creator shortlist

A partnership researcher can record the handle, full name and available follower counts in a candidate sheet. Add selection criteria in a separate column so colleagues can see the facts behind each proposed contact.

Connect internal account records

A developer can retain returned identifiers as exact strings and attach them to internal account references. This gives their application a consistent place to organize profile observations, project notes and links collected through their own workflow.

Edit a directory with source text

A directory editor can carry over the actual biography and distinguish an empty bio from text that was provided. Keep editorial additions separately, giving future reviewers a clear source for each public description.

Create a readable account header

A review interface can combine the avatar address, full name and handle in one compact account header. Keep the text available as an image fallback so staff can continue reading the other profile fields.

Compare observations you save

An analyst can record counts from separate authorized queries with their own capture times, then compare those stored observations. The resulting worksheet helps explain exactly which values support the team’s account research.

Draft an Agent profile brief

An HTTP-capable Agent can request the profile using the public POST contract, then summarize identity and available counts for a brief. Configure authorization securely in the client and keep the output separate from its credentials.

Questions about public profile data

Use a username, @username or a supported full Instagram profile URL. Supported profile URLs may include a reels or tagged suffix; that still selects the account for this profile endpoint. It does not switch the response into a Reels or tagged post list.

No. The profile response provides available counts, not a list of followers or following accounts. It also does not disclose private account content, email addresses, telephone numbers or audience demographics. Choose this endpoint for public profile context rather than contact discovery.

No post collection is included. If your next task concerns an account’s public Reels, make a separate request to that endpoint. A known post link belongs in the post details endpoint. Combining those results into a creator report is your own workflow.

The saved bio is an empty string and the verification field is false. Preserve both rather than replacing them with guessed content or a generic error. Null, missing fields and a real zero count should also remain distinct in your application.

No automatic monitoring is included. You may arrange separate requests, save observations and compare them in your own system. Current freshness and complete coverage are not guaranteed by the saved sample. Check the configured rate before each workflow that may issue multiple requests.

RELATED APIS

Add content context to your account research

Use a separate post query for one content link, a highlights query for collection metadata or a Reels query for returned video records. Keep each result’s scope visible when you assemble your own creator brief.