How the API signals problems, what each call costs, and the limits that keep it fast and fair.
Error envelope
Every error returns a JSON body with a machine-readable code and a human-readable message:
{ "error": { "code": "out_of_credits", "message": "Out of credits. Upgrade or top up to continue." } }
| Status | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | out_of_credits | You are out of credits. Upgrade or top up. |
403 | forbidden | Your plan has no API access. |
404 | not_found | No creator or sponsor matches the id. |
422 | invalid_request | A required parameter is missing or invalid. |
429 | rate_limited | Too many requests. Slow down and retry. |
Credit costs
| Endpoint | Cost |
|---|---|
GET /creators (search) | 1 credit per page |
GET /creators/{id} | 1 credit |
GET /creators/{id}/audience | 1 credit |
GET /sponsors (search) | 1 credit |
GET /sponsors/{id} | 1 credit |
GET /niches | Free |
GET /credits | Free |
Credits are shared with MCP usage and reset each period. See Authentication.
Rate limits
Requests are capped per API key per minute; exceeding the cap returns 429. There is also a coarse
per-IP limit at the edge. In batch jobs, add a small delay between requests and back off on 429.
Pagination and result caps
Creator search returns up to 25 results per page (fewer on the free trial). Use page with the
nextPage value from each response to move through results:
curl -H "Authorization: Bearer ifsk_your_key" \
"https://platform.influesque.com/api/v1/creators?query=gaming&page=2"
The API is designed for targeted queries, not bulk export. Results are paginated and capped per page, and there is no list-all endpoint. Fetch what you need for a query, then refine.