Lukhoo

Attorney API Integration

Lukhoo API Integration

Connect permission-controlled Lukhoo incidents and conversations to your firm's software through a secure REST API and signed webhooks.

REST
Current authorized records
HMAC
Signed event delivery
2-WAY
Client conversations

Portal Access is the base Lukhoo membership. Add API Integration when your firm wants the same permitted records and conversations inside its own software.

API Integration

Choose how your firm uses Lukhoo.

Choose Portal Access, or add API Integration so your firm can use the portal and connect its own software.

Already have API access? Open the console to create credentials, register a webhook, test delivery, and monitor integration activity. Open API Console

Portal Access

Portal only

Use Lukhoo directly to review permitted prospects, clients, incidents, and messages.

  • No technical setup.
  • Best for direct Lukhoo portal use.
  • Portal access must be active.

Select API membership

Choose Portal + API Integration Access during membership.

Create an API key

Choose only the permissions your firm software needs and store the secret securely.

Add webhook endpoint

Enter the HTTPS URL where Lukhoo sends event updates.

Test and monitor

Verify delivery, then monitor API-key usage, webhook attempts, failures, and retries.

What your software can do

Shared Lukhoo records
IncidentsRead the attorney's current permitted summaries and unlocked details.
ContactOpen or resume a permitted 24-hour prospect conversation.
MessagesReceive client messages and reply from firm software through the same Lukhoo conversation.
HiringRecord the attorney's confirmation; Lukhoo completes the match only after the client also confirms.

Connection and security

Least-privilege access
AuthenticationRestricted bearer API keys are shown once and can be rotated or revoked.
Scopesincidents:read, messages:read, messages:write, engagements:write
DeliveryHTTPS webhooks are signed with HMAC SHA-256 and contain resource references instead of private record details.
EnforcementEvery read, write, download, and delivery checks current membership and client permission.

Payload contract

JSON over HTTPS

REST 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"
  }
}

Two-way messaging

Firm software + Lukhoo
1. ReceiveA client message creates a signed message.created webhook.
2. FetchThe firm follows resource_url to retrieve the currently authorized message.
3. ReplyThe firm sends its response to POST /conversations/{id}/messages with an idempotency key.
4. ContinueThe client receives the reply in Lukhoo. The same message is visible in the API Console and Attorney Portal when each membership permits access.

Available events

Near real-time references
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.

Start in the API Console

Create a key, use the built-in test receiver, register your firm's HTTPS endpoint, and download the OpenAPI and Postman resources.