Postproxy - Engagement API - Publish, reply, and analyze social media via API
by•
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.
Replies
Postproxy
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.
Postproxy
@sven_rabe Thanks, Sven! Your feedback is one of the best feedbacks I've ever had. And what you're building is amazing. We feel incredibly proud that Postproxy is a part of your product. Literally after every call I'm astound of what I've just seen.
Postproxy
@sven_rabe Thank you, Sven. This really means a lot.
A lot of what we built got better because of our calls and your feedback. Plus your excitement and energy always gives us a push ) I honestly wish we had more customers like you.
Thanks for being with us since day one.
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!
Postproxy
@yahav_ohana Thanks for the support, Yahav!
We are big proponents of webhooks and tried to make them as easy to use as possible in Postproxy. They still feel kinda underrated, but once volume grows they are super useful and save a lot of unnecessary polling.
Needle
Nice one! Good luck with the launch!
Postproxy
@jan_heimes thanks mate!
Postproxy
@jan_heimes Thanks, Jan!
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.
Postproxy
@wilder_dev Thanks the comment! Yeah, processing webhooks looks simple until it goes to real production :) To handle spikes and platforms downtime we have a fancy back pressure system in place that takes care of that.
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!.
Postproxy
@murilo_bevervanso Thank you, Murilo. Really appreciate this.
Your feedback has been super helpful and we always happy to hear what works and what doesn't.
Thanks for sticking with us 🙏🏼
Postproxy
@murilo_bevervanso Thanks, man! Happy to see you're happy!
Foyer
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?
Postproxy
@fberrez1 Thanks for the questions, Florent.
No scraping or scraping-adjacent stuff - we only use official APIs, properly verified and approved flows.
Right now we cover 11 platforms: Instagram, TikTok, LinkedIn, X, YouTube, Facebook, Threads, Pinterest, Bluesky, Telegram, and Google Business. Reddit is coming soon.
Small note on X: because of their pretty aggressive API pricing, we keep X more limited in the base plans and offer pay-as-you-go and bring-your-own-key options for products that need heavier X usage.
As for the analytics, we pull data from the native analytics endpoints and expose it through an API, again, no scraping or guessing ourselve. And we do normalise the structure so the metircs are a bit more consistent across platforms.
Trivia by Typito AI
Postproxy
@sadaf_mahmood1 thank you Sadaf!
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?
Postproxy
@yannikga There's no difference what you post via Postproxy – text, image, carousel, video. The API is absolutely the same for every platform and every format and we take care of what you mentioned. Give it a shot! ;)
Postproxy
Yep, exactly as Denis wrote.
And answering your question of "do I still poll each platform.." - no, there is no need to poll each one. Calling GET /api/posts/:id will return per-platform status. Alternatively (and ideally) you can subscribe to post-related webhooks, i.e. platform_post.published fires when it actually went live or platform_post.failed in case something goes wrong.
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.
Postproxy
@hazy0 Yes, you can quickly and easily build reply-once logic on top of Postproxy API. If you need any assistance with that we're always happy to help.
Appreciate it, Denis. To build reply-once cleanly on top, the one thing I would need from the API is a stable idempotent ID per inbound comment/DM, one that survives edits and webhook re-deliveries. Does the payload expose that today, or would I be keying off platform fields that can change? That is the detail that decides whether dedupe is reliable or just best-effort.
Postproxy
@hazy0 We provide idempotent IDs for the inbound comments/DMs that survive edits, re-deliveries and such. And yep, it's exposed today as well. Give it a shot!
And even if something works not as expected we are always happy to help. We have world class support! Check some comments from our customers here ;)