Skip to main content
POST
/
webhooks
/
{id}
/
resume
Resume webhook
curl --request POST \
  --url https://xquik.com/api/v1/webhooks/{id}/resume \
  --header 'x-api-key: <api-key>'
Free - does not consume credits
curl -X POST https://xquik.com/api/v1/webhooks/15/resume \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  | jq '{
    webhook_id: .webhook.id,
    resumed: (.success == true),
    status_code: .statusCode,
    delivery_status: .webhook.deliveryStatus,
    consecutive_failures: .webhook.consecutiveFailures,
    failure_hard_cap: .webhook.failureHardCap,
    test_endpoint: ("/api/v1/webhooks/" + .webhook.id + "/test"),
    deliveries_endpoint: ("/api/v1/webhooks/" + .webhook.id + "/deliveries")
  }'
These snippets shape a recovery row. Store delivery_status, consecutive_failures, failure_hard_cap, status_code, and the delivery-log endpoint beside the webhook ID.

​
Path parameters

​
id
string
required
The webhook ID to test and resume.

​
Headers

​
x-api-key
string
required
Your API key. This endpoint also accepts session cookie authentication.

​
What happens

Xquik sends a signed webhook.test request to the webhook URL. If your receiver returns a 2xx status, Xquik reactivates the webhook, resets consecutiveFailures to 0, and returns the updated webhook object. If the signed test fails, Xquik returns 400 with success: false, statusCode, and error. The webhook is not reactivated. This endpoint does not rotate or return the signing secret. Keep using the one-time secret from Create Webhook.

​
Response

​
success
boolean
true when the signed test request succeeded and the webhook was resumed.
​
statusCode
number
HTTP status code returned by your receiver during the signed test.
​
webhook
object
Updated webhook configuration.
{
  "success": true,
  "statusCode": 200,
  "webhook": {
    "id": "15",
    "url": "https://your-server.com/webhook",
    "eventTypes": ["tweet.new", "tweet.reply"],
    "isActive": true,
    "consecutiveFailures": 0,
    "deliveryStatus": "active",
    "failureHardCap": 200,
    "createdAt": "2026-02-24T10:30:00.000Z"
  }
}

​
Recovery handoff

Use this endpoint after fixing a receiver that returned repeated non-2xx responses, became unreachable, or reached deliveryStatus: "needs_attention".

Needs Attention

deliveryStatus: "needs_attention" means the receiver has reached the failure cap. Fix the receiver before resuming.

Signed Test Gate

Resume only succeeds after a signed webhook.test request receives a 2xx response from your receiver.

Failure Counter

Store consecutiveFailures and failureHardCap for alerting and recovery dashboards.

No Secret Rotation

Resume does not return or rotate secret. Keep verifying delivery signatures with the secret returned at creation time.

Delivery Log

After resuming, check List Deliveries for recent status, attempts, lastStatusCode, and lastError rows.

Event Replay

Use delivery streamEventId with Get Event or event list pages to backfill missed downstream work.
This endpoint supports dual authentication: API key (x-api-key header) or session cookie from the dashboard.Related: List Webhooks · Update Webhook · Test Webhook · List Deliveries · Webhook Verification
Last modified on June 23, 2026