Agencies
Run many client accounts from one workspace, group accounts per client, and report on publishing status and per-platform metrics without switching between platform dashboards.
Use cases
Social publishing and analytics workflows for teams that need control and visibility.
Every workflow here runs on the same foundation: official account connections, one content preparation step, scheduling or immediate publishing, and status and analytics read-back per platform. Choose the workflow that matches how your team operates.
Social media scheduling API
Social Media Post Scheduling API for Multiple Platforms
Schedule social posts across TikTok, Instagram, Threads, Facebook, and YouTube from a backend job. One endpoint, server-side queues, and pollable status.
Scheduling through an API removes the nightly manual posting routine. Your backend submits the week of content once with a future timestamp, the queue holds each post until its time, and the team checks status instead of watching a clock. This page shows the scheduling request, the fields it accepts, what the queue does with it, and how to follow a post through to publication.
Multi-platform posting
Post to Multiple Social Platforms at Once with One API
Post once and publish to TikTok, Instagram, Threads, Facebook, and YouTube. Prepare content per platform and track each post from queue to published.
Multi-platform posting removes the copy-and-paste routine: prepare content once, select the accounts, and let the scheduled posts endpoint fan the request out to each platform. The work that remains is making sure the content fits the platform it targets. This page covers the endpoint fan-out, the per-platform media rules, how scheduling validates a batch, and how to track every post that came out of one request.
Content publishing API
Content Publishing API for Social Media Apps
Add social publishing to your product with one API for content, scheduling, account listing, status tracking, and per-platform analytics.
A content publishing API is the piece that lets your product post to social platforms without maintaining five integrations. Wahdx Connection handles account connections, media validation, scheduling, and status, and returns per-platform analytics, while your backend keeps the API key and your own product logic. This page covers the endpoints, a request to start from, and the behaviors worth planning around.
Post status tracking API
Post Status Tracking API: Queued, Published, Failed
Track social posts from queued to published. Check a single post or a batch, catch failures, and keep publishing success visible per platform.
Publishing does not end when the request returns 200. A post can still be queued, processing, published, or failed, and a workflow that ignores those states finds out too late that a campaign did not go out. Wahdx Connection exposes single and batch status endpoints so integrations can close the loop. This page covers the states, the two check patterns, and how to design retries around them.
Publishing analytics API
Publishing Analytics API: Success Rates per Platform
Measure publishing volume, provider acceptance, publication, and failure per platform with aggregate publishing analytics.
Audience analytics answer how a post performed. Publishing analytics answer a different question: how much content actually went out, and how much failed. Wahdx Connection computes those numbers server-side from the publishing ledger, so the response stays small as volume grows. This page covers the endpoint, the difference between requests and attempts, and the fields worth alerting on.
Social media analytics API
Social Media Analytics API: Metrics per Platform
Read followers, reach, engagement, views, and top content per platform for TikTok, Instagram, Threads, Facebook, and YouTube from one API.
Platforms measure different things, so an analytics API is only useful if it keeps those numbers separate. Wahdx Connection returns per-platform metrics tied to the connected accounts, with null where a platform exposes nothing, rather than a single blended figure. This page covers what each platform returns, how to scope a report, and how to combine audience metrics with publishing volume.
End to end
How any of these workflows runs from start to finish.
- 01STEP
Connect official accounts
Authorize TikTok, Instagram, Threads, Facebook, and YouTube accounts through each platform’s own login and permission flow. The scopes you approve stay visible per platform.
- 02STEP
Prepare content per platform
Write captions, attach media, pick the accounts, and apply platform-specific settings. Text-only posts work on Threads and Facebook; TikTok and Instagram require media.
- 03STEP
Schedule or publish
Send content now or queue it up to 30 days ahead. The server processes the queue, so publishing continues without someone keeping a browser open.
- 04STEP
Track status and measure
Use single or batch status checks to see queued, processing, published, or failed posts, then review per-platform analytics such as reach, engagement, and top content.
Who this is for
These workflows exist for three kinds of operators.
Brands and content teams
Keep a recurring content calendar across five platforms with status visibility, so a missed post or a rejected video is spotted before it becomes a client or campaign issue.
Developers
Call the API from a backend for publishing, scheduling, account listing, status checks, and analytics without exposing API keys in browser code.
Questions, answered
Straight answers on how these workflows fit your operation.
Do these workflows need the API or the dashboard?
Both are available. The dashboard covers day-to-day publishing, scheduling, and analytics review. The API supports server-side integration when your product or internal tooling needs to trigger the same operations.
Which platforms do the use cases cover?
TikTok, Instagram, Threads, Facebook, and YouTube. Text-only posts are supported on Threads and Facebook; TikTok and Instagram require media.
How far ahead can I schedule posts?
Up to 30 days ahead. Scheduled content is queued and processed server-side, so the workflow keeps running without a browser session.
Can I schedule posts and still track analytics?
Yes. Scheduling, status tracking, and analytics live in the same workflow and are tied to the connected accounts used for publishing.
Do I need a developer to use these workflows?
No for the dashboard. Direct API use requires a server-side integration, with API keys kept out of browser code.
Related reading
Platform guides and workflow walkthroughs.
How toHow to Post to Five Social Platforms at Once with One APIPublish to TikTok, Instagram, Threads, Facebook, and YouTube from one endpoint: media rules per platform, scheduling, status tracking, and text-only caveats.How ton8n Social Media Automation: A Publishing Workflow You Can ImportBuild an n8n social media automation that publishes and schedules through the Wahdx Connection API. Workflow JSON, HTTP setup, and error handling.AnalyticsSocial Media Analytics API: Which Metrics Matter per PlatformPer-platform social analytics: followers, reach, engagement, impressions, and views. What each platform returns, and how publishing analytics track volume.Platform guidesThreads API Guide: Text Threads, Scopes, and MetricsPublish text posts and thread sequences on Threads through an API: scopes, character limits, reply settings, rate limits, metrics, and scheduling.