s SuppyHQ

Developer tools and APIs

A support inbox for developer tools and APIs.

The paying customer blocked by a 401 goes first.

Developer tool support is technical and specific. Webhook signatures that don't verify. Rate limits hit in production. A key that stopped working after a plan change. The people writing are usually blocked, and many of them pay you.

Your inbox also gets dev-rel agencies, "we'll write your docs" offers and directory listings, from people who never called your API.

What lands in your support@, sorted

Example emails. Where SuppyHQ puts each one, and why.

On top · Can't wait

  • Our production key stopped working

    A paying customer who can't use what they paid for.

  • Third time asking about the webhook retries

    An upset customer. Answer before they leave.

Lead

  • Is there a free tier for testing?

    A developer evaluating you. Stripe or Polar doesn't know them yet.

Everything else

  • Where do I find the webhook signing secret?

    Asked before. Your answer is already in the composer.

  • Any plans for a Go SDK?

    Waits its turn, oldest first.

Junk

  • We write developer docs that convert

    A content agency's cold pitch.

  • List your API in our marketplace

    A paid-listing pitch from a stranger.

How SuppyHQ sorts it

Junk. Cold pitches, SEO offers and "partnership" emails from strangers go to Junk before you see them. Only a stranger's first email is held back, and only when SuppyHQ is sure. When in doubt, the email stays in your inbox.

On top. A refund, an upset customer, or someone leaving or locked out goes on top, under Can't wait, and emails you right away. A customer whose payment is failing goes on top too when they write. Connect Stripe or Polar and the customer's plan sits next to the email.

Lead. A real question from someone Stripe or Polar doesn't know yet gets a Lead badge. Junk is never a lead.

Everything else waits its turn, oldest first. SuppyHQ never replies for you.

Run support from your terminal

The open-source suppyhq CLI connects the agent you already use: Claude Code, Cursor, Codex, opencode and others. It reads the inbox, pulls the customer's purchase history and writes the reply into the composer.

Drafting and sending are separate permissions, and every send waits 30 seconds so you can cancel it. The email says who wrote it.

Same error, different words

"401 on every call" and "auth broke after upgrading" are the same problem. SuppyHQ matches by meaning, not keywords. When three people write about the same thing in one week, the sidebar lists the others, and the answer you gave them waits above your reply.

Questions

Does AI ever reply on its own?
Not unless you allow it. Suggested replies never send. A connected agent can only send if you tick that permission, every send waits 30 seconds so you can cancel, and the email says an AI wrote it.
Is there an API?
Yes. OAuth2 bearer tokens with read, draft and send scopes, at app.suppyhq.com/api/v1. The suppyhq CLI and MCP server use it.

Pitches out. Paying customers on top.

Solo is $29/mo, free for your first 10 people. No card to start.

Start free

Read next: A support inbox for SaaS on Stripe · A support inbox for open source projects with a paid tier · Stripe customers on top of your support inbox
SuppyHQ: Every use case · Every feature · Security · Pricing