Retrieve log entry
Retrieve log entry
Overview
Retrieve log entry
Returns a single log entry by type and ID. Responds with 404 when the entry does not exist or is outside the API key organization scope.
When to use this
Use when drilling into one failed request, webhook delivery, or activity event from a list view.
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 /logs/{type}/{id}
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
| Name | Required | Schema | Description |
|---|---|---|---|
id | Yes | - | Log entry UUID |
type | Yes | - |
Query parameters
No query parameters.
Responses
| Status | Description |
|---|---|
200 | Log entry details |
401 | Invalid or missing API key |
404 | Log not found or access denied |
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/logs/api_request/value" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
LogsController_findOne - Operation:
GET /logs/{type}/{id}
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.