The Webhooks API lets Quant accounts register outbound alert destinations that receive real-timeDocumentation Index
Fetch the complete documentation index at: https://docs.cs2cap.com/llms.txt
Use this file to discover all available pages before exploring further.
alert.triggered events. Custom and Google Sheets destinations receive the signed CS2Cap event JSON. Discord and Telegram destinations receive native message payloads formatted for those platforms. You can inspect delivery history, check retry attempts, and rotate signing secrets without downtime.
Webhooks are available on Quant accounts only.
GET /account/webhooks
Returns all outbound webhook destinations configured for your account. Auth: Bearer token · Rate limit: Standard per-tier RPMResponse example
UUID for this webhook destination.
Display name for the webhook.
Delivery URL.
Delivery platform key:
custom, discord, telegram, or google_sheets.Last four characters of the signing secret. The full secret is shown only at creation or rotation.
Whether the webhook is currently receiving deliveries.
ISO 8601 timestamp of the most recent successful delivery, or
null if none has occurred yet.ISO 8601 timestamp of the most recent failed delivery, or
null.Error message from the most recent failure, or
null.POST /account/webhooks
Creates one outbound webhook destination and returns its signing secret. Auth: Bearer token · Rate limit: Standard per-tier RPMDisplay name for the webhook (e.g.,
Production alerts).Delivery URL. Must be a valid HTTP or HTTPS endpoint.
Delivery platform key. Use
custom for signed CS2Cap JSON, discord for Discord webhooks, telegram for Telegram Bot API sendMessage URLs, or google_sheets for Apps Script-style receivers. Telegram URLs must include a chat_id query parameter.Set to
false to register the webhook in a paused state.Request body
Response example
Full plaintext signing secret for this webhook. Use this to verify the
X-CS2Cap-Signature header on incoming deliveries.GET /account/webhooks/deliveries
Returns outbound webhook delivery jobs for your account, newest first. Auth: Bearer token · Rate limit: Standard per-tier RPMPage size, clamped to 1–100.
Zero-based starting position.
Response example
Delivery job ID.
ID of the alert event that triggered this delivery.
UUID of the webhook destination.
Platform snapshot used for this delivery.
Event type. Currently always
alert.triggered.Delivery status:
pending, succeeded, or failed.Total number of delivery attempts made.
HTTP status code returned by your endpoint on the last attempt.
ISO 8601 timestamp for the next retry, or
null if no retry is scheduled.GET /account/webhooks/deliveries/:id
Returns one webhook delivery job and its full attempt history. Auth: Bearer token · Rate limit: Standard per-tier RPMDelivery job ID to retrieve.
Response example
The JSON body that was sent to your endpoint for this delivery.
Ordered list of delivery attempts for this job.
PATCH /account/webhooks/:id
Updates the editable fields of a webhook destination. Auth: Bearer token · Rate limit: Standard per-tier RPMUUID of the webhook to update.
Updated display name.
Updated delivery URL (HTTP or HTTPS).
Updated delivery platform key. If set to
telegram, the delivery URL must include a chat_id query parameter.Updated active state. Set to
false to pause deliveries without deleting the webhook.Request body
Omit any field to leave it unchanged.
DELETE /account/webhooks/:id
Deletes an outbound webhook destination. Pending deliveries for this destination are cancelled. Auth: Bearer token · Rate limit: Standard per-tier RPMUUID of the webhook to delete.
Response example
POST /account/webhooks/:id/rotate-secret
Rotates the signing secret for a webhook destination and returns the new secret once. Auth: Bearer token · Rate limit: Standard per-tier RPMUUID of the webhook whose secret you want to rotate.
Response example
The new plaintext signing secret. Replace your stored secret with this value immediately.