List Webhooks
List every webhook destination registered on your GetXAPI account, with its URL, active or disabled status, and creation time. Signing secrets are never returned.
/twitter/monitor/webhook/listReturn every webhook registered on your account.
Headers
| Header | Type | Required | Description |
|---|---|---|---|
Authorization | string | Yes | Bearer YOUR_API_KEY, the same key used for every other GetXAPI endpoint |
Query Parameters
None. The response is scoped to your account by your API key.
Notes
- Signing secrets are never included. They are only shown once, at creation.
- Use
webhook_idfrom here when adding or repointing monitors.
Response (200)
{
"webhooks": [
{
"webhook_id": "8f14e45f-ceea-467a-9f2b-1c3d4e5f6a7b",
"url": "https://your-server.com/hooks/getxapi",
"status": "active",
"created_at": "2026-07-26T09:14:22.000Z"
},
{
"webhook_id": "2c9a7b31-5d84-4e60-b1f7-9a3c5e2d8f10",
"url": "https://staging.your-server.com/hooks/getxapi",
"status": "active",
"created_at": "2026-07-20T16:02:41.000Z"
}
]
}Response Fields
| Field | Type | Description |
|---|---|---|
webhooks[].webhook_id | string | UUID for attaching monitors |
webhooks[].url | string | Destination URL |
webhooks[].status | string | active or disabled |
webhooks[].created_at | string | ISO 8601 creation time |
Rate limit
60 requests per minute.
Limits use a fixed 60-second window and are shared across every API key on your account, so creating extra keys does not raise the ceiling. Every response carries RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset; a 429 adds Retry-After. See rate limits for the full table.
Errors
| Status | Meaning |
|---|---|
403 | Monitoring is not enabled for this account |
429 | Rate limit exceeded. Wait retry_after seconds, then retry |
Example
curl https://api.getxapi.com/twitter/monitor/webhook/list \
-H "Authorization: Bearer YOUR_API_KEY"Create WebhookNew
Register an HTTPS destination for real-time X/Twitter tweet delivery and receive its HMAC signing secret, which is shown once and never returned again.
Test WebhookNew
Send a real HMAC-signed test payload to your webhook and get back the HTTP status your server returned. Verify your integration before live tweets depend on it.