Creator data for HTTP workflows.

Connect your data key

Create a data key in the API console with prepaid credits or an active API subscription. Use a GET request with a Bearer data key stored in your automation credential store. This example makes one search request and returns up to 20 matches. Disable automatic retries and pagination until you have configured a job budget.

curl --fail-with-body --max-time 30 --get \
  "https://api.ugcroster.com/v1/creators/search" \
  --header "Authorization: Bearer $ROSTER_API_KEY" \
  --data-urlencode "q=fitness" \
  --data-urlencode "country=US" \
  --data-urlencode "page=1" \
  --data-urlencode "limit=20"

Check the connection

Validate your key first with GET /v1/usage. Then run the single search and inspect the response. Use creator pk values from that response for optional profile reads; usernames are not profile IDs.

Make your first search

For the REST equivalent, add follower_min=10000 and follower_max=100000 to the GET request above. Keep page=1 and limit=20, with no retry or pagination loop. Or download the n8n template, import it and configure Header Auth before a manual run. The prompt below expresses the same budget for an MCP agent.

Find up to 20 US fitness creators with 10,000–100,000 followers. Use one search_creators call, page 1, limit 20. Budget: 10 credits, no profile reads, no retries or extra pages. Return a shortlist with available fields and state any missing data. Stop after the search, even if fewer than 20 creators match.

One search page costs 10 credits, whether it returns 1 or 20 matches. Each optional profile read costs 1 credit. Checking usage costs no credits. The prompt is an agent instruction, not a server-enforced spending cap; your application must enforce a job budget for unattended runs.

Work with the data you have

Results come from stored directory records. Location describes the creator, not their audience. An email on file is not a deliverability guarantee, and reading a profile does not trigger a live scrape. Reuse fields already returned by search before spending credits on extra profile reads.

Use a data key for these examples. It cannot send messages, create campaigns or record payouts. Do not enable brand actions for a discovery-only workflow.