Skip to content
Last updated

API FAQ

This page answers common questions about API access, credits, pagination, enrichment, performance, and metric behavior.

Who is the API for?

The API is designed for developers integrating programmatically, as well as operations and commercial teams running creator sourcing and enrichment workflows.

Which plans include API access?

API access is available to Pro subscribers.

Trial accounts can test the API with 10 trial credits.

How do credits work?

Credits are deducted only when a request successfully returns data. No credits are deducted when a request returns no results.

Calculate Credits

What are the rate limits?

The API is limited to 300 requests per minute per account.

If you paginate large result sets, implement request throttling and backoff to stay within the limit.

What is the maximum value for limit?

  • Maximum limit: 50 results per page.

Each request returns one page only.

If you want 150 results with limit=50, you must make 3 requests:

  • page 1
  • page 2
  • page 3

How does pagination work?

Pagination is page-based:

  • page=1 returns the first page of results (up to limit results)
  • page=2 returns the second page of results (up to limit results), and so on

If you need results across multiple pages, you must request each page separately.

Example paging object:

"paging": {
  "limit": 50,
  "page": 3
}

The example above returns only page 3 (up to 50 results).

Does the Discovery API return emails?

No. Discovery returns creator profile data only.

To retrieve verified email addresses, use Enrich by Handle – Full after Discovery.

Typical workflow:

  1. Discovery → collect handles
  2. Enrich by Handle → retrieve detailed data (and email where available)

How are emails validated?

Enrich by Handle – Full returns only valid email addresses when available.
Emails are validated via a third-party verification provider before inclusion.

What is the difference between Enrich by Handle – Raw and Full?

Enrich by Handle – Raw

Returns unprocessed platform-specific data directly from the source, including basic profile information, post data, media counts, and platform-native metadata.

Enrich by Handle – Full

Returns complete profile data including cross-platform presence, engagement analytics, follower growth metrics, content performance data, monetization indicators, niche classification, hashtags, income estimates, and optional lookalike creator recommendations.

Does the API return profile images?

Yes. Profile picture URLs are included in responses where available.

Why are engagement metrics sometimes 0, null, or missing?

This most commonly happens when:

  • the creator hides likes/views/comments
  • the platform restricts metric visibility
  • the metric is unavailable for the requested timeframe or content type

When a platform does not expose a metric, it cannot be reliably returned, and the value may appear as 0 or null.

How does Batch Enrichment work?

Batch enrichment is designed for scale.

You can:

  1. Upload a CSV (up to 10,000 contacts)
  2. Start the batch job
  3. Download the enriched CSV output

Batch is recommended for large lists where you prefer asynchronous processing over making many individual requests.

For large sourcing workflows:

  1. Use Discovery with clear sorting and paging.
  2. Paginate programmatically until you reach your target volume.
  3. Use Enrich by Handle – Full for the subset you need contact and analytics data.
  4. Use Batch Enrichment for very large lists (up to 10,000 at a time).

Support

For any issues or questions please contact love@influencers.club.

Previous page
Next page