Launched this week
Postproxy
One API to publish to Instagram, TikTok, Youtube and others
169 followers
One API to publish to Instagram, TikTok, Youtube and others
169 followers
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 hi team! great launch, congrats! wondering how do you handle posting content to different geos?
@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.
JDoodle.ai
I like the API-first one-api approach. Is it just for posting or we can comment, read stats, etc?
@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.
Cloudthread
Very cool to see dev friendly scheduling tool - congrats!
@daniele_packard Thank you!
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?
@vik_sh thanks for the question! This is exactly what we spend most of our time on, honestly.
Each platform gets published as an independent job, so if Twitter fails, your Instagram and LinkedIn posts still go through fine. Every post has its own status tracking, so you can see exactly what happened and where.
A few concrete things we do:
- Async platform handling. Some platforms (TikTok, Threads, Instagram carousels) don't give you a post ID immediately. They accept media, process it on their end, and you have to poll for status. We handle that automatically and update the post status when it actually goes live (or fails).
- Error categorization. When something breaks, we parse the actual error message from the API. For example, if Facebook says "access token expired", we mark that profile as inactive so you know to reconnect. If they say "post does not exist" when we're fetching stats later, we mark it as deleted on platform side.
- Rate limit cooldowns. If we hit a quota limit (Twitter is notorious for this), we set a cooldown period on that profile and skip it for stats collection until the window resets.
And when platforms introduce new things (and they do, constantly), we dig in and figure out what changed. Sometimes it's a new error code, sometimes they changed how media processing works. We add handling for it and move on. It's an ongoing thing, the social APIs are a moving target.
Happy to share more details if you're curious about any specifics.