It is the easiest possible setup and the easiest to leak: a URL ends up in a screenshot, a support ticket, a config file in a shared repo. Their own REST API uses a proper Authorization header for the same key, which shows the choice here was for client convenience rather than necessity. All fourteen tools being read-only limits the damage if it does escape — nobody can change anything with it.
InfluData's endpoint for creator discovery. Fourteen tools, all read-only, grouped by job across discovery and profiles, content and analytics, and campaigns.
- search_creators — the creator database filtered by platform, country, follower count, engagement and category
- get_campaign_metrics — reach, views and engagement per creator
- And the remaining twelve across profiles, content analysis and campaign reporting
Your API key as the last path segment of the URL. No header, no OAuth — their documentation says to select no auth type in the client. The same key is used with a normal Authorization header on their REST API.
Paste a URL with a key — add the endpoint to your client