Skip to main content

RAW API best practices and onboarding

Written by Georg Kiil

With the RAW API, you can fetch the latest creator and content data on demand - powering fast enrichment, performance analysis, and smarter activation at scale.

Key use cases

  • Monitor live campaign performance: Track results as they happen to enforce creator compliance, protect brand safety, and optimize ROAS.

  • Score and rank creators: Use granular raw signals to identify the best-fit creators for a specific campaign objective.

  • Refresh Data on demand: Update key metrics when it matters (e.g., final check before activating creator for a campaign)

  • Build custom analytics outputs: Create your own benchmarks, alerts, and derived metrics tailored to how your team measures success.

Per-request limits

RAW API endpoints differ by response type:

Single-item endpoints: Return details for one object per request, like detailed information for a specific Instagram reel.

Fixed-list endpoints: Return up to N items per request, like a creator’s Instagram feed. You can paginate to pull more items (With an additional request use per page).

Rate limit handling

When you hit rate limits, implement exponential backoff:

  1. Catch the 429 (Too Many Requests) response.

  2. Wait 1 second before retrying.

  3. If the retry also fails, double the wait time (2s, 4s, 8s...).

  4. Set a maximum number of retries (for example, 5 attempts) to avoid infinite loops.

Pagination

For endpoints that return lists (like content history), use pagination tokens:

  • Check the response for a next token.

  • Include the token in your next request to get the following page.

  • Continue until no next token is returned.

  • Don't assume a fixed number of pages. Always check for the token.

💡 The RAW API fetches data directly from social platforms at the time of your request, so you're always getting the latest available information. Cache results locally when real-time freshness isn't critical to save your request quota.

Combining with Discovery API

The most powerful integrations use both APIs together:

  1. Discovery API to search and filter creators matching your criteria.

  2. RAW API to get detailed profile data and content data for the creators you want to evaluate.

This workflow lets you efficiently find and vet creators at scale without wasting API credits on profiles that don't match your needs. It's the same approach that powers Modash's own Discover tool.

FAQs

  • What platforms does the RAW API support?

    Instagram, TikTok, and YouTube. Each platform has slightly different data available.

  • How fresh is the data I get from the RAW API?

    The RAW API fetches live data directly from social platforms at the time of your request, so you're always getting the latest available information.

  • Does fetching a profile use a credit?

    It depends on the endpoint and whether the profile is already unlocked. Check the API documentation for credit usage per endpoint.

  • Can I get data for private accounts?

    No. The RAW API can only access publicly available profile data.

  • What happens if I request a profile that isn't in the database?

    You'll receive a 404 response. You can request that the profile be added, and it typically takes about 48 hours for new profiles to become available.

  • Is there a bulk endpoint for multiple profiles?

    Check the API documentation for batch endpoints. Some data can be requested in bulk to reduce the number of individual API calls.

  • Why is the video_url field missing from some Instagram carousel items?

    The video_url field in carousel_media is optional and won't always be present, even for carousel items that contain videos. Your integration should handle this field gracefully when it's absent.

Did this answer your question?