instagram-search

What Instagram's search box shows for a query, one row per hit: kind (user, hashtag, place), name (username, #tag or place name), title (full name, the hashtag's post count text, or the place's address), followers (Instagram's rounded count for a user), media_count (exact, for a hashtag), is_verified, url. kind is users, hashtags, places or all (all = Instagram's blended list: users for a word, hashtags for a #word). session is required: your sessionid and csrftoken cookies, copied with the Crawl4AI Session extension; used for this run only and never stored. One fetch, 1 unit.

stagedinstagram.comWASM module7 fields2 unitsalways live
‹ Recipes
…json
POST api.crawl4ai.com/recipes/…

$ crawl recipe

              
Live · your key · counts against your quota✓ 200 OK
# Hit Run - the rows render here as a table, with the cost

Fields

7 columns on every row. null means the site does not state it.
fieldtypemeaning
kindstring
namestring
titlestring
followersinteger
media_count
is_verifiedboolean
urlstring

null means the site does not state it.

kindstring
namestring
titlestring
followersinteger
media_count
is_verifiedboolean
urlstring

How it behaves

Cost. 2 units. A failed run costs 0.

Always live. Every run reads the site again; nothing is served from cache.

Your session. It needs your own logged-in session for the site, copied with the Crawl4AI Session extension. It is used for that run only and not stored.

Questions about this recipeQuestions

Short answers. The API reference has the long ones.

Call POST /recipes/instagram-search with your key and query and kind. You get rows with the 7 fields above. It needs your own session for the site. The recipe is tested against the live site every 6 hours.

Need more from Instagram?

Extra fields, higher volume, or a private copy with a freshness SLA. We build it on Enterprise.

Request a change

For developers

Get a free API key and run your first crawl.

1,000 credits every month. No credit card. Your self-hosted setup keeps working.

For teams

Talk to us about volume, regions and an SLA.

A 30-minute call with the team that writes the crawler. DPA on request, invoice billing, your choice of US, EU or Singapore.