Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nippy.la/llms.txt

Use this file to discover all available pages before exploring further.

Nippy maintains a log of the last 20 webhook deliveries for your tenant. Use it to verify which events were sent, when, and whether they were received successfully.

​
Query the log

GET https://ms.nippy.la/v1/public/webhooks
x-api-key: npk_live_xxx
x-business-id: your-business-id

curl https://ms.nippy.la/v1/public/webhooks \
  -H "x-api-key: npk_live_xxx" \
  -H "x-business-id: your-business-id"

​
Response

[
  {
    "webhookId": "wh_abc123",
    "event": "spin.completed",
    "status": "delivered",
    "deliveryAttempt": 1,
    "traceId": "trace_xyz",
    "createdAt": "2026-04-30T22:40:34.147Z"
  },
  {
    "webhookId": "wh_def456",
    "event": "spin.completed",
    "status": "failed",
    "deliveryAttempt": 4,
    "traceId": "trace_uvw",
    "createdAt": "2026-04-30T21:15:00.000Z"
  }
]

​
Status values

StatusMeaning
deliveredYour endpoint responded with 2xx
pendingWaiting to be sent or in retry process
failedAll retries exhausted without a 2xx response

​
Diagnosing failed deliveries

If you see deliveries with status: failed, check:
  1. Your endpoint returns 2xx — any other status code (including 200 OK with an error body) counts as a failure
  2. The endpoint is reachable from the internet — Nippy cannot reach localhost or private IPs
  3. The signature is verified correctly — if you reject the signature with 401, Nippy counts it as a failure and retries
// Make sure your handler always responds 200 before processing
app.post('/webhooks/nippy', express.raw({ type: 'application/json' }), async (req, res) => {
  // Respond 200 first, process later
  res.status(200).send('ok')

  const isValid = verifyWebhookSignature({ ... })
  if (!isValid) return  // log but don't crash

  const event = JSON.parse(req.body.toString())
  await processEvent(event)  // async, doesn't block the response
})
Responding 200 before processing the event is a best practice. It avoids timeouts if your processing takes longer than expected and prevents unnecessary retries.

​
Using traceId for support

Each delivery has a unique traceId. If you need the Nippy team to investigate a specific delivery, include the traceId in your report: 
support@nippy.la — subject: "Failed webhook traceId: trace_xyz"