The Everra API.

A REST API over your firm's own records. Keys are issued in the workspace under Team, carry read or write scope, and can be revoked the moment they are no longer wanted.

01 — Authentication

One header

Every request carries the key as a bearer token. A key belongs to one firm and can only ever see that firm's records.

curl https://everra-legal.com/api/v1/matters \ -H "Authorization: Bearer ev_live_xxxxxxxxxxxx_yyyyyyyyyyyyyyyyyyyy"

We store only a hash of your key, so it cannot be recovered — if it is lost, revoke it and issue another. Treat it like a password: server-side only, never in a browser or a repository.

02 — Endpoints

What is available today

Method	Path	Returns
GET	/api/v1/matters	Every matter in the firm, newest first.
GET	/api/v1/hearings	Listings and court dates.
GET	/api/v1/clients	Client records.

Responses are { data, count } with up to 200 records. Write endpoints follow; the key scope already distinguishes them.

03 — Calendar

Subscribe without an API key

Hearings and task deadlines publish as an iCalendar feed. Copy the personal URL from the workspace and subscribe in Google Calendar, Outlook or Apple Calendar — it updates itself, and it needs no app registration with anyone.

https://everra-legal.com/api/calendar/feed?t=<your-token>

04 — Rules

What we guarantee

1 A key never crosses firms. Organisation scope is enforced in the query, not the caller.
2 Revocation is immediate — a revoked key fails on its next request.
3 Every key records when it was last used, so a forgotten integration is visible.
4 Breaking changes get a new version path. /api/v1 stays as it is.