Get risk assessment
Get risk assessment
Overview
Get risk assessment
Returns one Radar assessment by ID, including decision, score, and triggered rule signals.
When to use this
Use when handling PAYMENT_RISK_FLAGGED or PAYMENT_RISK_BLOCKED webhooks keyed by assessment ID.
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 /risk-assessments/{id}
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
| Name | Required | Schema | Description |
|---|---|---|---|
id | Yes | - | Risk assessment ID |
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/risk-assessments/value" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
RadarController_findOne - Operation:
GET /risk-assessments/{id}
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.