Describe the content you need
Search matches details in creators’ content and bios, as well as their presentation style. Include the topic and format that matter to your campaign:
Review the returned reasons and evidence to see which content supports each match. Add concrete requirements as you refine the query; broad phrases such as
good creator provide little direction.
Hard Filters
On top of the semantic matching, hard filters constrain results to creators who meet specific numeric or boolean requirements:- follower ranges
- engagement rate floors
- verification status
- platform
Geography
When your query names a country (for exampleUK skincare creators or American fitness influencers), geography is treated as a hard requirement, not a preference. A creator whose verified location contradicts the requested country is excluded from results. A creator whose location can’t be verified is still returned, but flagged with location_unverified: true so you can tell an assumed match from a confirmed one. When your query names no country, location_unverified is null on every result.
What You Get Back
Each result includes:creator: the creator’s identity and detailsrelevant_profile: the profile most relevant to the search query, ornullwhen no profile data is availableprimary_profile: the creator’s largest profile, ornullwhen no profile data is availablematch.score: a 0-1 relevance scorematch.confidence: the same 0-1 relevance value asmatch.scorematch.low_confidence: identifies lower-confidence results for additional reviewmatch.reasons: short plain-text explanations for why the creator matchedmatch.evidence: the same reasons in structured form, each with aprovenancelabel and, where the reason rests on a post, asource_post_idand a verbatimevidence_quote— see Match Reasonslocation_unverified:truewhen the creator’s location could not be verified against the requested country;nullwhen your query named no country
Search quality
Inspectquality.mode on the response and match.ranking_source on each result before displaying scores.
For example, a result with
match.ranking_source: "retrieval_fallback" and match.score: 0.9 is a highly ranked retrieval candidate, not a 90% campaign-fit assessment. Review its evidence or use campaign match scoring before making a fit decision.
quality.reason explains why fallback was used. Preserve this information when saving or displaying results. For older responses that omit quality and ranking_source, the contract defines the result as reranked.
Scores are ranking signals rather than guarantees. Compare them alongside reasons and evidence; avoid applying one threshold across reranked and fallback results.
Combine Search with Filters
Use semantic search for discovery, then hard filters for boundaries.- match the semantic intent of
sustainable fashion creators - are on Instagram
- fall within the follower range you care about
- clear your engagement floor
- have a verified account
Available Filters
Platforms
Creator search uses Instagram. Setplatforms to ["instagram"] or omit it to use the default:
Limit
limit sets the maximum number of results the can return. Range: 1-100, default: 25. This determines the billing cap for the session — start small (5-10) while prototyping and increase once you understand how your UI consumes results.
Search Pagination
The POST returns your search results together. Use GET to reopen those results in smaller pages.POST /v1/search creates a search session. You set a limit that caps the total number of results the session can ever return. You’re billed once based on the number of results delivered, up to that limit.
GET /v1/search/{id} paginates through the results using cursors. These requests are free — they read the existing session results.
For example, a session created with limit: 25 contains up to 25 results. Use GET to read that set in batches, or create a new search to discover more creators.
For cursor mechanics and page size options, see the Pagination guide.
Search Feedback
Submit feedback for a search with the same account that created it. Feedback does not consume search credits.helpful or not_helpful for rating. The reason and details are optional. Include the specific mismatch when reporting poor results, and avoid putting personal or confidential information in the details.
Refine searches in your application
Keep the original brief visible beside the results. If the reasons miss a requirement, refine that part of the brief before running another search. If you transform user input into a search query, compare the results with the original wording and preserve the requirements the user supplied.See the API Reference for request fields, response schemas, and SDK examples.