How to: penneo webhook path rewrite
Use this local guide before 2026-11-30. Re-check official vendor documentation for authoritative dates. This site does not call vendor APIs or store tokens.
- Step 1. Confirm Nov 30 2026 legacy webhook shutdown on Penneo migration guide + deprecation overview
- Step 2. Grep integrations for /api/v1/webhook and list legacy subscriptions
- Step 3. Rewrite base path to /webhook/api/v1 and drop the confirmation step
- Step 4. Map legacy signer/casefile events to Supported eventTypes
- Step 5. Create a test subscription with webhook.subscription.test and POST .../subscriptions/test
- Step 6. Optionally verify x-event-signature on inbound POSTs
- Step 7. Create production v2 subscriptions, then DELETE legacy v1 subscriptions to avoid duplicates
- Step 8. Export Markdown rewrite map with official migration URLs into the ticket
Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates. Export your Markdown pack into the change ticket with the official URLs listed on the home page.
Context for operators: Penneo legacy webhooks shut down Nov30 2026 — /api/v1/webhook → /webhook/api/v1 (e-sign webhook domain). The gap this wedge fills: migration guide 线性;缺可粘贴基址/事件对照+确认步取消提示。不做电子签平台 SaaS。 Keep owners assigned on every residue row so nothing silently slips past the deadline. When in doubt, re-open the official source pages rather than trusting a cached screenshot.