Dictionaries

Several search filters in Creator Search & Analytics take Fair's own identifiers rather than free text — locations, languages, brands, interests, and topics. The dictionary endpoints turn a search string into those identifiers, which you then pass into POST /discovery.

For example, to filter discovery by audience location you first look the location up:

curl "https://stg.api.fair-indonesia.com/api/fairservice/dictionary/locations?search_string=jakarta" \
  -H "Authorization: <your_token>"

{ "locations": [ { "id": "0244d71d-...", "name": "Jakarta", "type": "city" } ] }

…then pass the returned id into the audience_locations (or creator_locations) filter.

Available dictionaries

Dictionary	Endpoint	Feeds these filters
Locations	GET /dictionary/locations	audience_locations, creator_locations
Languages	GET /dictionary/languages	audience_language, creator_language
Brands	GET /dictionary/brands	audience_brand_affinities, creator_brand_affinities, brand_sponsors
Interests	GET /dictionary/interests	audience_interests, creator_interests
Topics	GET /dictionary/topics	topic_relevance
Topic relevance	GET /dictionary/topics/relevance	weight for a topic tag
User handles	GET /dictionary/userhandles	autocomplete a username as the user types

Each takes search_string, limit, and offset query parameters. Full request and response details are in the Creator Search & Analytics reference.

Dictionary data changes rarely. Cache the responses on your side (about 15 days is fine) instead of calling these on every search.

Related

• Creator Search & Analytics
• Guides → Find creators for a campaign