Portal Access
Portal onlyUse Lukhoo directly to review permitted prospects, clients, incidents, and messages.
- No technical setup.
- Best for direct Lukhoo portal use.
- Portal access must be active.
Connect permission-controlled Lukhoo incidents and conversations to your firm's software through a secure REST API and signed webhooks.
Portal Access is the base Lukhoo membership. Add API Integration when your firm wants the same permitted records and conversations inside its own software.
Choose Portal Access, or add API Integration so your firm can use the portal and connect its own software.
Choose Portal + API Integration Access during membership.
Choose only the permissions your firm software needs and store the secret securely.
Enter the HTTPS URL where Lukhoo sends event updates.
Verify delivery, then monitor API-key usage, webhook attempts, failures, and retries.
incidents:read, messages:read, messages:write, engagements:writeREST responses and webhooks use JSON. Webhooks contain a stable event identifier and an authorized resource reference; firm software then fetches the current record with its API key.
{
"spec_version": "1.0",
"event_id": "b38d0a60-2367-4c67-a6ad-bb9d83243a12",
"sequence": "125",
"event_type": "message.created",
"created_at": "2026-09-08T18:00:00.000Z",
"data": {
"resource_type": "message",
"resource_id": "456",
"resource_url": "/api/attorney/v1/messages/456"
}
}
message.created webhook.resource_url to retrieve the currently authorized message.POST /conversations/{id}/messages with an idempotency key.incident.createdincident.updatedincident.removed
conversation.updatedmessage.createdmessage.updated
Evidence availability and future incident-score changes are delivered through incident.updated. Webhooks are the primary notification channel; the event cursor supports recovery and reconciliation.
Create a key, use the built-in test receiver, register your firm's HTTPS endpoint, and download the OpenAPI and Postman resources.