Why webhooks have no test-send

Set a workspace webhook URL in Settings, or pass webhookUrl on create/send. Inkpacket POSTs JSON when an envelope is sent, viewed, signed, completed, expired, declined, voided, or corrected. Settings shows the last 12 deliveries with status, attempt count, and last error. There is no test-send or replay button — send an envelope after saving a URL. That is no-test-send honesty: the first POST is a real lifecycle event, failed rows retry on the hourly job, and opening Billing will not add a “Send test” control this pass does not ship.

How to listen at all is listen for envelope status webhooks. When a POST misses, when webhook delivery fails. The HMAC is webhook signature verify checklist. Desk help is Docs. This guide is why Settings has a log and not a dry-run.

Ask Inkpacket for webhooks have no test-send to open this article. Ask how do I test a webhook to open help. Ask test webhook to open Settings #webhooks. Those phrases stay on the product screens. This article is the public version of why “how do I test a webhook” still means send a real envelope.

What you do instead

• Save an HTTPS URL (localhost or .test is allowed). A missing URL means no delivery is queued.
• Send an envelope. The first POST is attempted immediately on that event.
• Read the last 12 rows. Status, attempt count, last error.
• If it fails, wait for the hourly envelope job. Up to 5 attempts. After 5 failures the row is marked failed. There is no replay button.

Envelope send still succeeds if the webhook fails. Do not treat a signed PDF as proof your endpoint stored the JSON. Do not void a completed envelope to “re-fire completed” — completed envelopes cannot be changed. Send another throwaway if you need another event. That send counts. Free allows 5 packets a month.

What this is not

• Not a missing Settings page. On a phone, Settings is a drawer row. The webhook card is still there after you open it.
• Not a plan gate. Starter is 20 envelopes — more than Free. A listed price does not add test-send.
• Not health. GET /api/v1/health is public and does not POST to your URL — why GET /api/v1/health needs no Bearer token.
• Not checkout. Billing is not open. Paying does not unlock replay.

Each request includes X-Inkpacket-Event and X-Inkpacket-Signature as t=unix,v1=hex. Verify with HMAC-SHA256 of timestamp.body using the workspace signing secret. Rotate the secret in Settings if it leaks. A bad signature is your check failing, not a test-send you skipped. Retries explained live in webhook retries explained.

The click-path

1. Owner or admin: open Settings → webhooks. Paste the URL. Save.
2. Send a throwaway envelope from the desk or POST /api/v1/packets/:id/send.
3. Watch the last 12 deliveries. If the first POST misses, wait for the hourly job.
4. After 5 failures, fix the endpoint and send another envelope. There is no replay on the failed row.
5. On a phone, tap Open desk menu for Settings. Help is not a drawer row — it stays in the header.

Create and send still accept an Idempotency-Key if your client may retry. That key does not fire a webhook by itself — send does. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on that send. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags invent a test-send button.

Ask and the log

Ask Inkpacket for webhooks have no test-send to open this article. Ask how do I test a webhook to open help. Marketing Ask stays site Q&A and deep links. It will not POST to your URL or replay a failed row from this article. Ask test webhook when you want the Settings card, not a dry-run.

Caps and what is not open yet

Saving a webhook URL is not a send. Send is. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not add a test-send or replay a failed delivery. The FAQ and Webhooks use There is no test-send or replay button — send an envelope after saving a URL in the same words.

Save the URL. Send a real envelope. Read the log. Open a workspace on Free — see published pricing — and fire one throwaway so no-test-send honesty is a missing button you have already looked for, not a dry-run you hoped Billing would unlock.