For SaaS · embed social publishing

Embed social media publishing in your SaaS

Embed social publishing in your SaaS so your users can post to Instagram, TikTok, YouTube, LinkedIn, X, Threads, Bluesky, Facebook and Telegram without leaving your product. There is no PostPulse UI in your app — provisioning, scheduling and publishing all run through the API, under your brand. Ship the feature in days with one REST API — not a multi-month platform-integration project.

No PostPulse UI — all API, in your product No Meta / TikTok / Google review on your side Idle connected accounts are free
Partner Portal dashboard: social publishing across 9 platforms, managed for your users through one API under your brand
Build vs. buy, for a feature you don't sell

"Let users post from our app" is a multi-month project

Social publishing is rarely your core product — but users keep asking for it, and competitors keep shipping it. Building it natively means owning nine platform integrations, multiple app-review processes, and an OAuth/token system for every user, indefinitely. That is a team's worth of work spent on a feature that isn't your differentiator.

Branded as you

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.

Build in-house · the actual cost

What it costs to build social publishing into your product

Every line item is undifferentiated platform work — effort that does not move your core product forward.

01

9 platform integrations to own

Instagram, TikTok, YouTube, LinkedIn, X, Threads, Bluesky, Facebook and Telegram are nine separate APIs with nine auth models and nine media pipelines. "Social posting" is not one integration — it is nine, plus their interactions.

One REST API covers all 9 platforms behind a single request shape.
02

App reviews you can't schedule around

Publishing on behalf of your users requires Meta App Review, TikTok Content Posting access and a Google/YouTube audit — gates measured in weeks to months and outside your sprint planning entirely.

PostPulse owns the verified apps, so your feature ships on your timeline, not a reviewer's.
03

Per-user OAuth & token management

Every user who connects an account adds OAuth flows, token refresh, rotation and re-consent handling — per platform. This scales with your user base and never stops needing maintenance.

OAuth and the full token lifecycle are handled server-side for every one of your users.
04

Scheduling, retries & status

Users expect "schedule for later" and clear success/failure feedback. That means a durable queue, idempotent retries, and status surfaced into your UI — infrastructure you build and operate yourself.

Scheduling is built in, and 14 webhook events let you reflect post status natively in your UI.
05

A connect step that fits your UX

A clunky or off-brand "connect your account" step hurts activation. Building a polished connect step that lives inside your own UI — with no vendor dashboard anywhere else — is real product work on top of the API plumbing.

The connect entry point is branded as you and lives in your app; there is no PostPulse UI in your product. Only the platform's own permission screen names the app, exactly like every social API.
06

Maintenance that competes with your roadmap

Once shipped, you own it: every platform deprecation, scope change and policy update becomes unplanned work that pulls engineers off your actual product.

We track and absorb API changes so your roadmap isn't hostage to platform churn.
How PostPulse works inside your SaaS

Add publishing as a feature, not a department

PostPulse Connect lets your SaaS offer social publishing as a native feature. Authenticate once as a partner, then represent each of your users with their own identity header. There is no PostPulse UI in your app — your users connect their own accounts from a step inside your product, and you publish on their behalf through one REST API, the same one documented for every other PostPulse integration.

Native to your product

Users connect and publish without leaving your app — there is no PostPulse logo or dashboard anywhere in your product. The one PostPulse touchpoint is the standard account-connection step, where the platform's own permission screen names the app, just as it does for any social API.

Scales per user automatically

One partner credential plus a per-user identity header means onboarding the ten-thousandth user is the same call as the first. No per-user setup, no per-user app.

Webhooks into your UI

Fourteen webhook events cover the post lifecycle, so you can show users real publish status, retries and failures inside your own interface instead of polling platforms.

Partner Portal: your users' connected social accounts across all 9 platforms, managed through the API
Your users' connected accounts, managed through the Connect API — no PostPulse UI in your product.
Four calls to live

Connect a user and publish from your app

One machine-to-machine token covers every user in your product. Provision a user, drop a branded Connect step into onboarding, 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"] }]
    }]
  }'
DIY vs PostPulse

A multi-month project, or a feature you ship this week

Both reach the same feature. Only one spends a team's quarter on integrations that aren't your differentiator.

DIY · build it into your app
  1. Register and audit developer apps across 9 platforms
  2. Pass Meta, TikTok and Google reviews before you can ship
  3. Build per-user OAuth, token refresh and rotation for every platform
  4. Build a branded connect flow that fits your product's UX
  5. Build scheduling, retries and status surfaced into your UI
  6. Own platform-API maintenance indefinitely, off your roadmap
PostPulse inside your SaaS
  1. Day 0 · Get partner credentials and a sandbox
  2. Day 1 · Drop a branded Connect step into your onboarding
  3. Day 1 · Your user authorises their accounts — no audit on your side
  4. Day 2 · POST /v1/posts publishes from your app to any of 9 platforms
  5. Day 2+ · Ship your actual roadmap, not platform plumbing
Security & multi-tenancy

Multi-tenant by design, secrets off the client

Your SaaS stays multi-tenant: one partner credential, but every user is an isolated identity with their own tokens — nothing leaks across accounts.

Per-user token isolation

Each user's OAuth tokens are stored against their own PostPulse identity and used only on calls carrying that user's id header — so one tenant in your product can never act on another's connected accounts.

Secrets stay server-side

Your client secret authenticates your backend only and never ships in your web or mobile client. 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 your app sends. White-label users are excluded from PostPulse emails and notifications, so the experience stays entirely yours.

Tenant isolation by default

A user id header scopes every read and write, and provisioning is idempotent on (your client id, your external user id) — so syncing the same user twice never collides with another tenant.

Partner Portal: each of your users is an isolated tenant with their own connected accounts and tokens
Every one of your users is a separate, isolated tenant — provisioned and managed through the API, never a PostPulse login.

Why product teams embed PostPulse

Reviewed on Product Hunt
James Mccarthy
James Mccarthy

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

Antonio Widera
Antonio Widera

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

Shawn Padilla
Shawn Padilla

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.

Karen Rivers
Karen Rivers

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.

Douglas Finch
Douglas Finch

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.

Andrea Scott
Andrea Scott

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.

William Dirks
William Dirks

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.

solo serg
solo serg

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.

Publishing to 9 platforms, in production today · see live stats →
Build vs. buy

A team's quarter, or a line item

For a feature that isn't your core product, the comparison is roadmap time spent on plumbing versus a flat monthly fee.

Engineer-months off your roadmap

Nine OAuth flows, three to four platform audits (weeks to months each), media pipelines and a scheduler are multiple engineer-months — spent on a feature that does not differentiate your product.

Maintenance competes forever

After launch, every platform deprecation and scope change is unplanned work that pulls engineers off your roadmap. The ongoing cost is the maintenance, not the first ship.

Buy: $200/mo, ship in days

PostPulse Connect is $200/month plus $1 per active account, idle accounts free. You add the feature in days and keep your engineers on what actually makes your SaaS different.

What PostPulse handles vs. building it into your app

Which of this is your product, and which is undifferentiated platform work.

CapabilityPostPulse white-labelBuild in-house
Onboarding your 10,000th user✓ The same API call as your first — no per-user setupPer-user OAuth and token state for every platform
Time to ship the feature✓ Days — your feature ships on your sprintA multi-month project gated on platform reviews
Post status inside your UI✓ 14 webhook events you reflect nativelyBuild a queue and poll each platform yourself
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 userBuild and maintain per platform, forever
Platforms covered✓ 9, one request shape9 separate APIs to integrate
Post status & delivery✓ 14 webhook events across the post lifecycleBuild a queue and poll each platform yourself
Partner Portal: 14 webhook events delivering post status, retries and failures back to your product
Fourteen webhook events deliver post status, retries and failures straight to your product — reflect them in your own UI, no polling.
Pricing

Usage-based pricing that fits a product

A flat platform fee plus a small fee per active account — your cost grows with publishing usage, not with every user who merely connects an account.

White-Label · one pricing model
$200/ mo+$1per active account
Talk to the founder

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.

Worked example
  • 1,000 connected accountsconnect freely
  • 300 active this month300 × $1 = $300
  • $200 + $300$500/mo
Startup support. Still pre-launch or in beta? We waive fees until you launch — discussed individually, so you can build the integration risk-free.
Want the full integration spec first? Read the white-label developer guide →

Frequently asked questions

9 platforms in your product, none to maintain

Your users connect any of these from one connect step inside your app — and you maintain none of them.

Add social publishing to your product in days

Talk to the founder about embedding white-label publishing, or open the app and try the API first. No platform audits, tokens handled, idle accounts free.