Postproxy is a social media API for products that need more than publishing. Publish posts, manage comments, DMs and reviews, track post and profile analytics, and receive webhooks across major platforms. Built for SaaS products, automation workflows, and agents that need reliable social media infrastructure without maintaining every platform API themselves.
Hey Product Hunt 👋
We launched Postproxy here a few months ago. Back then it was mostly about publishing. We solved the basic but painful problem of posting reliably across platforms, and that layer is still the foundation.
However, publishing a post is not the end of a social workflow. People comment, ask questions in DMs, and leave reviews. Someone has to read that, react somehow, or plug it into the product where the rest of the work already happens.
That is what this launch is about: Postproxy has moved beyond the publish button and now has an engagement API.
You can fetch comments, reply to users, read and send direct messages, and work with reviews through the API. So if you are building a social inbox, a support flow, a moderation tool, a customer dashboard, or an agent that needs to touch social platforms, you do not have to wire every platform yourself.
Of course, things like post stats, profile analytics, webhooks, and the rest of the plumbing are there too. And you can use Postproxy from your backend, automation tools like n8n, Make, Zapier, or Needle, or from whatever agentic setup you have through MCP.
If you have built anything around social APIs before, I'd love to hear where it hurt most.
Cheers,
Dmitry
The biggest challenge with social media isn't posting once, it's maintaining momentum over weeks and months. Tools that reduce that friction can make a real difference. I wonder if the biggest value here is saving time or helping people stay consistent.
The bit I'd want to know: if everyone posts through your one approved app, what happens when a customer abuses it or Meta flags it? Does one bad actor take everyone down, and is there a fallback if a platform suspends you?
Hey, so love itttt!
Skipping the headache of maintaining individual platform APIs is huge. When it comes to publishing, does the API fully support platform-specific native formats like Instagram Stories, YouTube Shorts, and TikTok carousels out of the box cause for most of platforms out there I don't think they fully support API for platform-specific?
The hidden cost of social media integrations isn't building them - it's maintaining them when platforms quietly change OAuth flows, add permission scopes, or drop API endpoints. Is that the maintenance burden Postproxy is taking on? If so, that's actually the valuable part. Curious whether you're absorbing Instagram's graph API versioning cycles and TikTok's business API quirks on behalf of developers, or leaving those edge cases to the caller.
The jump from reliable cross-platform publishing to a reply-and-analyze API is the part that actually closes the loop for community ops, since posting was never the hard half, keeping up with replies across platforms is. For the engagement side, does the API surface inbound comments and DMs with a stable per-item ID, so a team can build a reply-once workflow without two people double-answering the same comment? That dedupe guarantee is the thing that would decide whether I could put this in front of a real community team.
For me the pain was always video. Posting text or an image reliably is one thing, but every platform handles video upload and processing differently, with async transcoding and a status step that fails quietly. Does the publish API roll that into one flow, or do I still poll each platform to know a Reel actually went live?
Most "social media API" products mean Twitter/X plus maybe LinkedIn if you're lucky, with read access that breaks every time a platform updates its terms. Curious which platforms Postproxy actually covers right now and whether you're using official APIs throughout or a mix that includes anything scraping-adjacent. The analyze side is also where I'd want more detail: are we talking raw metrics pulled from native analytics endpoints, or is there some aggregation and normalization happening so you can compare performance across platforms without doing that work yourself?
I've been using Post Proxy across my projects, and it's been fantastic! It solved all my API issues, especially with Instagram. What really sets it apart is the outstanding support. Whenever I have a question or suggestion, the developer responds quickly, genuinely listens to feedback, and continuously improves the platform. It's rare to find a tool with this level of customer support and commitment to its users. Highly recommended!.
I used PostProxy while creating an agent and had a great experience. It was straightforward, easy to use and free from unnecessary fluff. Looking forward to exploring it further and using it more often.
to answer your question: rate limits and silently dropped webhooks are by far the worst part of building custom social integrations. abstracting that away is huge.
how are you handling platform rate limits when fetching comments during a viral spike? awesome update.
I use Postproxy since the very first launch and discovered through Product Hunt. It is truly incredible what has been added during this time and how the two guys handle feedback. Feedback is taken seriously. They even had video calls with me to understand my request. And they implemented it exactly as I wanted it and as it makes sense.
What I also really, really like and what is important is that the two guys really pay close attention to security and reliability. I am excited to see what else is coming. I will definitely stay on board and can only recommend it to everyone.
Congrats on moving beyond just publishing! To answer your question about where it hurts most: for me, it’s always been handling webhooks and unified payloads for DMs. Every platform formats a message or a comment completely differently, so writing the normalization layer is exhausting.
Having a single Engagement API that handles the plumbing for comments and DMs under one roof is a massive time-saver for anyone building SaaS toolboxes. Best of luck with the launch today!
About Postproxy - Engagement API on Product Hunt
“Publish, reply, and analyze social media via API”
Postproxy - Engagement API launched on Product Hunt on June 25th, 2026 and earned 118 upvotes and 32 comments, placing #12 on the daily leaderboard. Postproxy is a social media API for products that need more than publishing. Publish posts, manage comments, DMs and reviews, track post and profile analytics, and receive webhooks across major platforms. Built for SaaS products, automation workflows, and agents that need reliable social media infrastructure without maintaining every platform API themselves.
Postproxy - Engagement API was featured in Messaging (51.9k followers), API (98.4k followers) and Social Media (89.1k followers) on Product Hunt. Together, these topics include over 47k products, making this a competitive space to launch in.
Who hunted Postproxy - Engagement API?
Postproxy - Engagement API was hunted by Dmitry Sereda. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Reviews
Postproxy - Engagement API has received 1 review on Product Hunt with an average rating of 5.00/5. Read all reviews on Product Hunt.
Want to see how Postproxy - Engagement API stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Dmitry Sereda