socket.help

Delayed webhooks

Deliver a test webhook after a chosen delay.

Loading your workspace…

About Delayed webhooks

Send a JSON webhook after a delay or on a bounded repeating interval. Scheduled jobs belong to your workspace, survive restarts and retain recent delivery results.

When to use it

Deliver a callback after a delay, then inspect the attempt without keeping a script running.

Delayed webhooks example
POST /api/scheduled-jobs?ttlSeconds=3600
{ "name": "Ready event", "url": "https://example.com/hook", "body": { "event": "test.ready" }, "delaySeconds": 60 }

GET /api/scheduled-jobs/{id} → schedule and delivery events
Receiver: deduplicate X-Socket-Delivery-Id.

How to use it

  1. Sign in and choose a public callback URL without URL credentials.
  2. Enter a JSON payload, delay and optional repeating interval with a run count.
  3. Review delivery attempts or wait for job events from your agent. Delete the job when finished.

Limits & privacy

Payloads are at most 16 KiB. Start 5 seconds to 7 days ahead, repeat every 5 minutes or slower, and run at most 100 times within the resource lifetime. Two retries follow network errors, HTTP 429 or 5xx. Redirects are not followed. Timing is best effort. Delivery is at least once: deduplicate X-Socket-Delivery-Id at the receiver. Destination URL and DNS checks are repeated before every delivery. Jobs never run shell commands or arbitrary code.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.