The white-label social media API
Offer social publishing to Instagram, TikTok, YouTube, LinkedIn, X, Threads, Bluesky, Facebook and Telegram inside your own product. There is no PostPulse UI anywhere in your app — provisioning, scheduling and publishing all run through the API, under your brand. One REST API, no platform audits, and OAuth tokens we maintain forever.

Adding social publishing looks small until you scope it
Nine platforms, each with its own OAuth quirks, its own app-review gate, its own media rules, and its own breaking changes. Owning that is a standing engineering team — not a sprint. A white-label social media API lets you ship the feature without ever becoming a social-platform integrator.
See it branded as you — 60-sec demo
Watch a reseller app run the full Connect flow end to end: a user connects their own social account from a step inside the app, then publishes — with no PostPulse UI in the product, just the API underneath. The only PostPulse touchpoint is the platform's own permission screen, exactly like every social API.
What you sign up for if you build it in-house
Every item below is real, recurring work the native platform APIs hand you — multiplied across 9 networks and every user you onboard.
9 separate platform integrations
Instagram, TikTok, YouTube, LinkedIn, X, Threads, Bluesky, Facebook and Telegram each ship a different API, auth model, media pipeline and set of edge cases. There is no "social media" API — there are nine.
App audits & review, per platform
Meta App Review, TikTok Content Posting access, the YouTube/Google audit — publishing on behalf of other users is gated behind reviews that take weeks to months and get rejected for reasons that are rarely clear.
OAuth & token lifecycle, forever
PKCE, state, scope drift, refresh, rotation, revocation, re-consent prompts — per platform, per user. The first integration is a sprint; keeping all of them alive is a permanent on-call burden.
Scheduling, retries & webhooks
A publish queue, a scheduler, idempotent retries, and status you can surface back to users. Without callbacks you end up polling every platform to find out whether a post actually landed.
A connect step that fits your product
A clunky, off-brand account-connection step hurts activation. Building a polished connect bridge that lives inside your own UI — and keeps every other surface yours — is its own non-trivial project.
Ongoing API churn
Platforms deprecate endpoints, change scopes, and tighten policy on their schedule, not yours. Every change is unplanned maintenance that competes with your actual roadmap.
Your brand on top, our infrastructure underneath
PostPulse Connect is the white-label tier of our social media API. You authenticate once as a partner with a single machine-to-machine credential, then act on behalf of each of your users with a lightweight identity header. There is no PostPulse UI in your product — the only PostPulse touchpoint is the standard account-connection step, where the platform's own permission screen names the app requesting access, just like every social API.
Users connect their own accounts
Each of your users authorises their own Instagram, TikTok, YouTube and the rest from a connect step inside your product. Tokens are stored against that user server-side. No credentials ever touch your code.
No PostPulse UI in your product
There is no PostPulse logo or dashboard anywhere in your app — provisioning, scheduling and publishing all happen through the API, under your brand. White-label users are isolated from PostPulse subscriptions, emails and notifications. The one PostPulse touchpoint is the standard connection step, where the platform's own permission screen names the app and the OAuth redirect passes briefly through post-pulse.com.
One API surface to learn
Provision a user, generate a Connect URL, then call /posts, /media and /accounts exactly like the standard API — just with partner auth headers. Same endpoints, same docs.

Connect a user and publish on their behalf
One machine-to-machine token covers all your users. Provision a user, generate a branded Connect URL, then publish to any of the 9 platforms with the same request.
# 1. One machine-to-machine token covers ALL of your users
curl -X POST https://auth.post-pulse.com/oauth/token \
-H "Content-Type: application/json" \
-d '{
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET",
"grant_type": "client_credentials",
"audience": "https://api.post-pulse.com"
}'
# 2. Provision the end-user once. Idempotent on (client, externalUserId) —
# safe to re-send. Persist the returned uuid. (No user-id header yet: the
# user doesn't exist until this call returns.)
curl -X POST https://api.post-pulse.com/v1/connect/users \
-H "Authorization: Bearer <m2m_token>" \
-H "x-api-key: YOUR_CLIENT_ID" \
-H "Content-Type: application/json" \
-d '{
"externalUserId": "your_user_42",
"name": "Jane Doe",
"email": "[email protected]"
}'
# → { "uuid": "..." }
# 3. Generate a Connect URL for that user — branded as you.
# They authorise their own Instagram/TikTok/… on the standard connect step.
curl -X POST https://api.post-pulse.com/v1/connect/authorize-url \
-H "Authorization: Bearer <m2m_token>" \
-H "x-api-key: YOUR_CLIENT_ID" \
-H "X-Connect-External-User-Id: your_user_42" \
-H "Content-Type: application/json" \
-d '{ "platform": "INSTAGRAM", "redirectUri": "https://yourapp.com/connected" }'
# 4. Publish on that user's behalf — same API, 9 platforms, one request.
curl -X POST https://api.post-pulse.com/v1/posts \
-H "Authorization: Bearer <m2m_token>" \
-H "x-api-key: YOUR_CLIENT_ID" \
-H "X-Connect-External-User-Id: your_user_42" \
-H "Content-Type: application/json" \
-d '{
"scheduledTime": "2026-06-10T15:00:00Z",
"publications": [{
"socialMediaAccountId": 123,
"platformSettings": { "type": "INSTAGRAM", "publicationType": "REEL" },
"posts": [{ "content": "Shipped from your product 🚀", "attachmentPaths": ["uuid/reel.mp4"] }]
}]
}'The same capability, two timelines
Both assume a capable team. Only one spends its time on undifferentiated platform plumbing.
- Register a developer app on all 9 platforms and configure OAuth redirects
- Pass Meta App Review, TikTok and YouTube audits — weeks to months each
- Implement OAuth + token refresh and rotation, per platform, per user
- Build a connect step that lives inside your own UI, not a vendor dashboard
- Build scheduling, retries, status webhooks and failure alerting
- Keep all 9 integrations alive through platform API changes — forever
- Day 0 · Get partner credentials and a sandbox
- Day 1 · Provision a user and generate a branded Connect URL
- Day 1 · Your user authorises their account — no audit on your side
- Day 2 · POST /v1/posts publishes on their behalf to any of 9 platforms
- Day 2+ · Build your product, not platform plumbing
Isolated per user, secrets that never ship to the client
White-label is multi-tenant by design: one partner credential, but every one of your users is a separate, isolated identity with their own tokens.
Per-user token isolation
Each user's OAuth tokens are stored against their own PostPulse identity and only ever used for calls carrying that user's id header. One user can never act on another's connected accounts.
Secrets stay server-side
Your client secret authenticates your backend only — it is never embedded in a browser or mobile binary. The signed Connect state is HMAC-sealed, so a redirect URI can't be tampered with mid-flow.
GDPR & data processing
PostPulse acts as a processor for the social tokens and post content you send. White-label users are excluded from PostPulse marketing and notifications, so there is no shadow relationship with your users.
Tenant isolation by default
A user id header scopes every read and write. Provisioning is idempotent on (your client id, your external user id), so re-syncing a user can never collide with another partner's tenant.

Why teams ship social publishing on PostPulse
Reviewed on Product HuntI use PostPulse with an AI agent via their MCP server. My agent literally posts to social media on its own now. Didn’t expect that to work as smoothly as it did.
$5/month for what would otherwise require a full backend engineer to maintain? Easy yes. The REST API is clean and well-documented too, which is rare.
Tried to get TikTok API access myself. Three weeks, two rejections. Switched to PostPulse and was posting to TikTok the same day. Wish I hadn’t wasted that time.
I’m a Make.com power user and needed to post to 5 platforms from one scenario. The native PostPulse app for Make connected everything in one afternoon. Would’ve taken me weeks to do manually.
I built an n8n automation for a client and needed to add social publishing. The official PostPulse n8n node was literally drag and drop. No headache.
Saved me months of dev work. I was about to start integrating Instagram and TikTok APIs separately — then I found out Meta’s app review alone can take months. PostPulse just handled all of that. Shipped social posting in under a week.
The most flexible pricing model on the market!
I'm building an AI content factory as a side hustle. I'm still in the experimentation phase, so I don't have the budget for expensive tools — but I also needed to get everything up and running quickly, so I integrated with a ready-to-go API instead. PostPulse offers a flexible pay-as-you-go model that let me experiment first without commitment — and now that we have stable traffic, I’ve switched to their $5/month subscription.
Best support on the market — the founder personally emailed me when I hit a client error and walked me through the fix.
We optimized the posting to 20 twitter accounts. It was a problem to manage such a number, but through the platform everything works out perfectly. Very convenient dashboard for tracking errors. Great product.
What nine integrations actually cost to own
The honest comparison is not "an API call vs. a few weeks." It is a standing platform-integration capability vs. a flat monthly fee.
Engineer-months to first post
Nine OAuth flows, three to four platform audits (weeks to months each), media pipelines and a scheduler add up to multiple engineer-months before a single user can publish — and reviews can reject and reset the clock.
Maintenance never reaches zero
Once shipped, platform deprecations, scope changes and token-policy updates are permanent on-call load. The cost of social publishing is the maintenance, not the first integration.
Buy: $200/mo, live in days
PostPulse Connect is $200/month plus $1 per active account, and idle accounts are free. You skip every audit, integrate once, and redirect those engineer-months back to your actual product.
What PostPulse handles vs. building it yourself
The line between your product and undifferentiated social plumbing.
| Capability | PostPulse white-label | Build in-house |
|---|---|---|
| Going live with one new platform | ✓ A config flag — the verified app already exists | A fresh integration plus its own app review |
| PostPulse UI in your product | ✓ None — provisioning & publishing are all API, under your brand | Build every connect/manage surface yourself |
| Who owns platform API churn | ✓ We absorb deprecations and scope changes | Every change is unplanned work on your roadmap |
| Platform audits / app review | ✓ Not required — we own the verified apps | ✗ Meta / TikTok / Google review, per platform |
| OAuth, token refresh & rotation | ✓ Handled server-side, per user | Build and maintain per platform, forever |
| Platforms covered | ✓ 9, one request shape | 9 separate APIs to integrate |
| Post status & delivery | ✓ 14 webhook events across the post lifecycle | Build a queue and poll each platform yourself |

White-label pricing built for products
A flat platform fee plus a small per-active-account fee — so your cost tracks usage, not seats. Connected-but-idle accounts cost nothing.
How it works
An active account is one that publishes at least one post that month. Connected-but-idle accounts are not billed — connect as many as you like and pay only for the ones that actually post. Your cost tracks usage, not seats or profiles.
- 1,000 connected accountsconnect freely
- 300 active this month300 × $1 = $300
- $200 + $300$500/mo
Frequently asked questions
Ship social publishing under your own brand
Talk to the founder about white-label access, or open the app and try the API first. No platform audits, no token plumbing, idle accounts free.