The Instagram Search API: Account Lookup vs Topic Discovery

If you want to search Instagram without logging in or wrestling the official Graph API, there are two distinct endpoints, and the most common mistake is reaching for the wrong one. One is for finding entities (accounts, hashtags, places). The other is for exploring a topic and its content. They look similar from the outside and answer completely different questions. This is the quick, honest map of which to use when.

The two endpoints in one glance

• Search (/v1/scrape/instagram/search) — Instagram's native search. Give it a query and it returns matching users, hashtags, and places in a single page. It's for lookup and disambiguation. It does not return posts.
• Popular Search (/v1/scrape/instagram/search/popular) — topic exploration. Give it a topic and it returns a generated description, suggested terms, total media count, and a page of curated posts (with play counts and owners), paginated by cursor.

Rule of thumb: Search answers "which account/tag/place is this?" and Popular Search answers "what's this topic about and what's working in it?" Both are 1 credit, use the x-api-key header on https://api.sociavault.com/v1, and return the payload under data.

When to use Search (entity lookup)

Reach for Search when you have a name and need to resolve it to something specific:

• Finding a brand's official account among impersonators (rank by the is_verified flag).
• Resolving a handle to a numeric user_id for the endpoints that require one.
• Powering an account autocomplete in your own product.
• Discovering related hashtags with their media_count for tag research.

const API_KEY = process.env.SOCIAVAULT_API_KEY;
const BASE = "https://api.sociavault.com/v1";

async function search(query) {
  const qs = new URLSearchParams({ query }).toString();
  const res = await fetch(`${BASE}/scrape/instagram/search?${qs}`, {
    headers: { "x-api-key": API_KEY },
  });
  return (await res.json()).data; // { users, hashtags, places, keywords, rank_token }
}

We go deeper on that in finding a brand's real account.

When to use Popular Search (topic discovery)

Reach for Popular Search when you have a topic and want to understand or mine it:

• Niche research, what a topic is about and roughly how big it is (total_media_count).
• Finding top content, the curated posts, sortable by play_count.
• Keyword expansion, the suggested_terms for content planning.

async function popular(query, cursor) {
  const params = { query };
  if (cursor) params.cursor = cursor;
  const qs = new URLSearchParams(params).toString();
  const res = await fetch(`${BASE}/scrape/instagram/search/popular?${qs}`, {
    headers: { "x-api-key": API_KEY },
  });
  return (await res.json()).data; // { title, total_media_count, description, suggested_terms, posts, cursor, has_more }
}

The deeper guide: topic/niche research.

Using them together

The two shine as a pair. A realistic flow:

1. Popular Search a topic to find the top posts and the creators (owner) behind them.
2. Search each creator's handle to resolve their user_id and confirm the account.
3. Hand those IDs to the profile/reels endpoints for the deep dive.

That's discovery → resolution → enrichment, topic in, specific accounts out.

The honest limits (shared by both)

• Both return a sample, not an index. Search gives one page of top matches; Popular gives a curated page of posts. Neither enumerates everything, that's by design, and it's the right shape for lookup and research.
• Objects are keyed by index. users, hashtags, places, posts, and suggested_terms all come back keyed by index (0, 1, ...). Parse with Object.values() / .values(), not as arrays. This trips up almost everyone once.
• Search has no posts; Popular has no follower stats. They're deliberately scoped. Combine them (and the profile endpoint) when you need the full picture.
• Popular's description is auto-generated and its posts skew to reels, useful, but verify facts and know the format bias.
• Public data only, 1 credit each. No login-gated results, and debounce/cap any search-as-you-type or expansion so you don't overspend.

Frequently Asked Questions

What's the difference between the two Instagram search endpoints?

Search (/instagram/search) finds entities, users, hashtags, and places, for lookup and disambiguation, and returns no posts. Popular Search (/instagram/search/popular) explores a topic and returns a description, suggested terms, total media count, and curated posts. One answers "which account is this?"; the other "what's this topic about?"

Which one do I use to find an account?

Search. It returns matching accounts with username, full_name, id, is_verified, and profile_pic_url, ideal for resolving an official account, getting a user ID, or powering autocomplete. Popular Search won't help there; it's topic-oriented.

Which one returns posts?

Popular Search. It returns a curated, paginated page of posts (with play_count and owner) for a topic. Plain Search returns entities only, no posts, so use Popular when you want content.

Do both cost the same?

Yes, 1 credit per call for each. They just answer different questions, so you pick based on whether you're resolving an entity (Search) or researching a topic (Popular Search).

Can I use them together?

Absolutely, that's the strongest pattern. Use Popular Search to find top posts and their creators, then Search to resolve each creator's handle to a user ID, then enrich with the profile and reels endpoints. Discovery, resolution, enrichment.

Why do the responses use objects keyed by index?

Both endpoints return collections (users, posts, suggested_terms, etc.) keyed by index rather than as JSON arrays. Iterate them with Object.values() in JavaScript or .values() in Python, forgetting this is the most common integration bug.

---

Want both kinds of Instagram search in one API? Start free with 50 credits, no card required and try account lookup and topic discovery today.