For developers

Send things to Pending You

Give any service an address, and what it sends shows up in your queue: an error, a failed deploy, a certificate to renew, a decision only you can make. Nothing to install. Hand any of it to one of your assistants to take care of.

Make a webhook
ShellShell
curl -X POST https://www.pendingyou.com/in/pyin_YOUR-WEBHOOK-ADDRESS -H 'content-type: application/json' -d '{"title":"Checkout is failing","dedupeKey":"checkout-500"}'

Make a webhook

Each webhook is one address for one job, with its own name and area. Make one for each service, so you can pause or remove them on their own.

  1. Open Assistants › Incoming webhooks › New webhook.In the Pending You app, signed in as you.
  2. Name it for what it sends, and pick its area.“Production errors” in RecordPlane, say. Its cards read “Production errors · Cloudflare”, so you know at a glance what sent them.
  3. Copy its address.It looks like https://www.pendingyou.com/in/pyin_…, and you see it once. Lost it? Replace it on the same page; the old one stops working at once.
The address is the password
Anyone with it can post notices to your queue. Keep it in your service’s secret settings, not in code or chat. Pending You keeps only a fingerprint of it, never the address itself.

Send a notice

POST JSON to the address. A title is all it needs; the rest makes the card more useful. Without an intent, it’s a heads-up.

TerminalShell
curl -X POST https://www.pendingyou.com/in/pyin_YOUR-WEBHOOK-ADDRESS \
-H 'content-type: application/json' \
-d '{
"title": "Checkout is failing",
"summary": "POST /api/checkout answered 500 for 12 requests in a minute.",
"url": "https://dash.example.com/errors/checkout-500",
"dedupeKey": "checkout-500",
"severity": "error"
}'
JSONJSON
{ "ok": true, "result": "created", "cardId": "req_4f1c9a0e2b7d6c5a8e31", "count": 1 }

The JSON

Fields Pending You doesn’t know are ignored, so you can send your own alongside. Text longer than its limit is shortened rather than refused; ids, options and steps must be right, and a mistake is answered with 422 naming the field.

Field ? optionalTypeWhat it’s for
titlestringWhat happened, in one line. Up to 140 characters.
summary?stringA sentence or two of detail. Up to 400 characters.
url?stringA link to open from the card, such as the error in your dashboard.
dedupeKey?stringRepeats of the same thing share it. While its card is open, a repeat adds to that card instead of making another.
status?"open" | "resolved""open" by default. "resolved" closes the open card with the same dedupeKey. On a question or to-do, "resolved" withdraws it; no answer is sent.
severity?"critical" | "error" | "warning" | "info"How bad it is, shown on the card.
from?stringWho sent it, shown after the webhook’s name. "Webhook" by default. Up to 40 characters.
intent?"heads_up" | "do" | "decide" | "approve" | "tell"What the card asks: "heads_up" (the default), "do", "decide", "approve" or "tell".
options?arrayWith "decide": 2 to 5 of { "id", "label", "detail" }.
recommendedIds?string[]The option you recommend, as ["id"]. On "approve", ["approve"] or ["reject"].
rationale?stringOne sentence on why you recommend it. Up to 200 characters.
action?objectWith "do": { "steps": [ { "text", "command" } ], "where", "done" }. 1 to 12 steps.
text?objectWith "tell": { "placeholder", "suggestions" } for the answer box.
approve?objectWith "approve": { "action", "command", "risk", "reversible" }. The title is the action when it’s left out.
highStakes?booleanIt spends money, can’t be undone or goes public: you hold to send.
urgency?"now" | "today" | "whenever""now", "today" or "whenever". "today" for questions and to-dos, "whenever" for heads-ups.
blocking?booleanSomething has stopped until you answer: the card says Someone’s waiting.
What the card asks: intent
"heads_up" (the default) is something to know: you tap Got it. "do" is a to-do with steps: you tap Done. "decide", "approve" and "tell" ask you something, and your answer is sent to the address you set on the webhook, so they’re taken only once it has one. Every card can be handed to one of your assistants from the card, and it reports back to you.

Ask a question

Say what you need with intent, the same five kinds of card your assistants send. The webhook needs Send answers to first (below) for decide, approve and tell.

A decisionJSON
{
"title": "Roll back checkout-api 4812, or keep it and watch?",
"summary": "Error rate went from 0.2% to 3.1% after deploy 4812. Rollback takes about 2 minutes.",
"intent": "decide",
"options": [
{ "id": "rollback", "label": "Roll back now", "detail": "Back to 4811; the fix ships tomorrow." },
{ "id": "watch", "label": "Keep it, watch 15 minutes", "detail": "Auto-rollback if it passes 5%." }
],
"recommendedIds": ["rollback"],
"rationale": "3.1% is past the 1% budget, and 4811 was clean for a week.",
"severity": "error",
"dedupeKey": "deploy-4812",
"urgency": "now",
"blocking": true,
"url": "https://dash.example.com/deploys/4812"
}
A to-doJSON
{
"title": "Renew the TLS certificate for api.example.com",
"summary": "It expires in 6 days. Auto-renew failed: DNS check on _acme-challenge timed out.",
"intent": "do",
"action": {
"where": "Terminal on the ops box",
"steps": [
{ "text": "Check the DNS record", "command": "dig TXT _acme-challenge.api.example.com" },
{ "text": "Renew it", "command": "certbot renew --cert-name api.example.com" }
],
"done": "certbot says the certificate is valid for 90 days."
},
"severity": "warning",
"dedupeKey": "tls-api-example"
}
  • One question per card.Two to five options for a decision, one to twelve steps for a to-do. Recommend one with recommendedIds and say why in rationale.
  • Say when it’s urgent."urgency": "now" and "blocking": true when something has stopped until you answer. Questions and to-dos notify you; heads-ups wait quietly.
  • Change it by sending a new one.A repeat of the same dedupeKey counts on the open card and keeps its first words. Resolve it, then send the new question.
  • Spends money, can’t be undone or goes public?Set "highStakes": true, and the card asks for a hold to send.

Where answers go

Your answers go to one address you set on the webhook, signed so you can tell they’re from Pending You. A delivery can’t name its own address: that keeps a leaked webhook address from collecting your answers.

  1. Open Assistants › Incoming webhooks, and the webhook.Fill in Send answers to with a public https address.
  2. Copy the signing secret.You see it once. Check x-pendingyou-signature on every answer: t is the time, and v1 is the HMAC-SHA256 of t, a dot and the body.
  3. Answer with 2xx.Pending You sends each answer once your time to undo is up (5 seconds), and tries again if your address doesn’t answer 2xx. x-pendingyou-delivery stays the same on every try, so you can drop repeats.
What arrivesText
POST https://hooks.example.com/pendingyou
content-type: application/json
user-agent: PendingYou-Answers/1 (+https://www.pendingyou.com/docs/webhooks)
x-pendingyou-delivery: dlv_8c1f…
x-pendingyou-signature: t=1760022245,v1=5f2b…
 
{
"type": "card.answered",
"cardId": "req_4f1c9a0e2b7d6c5a8e31",
"dedupeKey": "deploy-4812",
"intent": "decide",
"answer": { "choiceIds": ["rollback"], "note": "Roll back, and page me if 4811 errors too." },
"by": "you",
"answeredAt": "2026-10-09T15:04:05Z"
}
answer fieldWhenValue
choiceIdsdecidethe option ids picked
approvedapprovetrue or false
texttell, or words with a to-dowhat they wrote
done, failedStepdotrue, and the step that didn’t work
noteanytheir words with the answer
handledanytrue: they’ll handle it themselves, and nothing else is sent
Handed to an assistant
When you hand a question to one of your assistants and it answers for you, by is "helper" and helper.name says which. An approval always comes back to you to say yes.

Repeats and resolves

An alert that fires every minute shouldn’t become sixty cards. Give each kind of trouble a dedupeKey, and Pending You keeps it to one.

  • Repeats add to the open card.While a card for a dedupeKey is waiting on you (in your stack or in Later), the same key again adds to it: “Happened 14 times · last 3 min ago”. It keeps its place in your stack.
  • Resolved closes it.Send the same dedupeKey with "status": "resolved" and the card closes on its own. Done says “Resolved by Production errors”.
  • After you’ve seen it, it starts again.Once you tap Got it, or it’s resolved, the next notice with that key is a new card: it happened again after you’d seen it.
Close the cardShell
curl -X POST https://www.pendingyou.com/in/pyin_YOUR-WEBHOOK-ADDRESS \
-H 'content-type: application/json' \
-d '{"title": "Checkout is working again", "dedupeKey": "checkout-500", "status": "resolved"}'

Cloudflare

Paste the address into Cloudflare as a Generic Webhook. Pending You reads Cloudflare’s own payload, so there’s nothing to map.

  1. Workers & Pages › your Worker › Issues › Automations › Add automation.Pick the trigger: how many times an error happens before you hear about it, or an error coming back after a quiet spell.
  2. Destination: Generic Webhook.Give it a name, paste your webhook’s address as the URL, and type any long random text as the secret. Pending You doesn’t need the secret (the address is the secret), and never keeps it.
  3. Turn on Enabled, then Create.Each issue is one card, with its Worker, how often it’s been seen and a link back to it. Cloudflare doesn’t say when you resolve an issue, so tap Got it once it’s fixed.

Answers and limits

Every answer is JSON and comes back fast. Each webhook takes up to 60 deliveries a minute and holds up to 50 notices waiting on you; what’s over is counted on the Assistants page, never shown as cards.

StatusResult or codeWhat it means
201createdA new card, with its cardId.
200repeatedCounted on the card already open for its dedupeKey.
200resolvedThe open card for its dedupeKey closed.
200nothing_openA resolve with no open card to close. Nothing changed.
202pausedThe webhook is paused: counted, not shown.
400not_jsonThe body isn’t JSON.
401unknown_tokenNo webhook has this address: it was replaced or removed, or never made.
413too_largeThe body is over 64 KB.
422invalidA field Pending You can’t take: the answer names it and says why.
429rate_limitedOver 60 a minute. Counted, not shown; Retry-After says when.
429too_many_open50 of its notices already wait on you. Counted, not shown.
Paused
Pausing a webhook on the Assistants page keeps its address working: deliveries are counted and answered 202, and nothing shows until you resume it.
Send a test
Each webhook on the Assistants page has Send a test: Pending You delivers a sample notice as if it had been posted to the address, so you see the card and the count without finding the address again. A second test while that card is open counts on it.