SOLVORY · PROFESSIONAL WORKSPACEWave 23 · Browser-first
Private receiving endpoint
Creating private webhook session…
URLs are unpredictable. The separate read key is required to view captured requests. Session expires in 15 minutes, max 25 captured requests. Do not send passwords, payment secrets or real customer records.
Send a diagnostic request
Incoming webhook requests
0 captured requests
Session awaiting initialization
Selected event data
No event selected
Authorization, Cookie and credential-like request header names are redacted. Request bodies themselves can still contain secrets—avoid sending sensitive production payloads. No request forwarding or third-party calls.
How to inspect webhooks without deploying an API
The studio creates a unique public receiving URL backed by a temporary WordPress REST endpoint. Copy it into a webhook sender to capture inbound HTTP requests. A separate read secret protects dashboard access. Events appear after live polling every few seconds, and you can inspect methods, content types, safe headers and JSON body values.
Webhook troubleshooting and response codes
The receiving endpoint returns HTTP 202 for accepted requests, HTTP 410 for expired sessions and 429 after the event limit. Valid requests are stored temporarily using WordPress transients rather than permanent posts. Use the local test sender to verify HTTP connectivity before connecting external services.
Privacy, limits and correct usage
Capture windows are limited to 15 minutes and 25 requests, with 64 KB maximum body size. Authorization-like headers are redacted, but arbitrary request bodies can contain confidential information: use synthetic test payloads only. External webhook providers may log the receiving URL and sent payloads. Do not treat the inspector as a durable production webhook receiver.