Get Radar settings
Get Radar settings
Overview
Get Radar settings
Returns whether lomi. Radar screening is enabled for the organization, the monitor/block mode, and card-network passthrough preferences.
When to use this
Use before toggling Radar in your own settings UI or to confirm org configuration in support tools.
See also
Update Radar settings · lomi. Radar guide
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 /organization/radar-settings
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
No path parameters beyond the URL pattern.
Query parameters
No query parameters.
Headers
| Name | In | Required | Schema | Description |
|---|---|---|---|---|
Lomi-Account | header | No | - | Optional lomi. Network account id (acct_...). When present, the API key acts as the Operator and the request targets the connected Member Account. |
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/organization/radar-settings" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
RadarController_getSettings - Operation:
GET /organization/radar-settings
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.