Retrieve webhook delivery log
Retrieve webhook delivery log
Overview
Retrieve webhook delivery log
Returns a single delivery attempt record.
When to use this
Use when correlating one failure with a specific HTTP response body your server returned.
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/{id}
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
| Name | Required | Schema | Description |
|---|---|---|---|
id | Yes | - | UUID du journal |
Query parameters
No query parameters.
Responses
| Status | Description |
|---|---|
200 | Success |
401 | Invalid or missing API key |
404 | Resource not found |
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/value" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
WebhookDeliveryLogsController_findOne - Operation:
GET /webhook-delivery-logs/{id}
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.