ping

When it fires

Doorloom staff send a test, or an automatic probe checks whether a paused endpoint has recovered. Probes run every 30 minutes while an integration is paused.

This event carries neither property nor window.

What to do with it

• A ping is never persisted and consumes no sequence. Its sequence field reports the integration's current last_sequence, so you can compare it against your own cursor to see whether you have fallen behind.
• Do not apply a ping to any state. Just answer 2xx.
• If your integration was auto-paused, the first 2xx you return to a probe resumes delivery and the accumulated backlog drains in sequence order.
• property and window are always null.

The data block

Example

The full envelope, as it arrives on the wire.

{
    "id": "01J6Y0X3V6X9A1C3E5G7J9L1M3",
    "type": "ping",
    "version": "2026-09",
    "sequence": 1047,
    "occurred_at": "2026-10-01T16:30:00+05:30",
    "integration": {
        "id": 12,
        "slug": "acme-pms"
    },
    "property": null,
    "window": null,
    "data": {
        "message": "Test webhook sent from the Doorloom admin panel.",
        "sent_by": "admin"
    }
}

Related

• The event envelope — the wrapper around data, shared by every event.
• Ordering and idempotency — how to decide whether to apply this event.