List webhook delivery logs
List webhook delivery logs
Overview
List webhook delivery logs
Returns delivery attempts for an outbound webhook endpoint, including HTTP status and retry hints.
When to use this
Use when debugging missed events or proving delivery to auditors.
See also
Authentication
Merchant routes require an API key in the X-API-KEY header (see Integration overview). Use a test key against https://sandbox.api.lomi.africa and a live key against https://api.lomi.africa.
Endpoint
GET /webhook-delivery-logs
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
No path parameters beyond the URL pattern.
Query parameters
| Name | In | Required | Schema | Description |
|---|---|---|---|---|
offset | query | No | - | Nombre de journaux à ignorer (pagination) |
limit | query | No | - | Nombre maximal de journaux |
failedOnly | query | No | - | Uniquement les livraisons en échec |
successOnly | query | No | - | Uniquement les livraisons réussies |
webhookId | query | Yes | - | Filtrer par identifiant de webhook |
Responses
| Status | Description |
|---|---|
200 | Success |
401 | Invalid or missing API key |
Errors
Errors follow the standard JSON error format (status code and machine-readable message). Validate inputs before calling; 401 indicates a missing/invalid key, 404 a missing resource for this organization, 429 rate limiting. For safe retries on create-style calls, send an idempotency key when your flow supports it.
Example
curl -sS -X GET "https://sandbox.api.lomi.africa/webhook-delivery-logs?offset=1&limit=1" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
WebhookDeliveryLogsController_findAll - Operation:
GET /webhook-delivery-logs
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.