Developer API
Creator intelligence inside your agency’s own tools
Client portals, internal dashboards, pitch generators — feed them all from the same API that powers Zaver’s discovery and insights.
- Discovery, analytics, insights and enrichment endpoints
- Org-scoped keys with granular permissions per integration
- Credit-metered per call — costs track usage, not seats
What agencies build with it
Common patterns from agency engineering teams:
- Client-facing portals showing live insights data under your brand
- Pitch automation: brief in, ranked and vetted shortlist out
- Internal CRM enrichment: every creator record annotated with Zaver insights
- Reporting pipelines that pull fresh stats on scheduled runs
Natural-language discovery, programmatically
The discovery endpoint accepts the same plain-English queries as the platform:
curl -X POST https://api.zaver.one/discover \
-H "Authorization: Bearer $ZAVER_API_KEY" \
-d '{
"query": "clean-beauty creators in LA, 50k-200k followers",
"limit": 25
}'Operationally boring, by design
Idempotency-keyed billing, async job polling for long-running analyses, and self-serve key management in Settings → Developer. Your finance team sees one metered bill per workspace.
Frequently asked questions
Which endpoints exist?
Nine: discover, insights, profile-insights, analyzer, engagement, followers, username resolution, track, and email outreach — plus async job polling.
How is the API priced?
Per call, from your workspace’s credit pool, with idempotency keys so retries never double-bill.
Can we white-label the data?
You control presentation entirely — the API returns structured JSON for your own UI.
Where are the docs?
Self-serve documentation with cURL examples lives in the platform under Settings → Developer.