Skip to content
SocialData SocialData

Monitor Event History - API Reference

Every webhook request a monitor sends is recorded, together with the exact payload we posted and the response your server returned. These two endpoints let you read that history.

This is how you recover events that were lost because your endpoint was down, misconfigured, or deployed mid-delivery — failed webhooks are never retried, so replaying from this history is the supported way to backfill.

List monitor events

Returns the 100 most recent webhook events for a single monitor, newest first.

GET https://api.socialdata.tools/monitors/{monitor_id}/events

Headers

Authorization string required

Authorization Bearer header containing your SocialData API key

Example: Bearer YOUR_API_KEY

Path Parameters

monitor_id string required

Target monitor ID

Example: 01jeg76qa91b095gttamsbwa6q

Example Response

{
    "data": [
        {
            "id": "MTAwMDAwMDk4NzY1NDMyMQ==",
            "created_at": "2026-08-01T14:22:31.000000Z",
            "url": "https://my-website.com/webhook",
            "response_code": 200
        },
        {
            "id": "MTAwMDAwMDk4NzY1NDMyMA==",
            "created_at": "2026-08-01T14:19:02.000000Z",
            "url": "https://my-website.com/webhook",
            "response_code": 502
        }
    ]
}

response_code is the HTTP status your server returned. A null value means the request never completed — a timeout, a DNS failure, or a connection that was refused.

Get event details

Returns a single event, including the full webhook payload we sent and the body your server responded with.

GET https://api.socialdata.tools/monitors/{monitor_id}/events/{event_id}

Headers

Authorization string required

Authorization Bearer header containing your SocialData API key

Example: Bearer YOUR_API_KEY

Path Parameters

monitor_id string required

Target monitor ID

Example: 01jeg76qa91b095gttamsbwa6q

event_id string required

Event ID, as returned in the id field by the list endpoint above

Example: MTAwMDAwMDk4NzY1NDMyMQ==

Example Response

{
    "data": {
        "id": "MTAwMDAwMDk4NzY1NDMyMQ==",
        "created_at": "2026-08-01T14:22:31.000000Z",
        "url": "https://my-website.com/webhook",
        "response_code": 502,
        "request_body": "{\"event\":\"new_tweet\",\"data\":{ /* ... full tweet ... */ },\"meta\":{ /* ... */ }}",
        "response_body": "<html><head><title>502 Bad Gateway</title></head></html>"
    }
}

request_body contains the exact JSON we posted to your webhook URL — the same payload documented in Processing webhook events. Parse it to replay the event as if it had been delivered normally.

Response Codes

  • 200 OK - request succeeded
  • 404 Not Found - requested monitor or event does not exist

Before you integrate