API FAQ

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

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

API access is available to Pro subscribers.

Trial accounts can test the API with 10 trial credits.

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

Yes. Every request that returns data deducts credits, regardless of whether the filters or parameters match a previous request. The API fetches fresh, up-to-date data on each call.

It is the client's responsibility to monitor request volume and credit usage. Use the dashboard or GET /public/v1/account/credits to track remaining credits.

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.

• 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

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).

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)

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

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.

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

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.

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

All profile pictures are stored on our infrastructure and returned at the highest resolution available. The URLs are signed and expire after 24 hours — this is a security measure and recommended industry practice. Download and store the images on your side within that window.

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.

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).

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