Customer portal audit log
Customer portal audit log
Overview
Customer portal audit log
Returns portal activity for a customer (sign-ins, subscription changes, etc.) for support and compliance.
When to use this
Use when investigating billing disputes or verifying what the customer changed in the portal.
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 /customers/{id}/portal-audit
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
| Name | Required | Schema | Description |
|---|---|---|---|
id | Yes | - | UUID du client |
Query parameters
| Name | In | Required | Schema | Description |
|---|---|---|---|---|
eventType | query | No | - | Filtre sur customer_portal_audit_events.event_type |
pageSize | query | No | - | |
page | query | No | - |
Responses
| Status | Description |
|---|---|
200 | Success |
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/customers/value/portal-audit?eventType=value&pageSize=1" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
CustomersController_getPortalAudit - Operation:
GET /customers/{id}/portal-audit
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.