Launching today
Postproxy

Postproxy

One API to publish to Instagram, TikTok, Youtube and others

150 followers

Visit website
•
•
Postproxy is a unified publishing API for social networks. Built for developers who automate content at scale. One endpoint, explicit states, built-in retries. And scheduling, of course.
Postproxy gallery image
Postproxy gallery image
Postproxy gallery image
Postproxy gallery image
Postproxy gallery image
Postproxy gallery image
Postproxy gallery image
Free
Launch tags:API•Social Media•Developer Tools
Launch Team / Built With
Intercom
Intercom
Startups get 90% off Intercom + 1 year of Fin AI Agent free
Promoted

What do you think? …

Dmitry Sereda
Maker
📌
Hey Product Hunt 👋 When we started building 64ads (an AI-driven platform for generating marketing assets at scale), we genuinely thought publishing would be the trivial part. Like, "we'll just hit the API at the end and call it done." Turns out we massively underestimated what "just integrate publishing" actually means: - Each platform has its own app review process (some take weeks) - Each has different verification requirements before you can even post - Twitter's API works completely differently from LinkedIn's, which is nothing like Instagram's - Rate limits aren't just "requests per hour" – they're nested, conditional, and platform-specific - Orchestrating all of this together so that partial failures don't cascade? Way more tricky than we expected. We ended up spending weeks on what was supposed to be a side quest. Our product is about AI content generation - that's where we wanted our focus to be. Instead, we were stuck dealing with app reviews and debugging why LinkedIn would trim the text in the middle. So, we decided to make it a separate product - Postproxy - and today we're launching with 7 platforms (Twitter, LinkedIn, Facebook, Instagram, YouTube, Threads, TikTok) and three ways to integrate: REST API, n8n community node, or MCP server for AI agents. Would love to hear if anyone else has felt this pain. What broke your automation? Platform oddities? The gap between "API says ok" and "actually published"? Happy to answer any technical questions about how we handle the messy reality of multi-platform publishing Cheers, Dmitry
Gokul Chandrasekaran
JDoodle.ai

I like the API-first one-api approach. Is it just for posting or we can comment, read stats, etc?

Dmitry Sereda
Maker

@gokuljd, thanks!

Our core focus is on reliably getting content out to platforms, not managing conversations. That said, for some platforms, we do support limited extras where it makes sense. For example, adding a first comment on publication is available for Instagram.

We also regularly collect post-level statistics. Those are available both via the API and in the app, so you can monitor performance after publishing.

Anton Ponikarovskii

@Postproxy hi team! great launch, congrats! wondering how do you handle posting content to different geos?

Dmitry Sereda
Maker

@ponikarovskii Hi Anton, thank you!
We currently treat geo targeting as an upstream concern and focus on publishing, while regional content variants are usually resolved before the API call.

We don’t expose geo-gating controls yet, but I would love to learn more about your use case.

Daniele Packard

Very cool to see dev friendly scheduling tool - congrats!

Dmitry Sereda
Maker

@daniele_packard Thank you!

Viktor Shumylo

Congrats on the launch! Splitting publishing into a dedicated layer makes a lot of sense given how inconsistent and fragile platform APIs can be. How does Postproxy handle partial failures or edge cases, like when one platform silently modifies content or rejects a post after initially accepting the request?