Guide
Social media API: one API to post to six platforms
A social media API that posts everywhere is really six different APIs; the alternative is to call one scheduler’s API that has already done the connecting. This guide covers social media API integration, what it costs and when going direct is right.
What going direct looks like
Each platform has its own flow. Instagram publishes in two steps, a media container and then media_publish. LinkedIn wants a Linkedin-Version header and an author URN, and returns the post ID in a response header.
Each also has its own permissions. Instagram’s page names instagram_content_publish. LinkedIn’s names w_member_social and w_organization_social.
The cost that adds up
Using a platform’s own API usually means registering your own developer app and getting its permissions approved, and then keeping every one of those integrations working as the platforms change.
Social media API integration: one API instead
Dripost has a REST API, documented as OpenAPI at dripost.com/docs/api. You connect your accounts once, then one call can send a post to YouTube, Instagram (professional accounts), Facebook Pages, LinkedIn (personal profile), Threads and X (text only).
A refusal comes back with the platform’s own reason, and the live post’s link comes back when it works.
Keys and plans
API keys start with dp_, are shown once and expire after 30 to 365 days, 90 by default. An app can connect with OAuth instead of a key.
Free lets the API read and make drafts, with 1 key. Creator has the full API and MCP with 3 keys, plus webhooks and Zapier, Make and n8n. Pro has 10 keys. Agency has the highest limits with 20 keys.
When going direct is still right
If you need something Dripost doesn’t send, such as images on X or posts as a LinkedIn company page, the platform’s own API is where to build it.
Facebook API: publishing to a Page with the Pages API
You publish to a Facebook Page by posting to the Page’s /feed edge with a Page access token, and you can schedule a post by setting published to false.
The endpoints. Meta’s Pages API documentation names a POST to /page_id/feed for posts and /page_id/photos for photos. Video is handled by the separate Video API.
Token and permissions. You need a Page access token obtained through Facebook Login. The permissions listed are pages_manage_posts, pages_manage_engagement, pages_read_engagement and pages_read_user_engagement, plus publish_video for video.
Scheduling in the API. Set published to false and add scheduled_publish_time, as a Unix timestamp, an ISO 8601 string or a strtotime-style phrase.
n8n social media automation: one workflow, six platforms
n8n is good at deciding when and what to post, and Dripost’s API is good at sending it, so a workflow can hand the last step to one HTTP Request node.
What n8n brings. n8n’s documentation calls it a fair-code licensed workflow automation tool that combines AI features with business process automation. You can host it in the cloud or run it yourself.
What each side does. Let n8n watch a feed, a sheet or a form, shape the text, or ask a model for a draft. Let Dripost take the finished post and deliver it to the platforms.
A workflow that works. Start with a trigger, such as a new row. Add the steps that write the post. Finish with an HTTP Request node, set to POST with a JSON body, that calls Dripost’s API with the text, the media and the platforms.
Threads API: publishing posts, limits and the 30-second wait
Threads’ API publishes in two calls, create a container on /threads and then publish it on /threads_publish, with a pause in between while media is processed.
Two calls, one pause. Meta’s documentation describes POST /{threads-user-id}/threads to create a media container and POST /{threads-user-id}/threads_publish to publish it with the container’s ID.
Permissions. Two permissions appear: threads_basic and threads_content_publish.
What a post can hold. Text, images, videos and carousels of up to 20 items are listed.
Sources
Questions
Is there one API that posts to every platform?
Dripost’s REST API posts to six: YouTube, Instagram, Facebook Pages, LinkedIn, Threads and X.
Do I need developer apps for each platform?
Not with Dripost. You connect your accounts once and use one Dripost key.
Can an AI assistant use it too?
Yes. Claude and ChatGPT have been connected to Dripost’s MCP server and tested end to end.
Is there a social media scheduler API?
Yes. Dripost has a public API and an MCP server for scheduling to all six platforms, with keys, scopes and plan limits.
Which social media APIs does Dripost use?
The official ones: Meta's APIs for Instagram, Facebook and Threads, the YouTube Data API, LinkedIn's posting API and the X API. Dripost never logs in with a password or uses unofficial access.
Can I schedule a Facebook post through the API?
Yes. Set published to false and give scheduled_publish_time, between 10 minutes and 30 days ahead.
What token posts to a Page?
A Page access token obtained through Facebook Login.
Does Dripost have an n8n node?
Dripost’s API is documented at dripost.com/docs/api, and n8n’s HTTP Request node can call it.
Which platforms can the workflow post to?
YouTube, Instagram (professional accounts), Facebook Pages, LinkedIn (personal profile), Threads and X (text only).
How long is a Threads text post allowed to be?
500 characters, per Meta’s documentation.
Why wait before publishing a Threads container?
Meta says to wait on average 30 seconds so uploads can be processed.
Post it with Dripost
- Schedule video everywhereAdd your video once; Dripost posts it as a Short, a Reel and a Page video.
- Client approvals, no loginClients see each post as it will look and approve it from a link.
- Post from Claude or ChatGPTDripost's MCP server lets your AI assistant schedule posts. You approve before anything goes out.