Core API Concepts (1.0.0)

Authentication

Every request is authenticated by a Bearer credential in the Authorization header. There are two types of credential, each suited to a different use case:

• API Keys — call the API as yourself (scripts, backend services). Create and revoke them in the dashboard or via the API; you can hold several and revoke any one independently.
• OAuth — for applications acting on behalf of other users (desktop or CLI tools), via OAuth 2.0 with PKCE.

Each credential carries one or more scopes that control what it can access. Today every credential is issued with full access; scoped, least-privilege credentials are planned.

Discovery

Identify and evaluate creators using structured, platform-specific search criteria. Responses are intentionally constrained to support ranking, filtering, and selection at scale rather than full profile hydration.

Enrichment

Retrieve complete creator-level data once a candidate has been identified. Enrichment responses provide the depth required for analysis, activation, and downstream data workflows.

Execution modes

Enrichment is available in both synchronous and asynchronous forms. Single enrichment supports real-time use cases, while batch enrichment is optimized for high-throughput, non-interactive processing.

Typical usage

Discovery and enrichment are designed as complementary stages. Discovery narrows the candidate set; enrichment supplies detailed data for creators that have already been qualified.