Native publishing
One service, platform-specific endpoints
Publish to Six Social Platforms Through One API
Connect authorized social accounts once, create a Postifys API key, and automate supported image, video, and feed publishing from your backend, internal tool, or n8n workflow.
API-key authentication
Connected-account targeting
Publish history
curl -X POST \ https://postifys.com/api/instagram/post \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "type": "VIDEO", "mediaUrls": ["https://cdn.example/video.mp4"], "text": "Scheduled from my workflow", "instagramAccountId": "CONNECTED_ACCOUNT_ID" }'
Quick answer
What does Postifys do?
Postifys is a social media publishing service for developers and automation teams. It gives each user one place to authorize supported social accounts, then exposes platform-specific REST endpoints and an n8n community node for publishing, media preparation, account selection, status checks, history, and retry workflows.
Supported publishing workflows
One integration layer, without pretending every platform is identical
Postifys standardizes authentication and operational tracking while preserving the fields, targets, permissions, and approval requirements of each social network.
Native publishing
Instagram Professional
Video upload
YouTube Channels
Access dependent
Pinterest Boards
Member publishing
LinkedIn Members
Creator review
TikTok Creator Inbox
Implementation path
From account authorization to publish status in four steps
Create a user account
Register, verify the email address, and create a Postifys API key from the secure settings page.
Connect social accounts
Complete each platform’s authorization flow. Postifys stores the connection for that user and lists available targets.
Send a platform request
Call the matching endpoint with a connected target, supported media URL, and the fields required by that platform.
Track the result
Use synchronous responses, asynchronous status polling, publish history, queue state, and failure details to operate reliably.
REST endpoint map
Use the endpoint designed for each destination
All publishing calls require a logged-in session or a Postifys API key. Keep API keys in server-side environment variables or a secrets manager.
| Platform | Endpoint | Primary target | Supported workflow |
|---|---|---|---|
/api/facebook/post | Page | Feed, image, Reel | |
/api/instagram/post | Professional account | Image, Reel | |
| YouTube | /api/youtube/post | Channel | Video upload |
/api/pinterest/post | Board | Image Pin, video Pin | |
/api/linkedin/post | Member profile | Text, image, video, link | |
| TikTok | /api/tiktok/post | Creator account | Video upload to inbox |
Built for operations
More than six thin API wrappers
Per-user connections
API keys resolve only the accounts connected by their owner, with target validation before publishing.
Remote media preparation
Queue remote media, inspect it, normalize supported Google Drive links, and serve short-lived files where a platform needs them.
Asynchronous publishing
Accept long-running video work with a submission ID, process it in the background, and query status without holding one HTTP request open.
History and failure reasons
Review recent attempts, platform responses, processing stages, and normalized errors from the dashboard or API.
Retry support
Retry supported failed attempts while preserving their original platform, target, text, and media context.
n8n integration
Use credential testing and dynamic account selectors in the Postifys community node, or call REST endpoints directly.
Clear limitations
What developers should account for before going live
No multi-platform API removes the underlying platform rules. Reliable automation starts with accurate expectations.
Platform review and scopes
Publishing depends on each application’s approved products, scopes, and production access. A successful Postifys connection cannot grant permissions a platform has not approved.
Different content models
Use platform-specific endpoints. Media duration, dimensions, size, privacy, captions, thumbnails, target IDs, and audience controls vary.
Reachable source media
Remote files must be downloadable. Postifys can proxy supported sources, but inaccessible, expired, oversized, or unsupported media will fail validation or platform processing.
Account-type restrictions
Instagram requires a professional account, LinkedIn currently targets members, TikTok uses creator-inbox delivery, and Pinterest writes depend on approved access.
Common use cases
Where a unified publishing service removes repeated integration work
Automation teams
Connect database, storage, approval, and AI-generation workflows to supported social publishing through n8n.
Agencies and operators
Keep each customer’s connected accounts separate, choose specific targets, and review history from one operational dashboard.
Internal applications
Add publishing to a CMS, asset pipeline, CRM, approval tool, or back-office system without putting social credentials in frontend code.
FAQ
Social publishing API questions
Short answers for developers evaluating Postifys.
It lets an application submit supported posts programmatically instead of publishing manually in every network. Postifys provides one authenticated service while each platform keeps its own permissions and content rules.
Connected Facebook Pages, Instagram professional accounts, YouTube channels, Pinterest boards, LinkedIn member accounts, and TikTok creator accounts. Available operations depend on approval and granted permissions.
Yes. Use the Postifys n8n community node with credential testing and connected-account selectors, or call the REST endpoints from an HTTP Request node. See the n8n integration page.
Users authorize their social accounts, create a Postifys API key, and send it as a Bearer token or X-API-Key header. Store the key only in trusted server-side systems.
No. The service and authentication model are unified, but endpoints remain platform-specific because media, caption, privacy, permission, and target requirements differ.
The current production workflow uploads eligible videos to the creator inbox. The creator reviews and completes the post inside TikTok. Direct posting requires separate TikTok approval.
Build the first workflow
Connect an account, create an API key, and publish with verified parameters.
Start with the documentation, then use status and history endpoints to make publishing observable.