Postproxy - Engagement API

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.

Nice one! Good luck with the launch!

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!

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