IpInkpacket

Blog

Why Settings only shows the last 12 webhook deliveries

Inkpacket Settings shows the last 12 webhook deliveries with status, attempt count, and last error. Older rows are not a plan unlock. That is webhook-log honesty — not a missing replay.

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. Older rows are not waiting behind a paid lane. That is webhook-log honesty: twelve rows is the desk list, there is no export of attempt 13, and opening Billing will not “unlock history.”

Why there is no dry-run is why webhooks have no test-send. When a POST misses, when webhook delivery fails. How to verify the HMAC is webhook signature verify checklist. Desk help is Docs. This guide is why the Settings table stops at twelve, and why that stop is not a failed secret.

Ask Inkpacket for why Settings only shows the last 12 webhook deliveries to open this article. Ask how webhooks work to open help. Ask test webhook to open Settings. Those phrases stay on the product screens. This article is the public version of Settings shows the last 12 deliveries with status, attempt count, and last error — the string help already uses next to the table.

What twelve covers

  • The last 12 delivery rows. Status, attempt count, and last error sit on each row.
  • The first POST is attempted immediately. Failed deliveries retry on the hourly envelope job, up to 5 attempts.
  • After 5 failures the row is marked failed. That failed row still occupies a slot in the last 12 until newer events push it out.
  • A missing URL means no delivery is queued. Envelope send still succeeds if the webhook fails.

Need an older attempt? Your receiver is the system of record. Log the JSON on your side. Inkpacket will not replay a row that aged out of the twelve, and there is no test-send or replay button for a row that is still visible either — send an envelope after saving a URL. Free allows 5 packets a month. Reading the table is not a send. A new envelope you send to generate a row does count. HTTP 402 ENVELOPE_LIMIT is that send cap, not a history cap. HTTPS is required except on localhost or .test hosts.

What this is not

  • Not a missing test-send. There is no test-send or replay button even when twelve rows are visible.
  • Not HTTP 429. Access-code 429 is a signer PIN lockout. /api/v1 does not return HTTP 429 for send volume.
  • Not Bearer token required. Webhook Settings is the desk. Public API uses a different door.
  • Not checkout. Billing is not open. Paying a listed price does not add row 13.

Each request includes X-Inkpacket-Event and X-Inkpacket-Signature. Verify with HMAC-SHA256 of timestamp.body using the workspace signing secret. Rotate the secret in Settings if it leaks. Members cannot mint API tokens; owners and admins set the webhook URL. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on the envelope that triggered the POST. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. None of those flags expand the table.

The click-path

  1. Save a webhook URL in Settings. Send an envelope. Confirm a row appears with status and attempt count.
  2. If you need history past twelve, store the POST on your receiver. Do not open Billing for row 13.
  3. If a row is failed after 5 attempts, fix the receiver. Send another envelope. There is no replay button.
  4. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the delivery table.
  5. On a phone, tap Open desk menu for Settings. The last 12 deliveries are the same list. Help is not a drawer row — it stays in the header.

GET /api/v1/health needs no Bearer token and does not list deliveries. Health staying 200 is not a webhook log. Tokens never cross workspaces — a secret from org A will not show org B’s twelve rows. Ask Inkpacket for why Settings only shows the last 12 webhook deliveries to open this article. Ask how webhooks work to open help.

Ask and the table

Ask Inkpacket for why Settings only shows the last 12 webhook deliveries to open this article. Ask how webhooks work or webhook failed to open help. Ask test webhook to open Settings. Marketing Ask stays site Q&A and deep links. It will not replay a delivery, export older rows, or POST a signed body from this article. Twelve is the desk list. Your receiver keeps the rest.

Caps and what is not open yet

Reading the last 12 rows is not a send. Send that creates a new delivery 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 row 13 or invent a replay. The FAQ and Webhooks use Settings shows the last 12 deliveries in the same words.

Watch the twelve. Log the rest on your side. Open a workspace on Free — see published pricing — and send enough throwaway envelopes that an early row ages out so webhook-log honesty is a table that already stopped at twelve, not a checkout you opened for history this pass does not ship.

Open a workspace on Free

Billing is published, not charging. Send an envelope from the desk without a card.

Open a workspace