lomi.
Logs

List logs

List logs

Overview

List logs

Returns paginated logs for the organization. The type query parameter selects which log stream to read: api_request, api_error, webhook_delivery, or activity.

When to use this

Use when debugging API errors, auditing webhook deliveries, or building support dashboards.

See also

Retrieve log entry · Webhook delivery logs

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

Base URLs:

  • https://sandbox.api.lomi.africa
  • https://api.lomi.africa

Request

Path parameters

No path parameters beyond the URL pattern.

Query parameters

NameInRequiredSchemaDescription
eventqueryNo-Filter activity logs by event type
failedqueryNo-Only failed webhook deliveries
successqueryNo-Only successful webhook deliveries
webhook_idqueryNo-Filter webhook_delivery logs by webhook ID
severityqueryNo-
statusqueryNo-Comma-separated HTTP status codes (api_request, api_error). Example: 400,500
end_datequeryNo-ISO 8601 end timestamp (inclusive)
start_datequeryNo-ISO 8601 start timestamp (inclusive)
offsetqueryNo-
limitqueryNo-
typequeryYes-Log stream to query

Responses

StatusDescription
200Paginated log list
400Invalid query parameters
401Invalid 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/logs?event=value&failed=true" \
  -H "X-API-KEY: $LOMI_SECRET_KEY"

OpenAPI

  • operationId: LogsController_findAll
  • Operation: GET /logs

Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.

On this page