The Juicer API is a public REST API for social media aggregation. Use it to create feeds, add sources, pull post data, and query social posts directly from 15+ platforms—all over HTTPS with a single API key. It's self-serve and available on every plan, so you can start building in minutes.
🌿 Get started free at developers.juicer.io — create an API key in minutes. Upgrade to a paid plan for permanent keys and higher account limits.
What you can build with the Juicer API
The Juicer API is two products that share one API key:
Integration API — manage feeds, sources, posts, moderation, analytics, and webhooks programmatically, including configuring AI moderation (harmful-content filtering, sentiment, and custom rules). Anything you can do in the dashboard, you can script through the feed API.
Data API — query social media posts directly from 15+ platforms (Instagram, TikTok, YouTube, X, and more) without setting up a feed or source. Responses are cursor-paginated, so you can page through every matching post.
Full endpoint, object, and request/response details live in the API reference at developers.juicer.io.
Two ways to get an API key
You can get a key with or without a dashboard account:
From the dashboard (permanent key) — sign in at juicer.io, open the Developer page, and create a key. Permanent keys never expire, so they're best for production integrations. Creating one requires a paid plan.
By email, without the dashboard (temporary key) — send a
POSTto/v1/authorizewith just an email address. Temporary keys are free and available to anyone. New users get a key valid for 2 hours, extended to 12 hours once they confirm their email. Existing users get a link to approve the request in the browser.
Authenticating your requests
Every key is prefixed with jcr_ and is a secret, so treat it like a password. Pass it in the Authorization header on every request:
Authorization: Bearer YOUR_JCR_API_KEY
All endpoints live under the base URL https://api.juicer.io/v1.
⚠️ Keep your key private: never embed an API key in client-side code or a public repository. If a key is exposed, revoke it from the Developer page and create a new one.
Rate limits and plans
Unconfirmed keys allow 60 requests per hour.
Confirmed and permanent keys allow 300 requests per hour by default, with a short burst allowance.
Exceeding a limit returns
429 Too Many Requests.
These rate limits are the same on every plan. Paid plans add permanent keys for production, plus higher feed, source, and monthly-view limits and features like AI moderation that also apply through the API. You can upgrade from your Juicer dashboard.
Best practices
Cache responses where you can—feed and post listings rarely need second-by-second freshness.
Request only the data you need, and avoid polling endpoints in tight loops.
Page-view and click analytics only fire on Juicer's standard JS, WordPress, and iframe embeds. They don't run when you consume the API directly, so a custom front-end won't record views or clicks in your dashboard.
Already using the older Enterprise dashboard API? It remains available to existing Enterprise customers and is documented in Juicer's Enterprise plan. For new integrations, use the Juicer API above.
If a request returns an unexpected error or your key stops working, contact us with your key preview (the jcr_ prefix and last four characters), the endpoint you called, and the response status, and we'll take a look.