API Reference
The NFI Clear API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.Base URL
Content Type
All requests should include theContent-Type: application/json header when sending JSON data.
Response Format
All API responses follow a consistent format:Error Response
HTTP Status Codes
| Code | Meaning |
|---|---|
| 200 | OK - Request succeeded |
| 201 | Created - Resource created successfully |
| 400 | Bad Request - Invalid parameters |
| 401 | Unauthorized - Invalid or missing API key |
| 403 | Forbidden - Insufficient permissions |
| 404 | Not Found - Resource not found |
| 409 | Conflict - Resource already exists |
| 500 | Internal Server Error - Server error |
Endpoints Overview
Verifications
| Method | Endpoint | Description |
|---|---|---|
| POST | /verifications | Create verification |
| GET | /verifications | List verifications |
| GET | /verifications/:id | Get verification |
| GET | /verifications/:id/details | Get full details |
Pagination
List endpoints support pagination usingpage and limit query parameters:
Pagination Response
Filtering
Use query parameters to filter results:| Parameter | Type | Description |
|---|---|---|
status | string | Filter by status: pending, submitted, action_needed, approved, rejected |
type | string | Filter by type: kyc, kyb |
subjectReference | string | Search by subject reference |
sortBy | string | Sort field (default: requestedAt) |
sortOrder | string | Sort order: asc, desc (default: desc) |
Testing
All endpoints include cURL examples. Replacenfi_your_api_key with your actual API key.