Fylely API and webhooks
Connect a receptionist service, a lead vendor, a timer or a firm's own scripts to Fylely. There is a JSON API over HTTPS, webhooks that tell your tool when something happens, an OpenAPI file, and a connector for Claude. The firm's owner makes the key; you do not need a Fylely account to build against it. This page describes the API and shows no firm's data.
Start here
- Base address
- https://fylely.com
- Header on every request
- Authorization: Bearer fy_live_…
- Bodies and answers
- JSON, sent with Content-Type: application/json.
Check a key works by asking which firm and key it is:
curl "https://fylely.com/api/v1/me" \ -H "Authorization: Bearer fy_live_…"
Call the API from a server, or from a service such as Zapier or Make, never from a web page's own JavaScript, where every visitor could read the key. A browser posting to it from another website is refused.
Getting a key
Only the firm's owner can make a key, in Fylely under Settings → Connections → API keys. Ask them for one, made just for your tool, so they can revoke it without stopping anything else. A firm can have 5 keys at a time. A key starts with fy_live_ and is shown once: Fylely keeps only a fingerprint of it.
Every key can read. Anything more is a switch on the key, off until the owner turns it on:
| Switch | What it allows |
|---|---|
| Can also create enquiries | Sends enquiries into the firm’s Potential matters. Any other key gets 403. |
| Can also set up its own webhooks | Adds a webhook of its own, one event to one address. Any other key gets 403. |
| Allow changes | Adds and changes contacts, matters, tasks, time and notes, as the person who made the key. Turning it on needs an authenticator app or a passkey on the owner’s account. Any other key gets 403. |
Turning on Allow changes also needs the owner to have passed two-step sign-in in the session they do it from. A key that changes records acts as the person who made it, every time: what it adds is logged under their name, and it can do only what their role in Fylely lets them do. No key can delete a record. A fourth switch, Allow suggestions, is for AI assistants (below).
Revoking a key stops it at its next call and removes the webhooks it set up for itself. An AI assistant that signed in rather than using a key can read, but never send enquiries, set up webhooks or change records.
Endpoints
Every path below is under https://fylely.com. An id is one this API gave out. A write needs the switch named on it.
Reading
Every key can read. Each answer is JSON.
The key in use
GET /api/v1/me
The firm the key belongs to, and the key. Call it first to check a key works.
Key: Any key. Answers 200 with { "data": Me }. The answer has: firm (id, name), key (id, name, prefix).
List matters
GET /api/v1/matters
Estates, guardianships and cases in one list, each with its kind.
Key: Any key. Answers 200 with { "data": [Matter, …], "next_cursor": "…" }. A matter has: id, kind, name, type, status, case_number, file_number, state, county, court_name, client_id, responsible_email, date_of_death, appointment_date, opened_on, closed_on, is_sample, created_at, updated_at.
| Filter | What it does |
|---|---|
| kind | Only this kind of matter. One of: estate, guardianship, case. |
| status | Only open or only closed matters. One of: open, closed. |
| updated_since | Only matters changed since then: a date (2026-01-31) or a time (2026-01-31T09:00:00Z). |
Paged: limit and cursor, below.
Get a matter
GET /api/v1/matters/{id}
One matter, whichever kind it is. Another firm’s matter and one that never existed are the same 404.
Key: Any key. Answers 200 with { "data": Matter }. A matter has: id, kind, name, type, status, case_number, file_number, state, county, court_name, client_id, responsible_email, date_of_death, appointment_date, opened_on, closed_on, is_sample, created_at, updated_at.
List deadlines
GET /api/v1/deadlines
Deadlines across every matter.
Key: Any key. Answers 200 with { "data": [Deadline, …], "next_cursor": "…" }. A deadline has: id, matter_id, matter_kind, matter_name, title, category, due_date, status, completed_at, created_at.
| Filter | What it does |
|---|---|
| matter_id | Only this matter’s deadlines. |
| status | Waived and vacated are closed without being met. One of: upcoming, done, waived, vacated. |
| due_from | Due on or after this date. |
| due_to | Due on or before this date. |
Paged: limit and cursor, below.
List contacts
GET /api/v1/contacts
Clients and other contacts: names and how to reach them.
Key: Any key. Answers 200 with { "data": [Contact, …], "next_cursor": "…" }. A contact has: id, type, category, name, email, phone, address (full, line1, unit, city, region, postal_code, country, withheld), status, preferred_contact, created_at, updated_at.
Paged: limit and cursor, below.
List invoices
GET /api/v1/invoices
Number, matter, status, dates and totals.
Key: Any key. Answers 200 with { "data": [Invoice, …], "next_cursor": "…" }. An invoice has: id, number, matter_id, matter_kind, matter_name, status, issue_date, due_date, sent_at, paid_at, currency, total, settled, collected, balance, created_at, updated_at.
| Filter | What it does |
|---|---|
| status | Only invoices with this status. One of: draft, sent, paid, void. |
Paged: limit and cursor, below.
Sending in an enquiry
An enquiry lands in the firm’s Potential matters, the same list its intake form fills. It does not make a contact or a matter: someone at the firm still decides what it becomes.
Send in an enquiry
POST /api/v1/enquiries
Puts one enquiry in Potential matters, marked as sent by the key, and sends the intake.received webhook. Sending the same enquiry twice makes two: there is no check for repeats.
Key: Can also create enquiries. Answers 201 with { "data": Enquiry, "ignored": [] }. An enquiry has: id, status, created_at.
| Field | Takes | Notes |
|---|---|---|
| name* | text | Required. Up to 120 characters. |
| text | An email address. Send this, phone, or both. | |
| phone | text | Up to 40 characters. Send this, email, or both. |
| matter_type | text | What it is about, in the enquirer's words or yours. Up to 80 characters. |
| description | text | Their message. Line breaks are kept. Up to 4000 characters. |
| source_page | text | The full address of the page the enquiry was made on. Only the site and path are kept; the rest of the address is dropped. |
| utm_source | text | A campaign label, as on a link. Up to 100 characters. |
| utm_medium | text | The same, up to 100 characters. |
| utm_campaign | text | The same, up to 100 characters. |
* required. Every field is a string, or null to leave it out. Text longer than its limit is cut to fit, not refused. Any other field is not saved: it is listed back in ignored.
curl -X POST https://fylely.com/api/v1/enquiries \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"name": "Grace Lin",
"email": "grace@example.com",
"phone": "555-0142",
"matter_type": "Probate",
"description": "My father died last month and I am named executor.",
"source_page": "https://yourfirm.com/probate",
"utm_source": "google"
}'Webhooks a tool sets up
For a tool that turns its own events on and off. A key can remove only what it added.
Set up a webhook
POST /api/v1/hooks
Sends one event to an address the tool chooses. Asking again for the same address and event answers 200 with the one already there.
Key: Can also set up its own webhooks. Answers 201 with { "data": Hook }. A webhook has: id, event, target_url, created_at.
| Field | Takes | Notes |
|---|---|---|
| target_url* | text | Required. A public https address on the standard port. It cannot point at Fylely. |
| event* | text | Required. One of: matter.created, matter.closed, intake.received, deadline.created, deadline.completed, invoice.sent, payment.recorded, signature.completed. |
* required.
curl -X POST https://fylely.com/api/v1/hooks \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"target_url": "https://hooks.example.com/abc",
"event": "matter.created"
}'Remove a webhook
DELETE /api/v1/hooks/{id}
Stops a webhook this key set up. Any key may call it, even after its permission is taken away; it reaches only its own.
Key: Any key. Answers 200 with { "data": HookRemoved }. The answer has: id, deleted.
Sample deliveries
GET /api/v1/hooks/samples
What a delivery of an event looks like, from the firm’s own recent records where a key can read them, otherwise made up.
Key: Any key. Answers 200 with { "data": [Delivery, …], "next_cursor": null }. A delivery has: id, event, created_at, data.
| Filter | What it does |
|---|---|
| event* | The event to show. One of: matter.created, matter.closed, intake.received, deadline.created, deadline.completed, invoice.sent, payment.recorded, signature.completed. |
Adding and changing records
A key writes as the person who made it: what it adds is logged under their name, and it can do only what their role in Fylely lets them do. A private matter they are not on is not found (404). Nothing here deletes anything.
Add a contact
POST /api/v1/contacts
Adds a contact, and answers with it as the contacts list gives it.
Key: Allow changes. Answers 201 with { "data": Contact, "ignored": [] }. A contact has: id, type, category, name, email, phone, address (full, line1, unit, city, region, postal_code, country, withheld), status, preferred_contact, created_at, updated_at.
| Field | Takes | Notes |
|---|---|---|
| name* | text, up to 200 characters | |
| type | text, one of: individual, organization | |
| category | text, one of: potential_client, client, vendor, other | |
| email, up to 320 characters | ||
| phone | text, up to 50 characters | |
| address_line1 | text, up to 200 characters | |
| address_unit | text, up to 100 characters | |
| city | text, up to 100 characters | |
| region | text, up to 100 characters | |
| postal_code | text, up to 20 characters | |
| country | text, up to 100 characters | |
| preferred_contact | text, one of: any, email, phone, post | |
| automated_email | true or false | Whether Fylely may email them automatically. true if not sent. |
| job_title | text, up to 200 characters | |
| email_secondary | email, up to 320 characters | |
| phone_secondary | text, up to 50 characters | |
| website | text, up to 500 characters | |
| referral_source | text, up to 200 characters | |
| aliases | list of names, each up to 200 characters | |
| notes | text, up to 10000 characters |
* required. null or an empty string leaves a field out. A field of the wrong type, too long, or not one of its values is 400. Any other field is not saved: it is listed back in ignored.
curl -X POST https://fylely.com/api/v1/contacts \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"name": "Grace Lin",
"email": "grace@example.com",
"phone": "555-0142",
"category": "potential_client"
}'Change a contact
PATCH /api/v1/contacts/{id}
Changes the fields sent and keeps the rest. null clears one.
Key: Allow changes. Answers 200 with { "data": Contact, "ignored": [] }. A contact has: id, type, category, name, email, phone, address (full, line1, unit, city, region, postal_code, country, withheld), status, preferred_contact, created_at, updated_at.
| Field | Takes | Notes |
|---|---|---|
| name | text, up to 200 characters | |
| type | text, one of: individual, organization | |
| category | text, one of: potential_client, client, vendor, other | |
| email, up to 320 characters | ||
| phone | text, up to 50 characters | |
| address_line1 | text, up to 200 characters | |
| address_unit | text, up to 100 characters | |
| city | text, up to 100 characters | |
| region | text, up to 100 characters | |
| postal_code | text, up to 20 characters | |
| country | text, up to 100 characters | |
| preferred_contact | text, one of: any, email, phone, post | |
| automated_email | true or false | |
| job_title | text, up to 200 characters | |
| email_secondary | email, up to 320 characters | |
| phone_secondary | text, up to 50 characters | |
| website | text, up to 500 characters | |
| referral_source | text, up to 200 characters | |
| aliases | list of names, each up to 200 characters | |
| notes | text, up to 10000 characters |
* required. Send only what changes; null clears a field. Any other field is not saved: it is listed back in ignored.
curl -X PATCH https://fylely.com/api/v1/contacts/{id} \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"phone": "555-0199",
"preferred_contact": "phone"
}'Open a matter
POST /api/v1/matters
Opens an estate, a guardianship or a case (kind), with the starter checklist the new-matter form gives it, and sends the matter.created webhook. Answers with the matter. Not applied yet: the firm’s automatic file numbers (send file_number instead) and its rules for when a matter is opened.
Key: Allow changes. Answers 201 with { "data": Matter, "ignored": [] }. A matter has: id, kind, name, type, status, case_number, file_number, state, county, court_name, client_id, responsible_email, date_of_death, appointment_date, opened_on, closed_on, is_sample, created_at, updated_at.
| Field | Takes | Notes |
|---|---|---|
| kind* | text, one of: estate, guardianship, case | |
| name* | text, up to 200 characters | The person who died for an estate, the protected person for a guardianship, the case name for a case. |
| type | text, up to 100 characters, only for a case or a guardianship | A case’s type, in your words. For a guardianship, one of: guardianship_person, conservatorship_estate, both, minor_guardianship. |
| client_id | id | The id of one of the firm’s contacts. |
| responsible_email | email, up to 320 characters | The address of the person at the firm responsible for it. |
| state | text, up to 10 characters | |
| county | text, up to 100 characters | |
| court_name | text, up to 200 characters | |
| case_number | text, up to 100 characters | |
| file_number | text, up to 40 characters | |
| opened_on | date, only for an estate or a case | |
| date_of_death | date, only for an estate | |
| appointment_date | date, only for a guardianship |
* required. null or an empty string leaves a field out. A field of the wrong type, too long, or not one of its values is 400. Any other field is not saved: it is listed back in ignored.
curl -X POST https://fylely.com/api/v1/matters \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"kind": "estate",
"name": "Jordan Reed",
"state": "WA",
"county": "King",
"date_of_death": "2026-10-02"
}'Add a task
POST /api/v1/matters/{id}/tasks
Adds a task to the matter. Someone at the firm it is assigned to is told, as in Fylely.
Key: Allow changes. Answers 201 with { "data": Task, "ignored": [] }. A task has: id, matter_id, matter_kind, matter_name, title, category, due_date, status, assignee_email, completed_at, created_at.
| Field | Takes | Notes |
|---|---|---|
| title* | text, up to 500 characters | |
| due_date | date | |
| category | text, up to 100 characters | |
| assignee_email | email, up to 320 characters | Someone on the firm’s team. |
| notes | text, up to 10000 characters | Saved, but not sent back: the API does not read them. |
* required. null or an empty string leaves a field out. A field of the wrong type, too long, or not one of its values is 400. Any other field is not saved: it is listed back in ignored.
curl -X POST https://fylely.com/api/v1/matters/{id}/tasks \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"title": "Call the clerk",
"due_date": "2026-12-01",
"assignee_email": "sam@yourfirm.com"
}'Mark a task done or open
PATCH /api/v1/tasks/{id}
Marks a task done, or open again. A repeating task makes its next one. A task still waiting on unfinished work is 409.
Key: Allow changes. Answers 200 with { "data": Task, "ignored": [] }. A task has: id, matter_id, matter_kind, matter_name, title, category, due_date, status, assignee_email, completed_at, created_at.
| Field | Takes | Notes |
|---|---|---|
| status* | text, one of: done, open |
* required. null or an empty string leaves a field out. A field of the wrong type, too long, or not one of its values is 400. Any other field is not saved: it is listed back in ignored.
curl -X PATCH https://fylely.com/api/v1/tasks/{id} \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"status": "done"
}'Log time
POST /api/v1/matters/{id}/time-entries
Logs time in whole minutes, at the usual rate unless one is sent. Answers with the minutes kept after the firm’s rounding. A body with "hours" in it is refused.
Key: Allow changes. Answers 201 with { "data": TimeEntry, "ignored": [] }. A time entry has: id, matter_id, matter_kind, matter_name, entry_date, minutes, billable, created_at.
| Field | Takes | Notes |
|---|---|---|
| entry_date* | date | |
| minutes* | whole number | Whole minutes: 90 for 1h 30m. Hours are not taken. |
| description* | text, up to 5000 characters | Saved, but not sent back: the API does not read it. |
| billable | true or false | true if not sent. |
| hourly_rate | number | Used only when the key’s person can see billing. |
| task_code | text, up to 10 characters | |
| activity_code | text, up to 10 characters |
* required. null or an empty string leaves a field out. A field of the wrong type, too long, or not one of its values is 400. Any other field is not saved: it is listed back in ignored.
curl -X POST https://fylely.com/api/v1/matters/{id}/time-entries \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"entry_date": "2026-12-01",
"minutes": 90,
"description": "Call with the client about the inventory"
}'Add a note
POST /api/v1/matters/{id}/notes
Adds a note to the matter. Colleagues it @mentions are told. What it says is not sent back.
Key: Allow changes. Answers 201 with { "data": Note, "ignored": [] }. A note has: id, matter_id, matter_kind, matter_name, created_at.
| Field | Takes | Notes |
|---|---|---|
| body* | text, up to 20000 characters |
* required. null or an empty string leaves a field out. A field of the wrong type, too long, or not one of its values is 400. Any other field is not saved: it is listed back in ignored.
curl -X POST https://fylely.com/api/v1/matters/{id}/notes \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"body": "Client called: the bank wants a certified copy of the letters."
}'Dates are year-month-day, such as 2026-12-01. Time is whole minutes, sent and answered: 90 for 1h 30m. Opening a matter sends the matter.created webhook, as one opened in Fylely does; the other changes have no webhook of their own.
Lists and paging
Lists come newest first, 50 at a time. Ask for more with limit, up to 200. Each answer is { "data": [...], "next_cursor": "..." }: pass next_cursor back as cursor for the next page, and stop when it is null. Records added while you page appear at the front and never shift what is still to come. A cursor this API did not give out is 400.
Errors
Anything but a 2xx answers { "error": { "code": "...", "message": "..." } }. The message says, in words, what went wrong.
| Status | Code | When |
|---|---|---|
| 200 | — | Done: a read, a change, or a webhook that was already there. |
| 201 | — | Made: an enquiry, a webhook or a record. |
| 400 | invalid_request | Something sent is wrong: a filter, a cursor, a missing required field, or a field of the wrong type. The message says which. |
| 401 | unauthorized | No key, or a key that is not valid or was revoked. |
| 403 | forbidden | The key is valid but may not do this; or the firm is suspended; or, for a change, the plan’s matter limit or an ended trial. |
| 404 | not_found | No such record for this firm, or a private matter the key’s person is not on. |
| 409 | conflict | A file number already in use, a task still waiting on unfinished work, or a request with the same Idempotency-Key still being saved. |
| 413 | invalid_request | The body is too large. |
| 415 | invalid_request | The body is not sent as application/json. |
| 422 | invalid_request | An Idempotency-Key already used for a different request. |
| 429 | rate_limited | Too many requests. Wait for the seconds in Retry-After. |
| 503 | unavailable | Fylely could not finish it just now. Nothing was saved, so it is safe to send again. |
Limits
| What | Limit |
|---|---|
| Requests, per key (or per signed-in assistant) | 120 a minute |
| Requests without a valid key, per address | 20 a minute |
| Enquiries, per key | 30 an hour |
| Webhooks set up, per key | 60 an hour, and 25 at a time |
| Changes to records, per key | 30 a minute and 600 an hour |
| Body of an enquiry | 16 KB |
| Body of a webhook request | 4 KB |
| Body of a change | 16 KB |
| Items on one page of a list | 200 (50 if not asked) |
| Keys per firm | 5 at a time |
| Webhooks the owner adds by hand | 5 |
Past a limit the answer is 429 with a Retry-After header, in seconds, and nothing is saved. The writes' own limits count on top of the 120 requests a minute every key has. A request that was refused does not use up the hour.
Safe retries
To make a retry of a change safe, send an Idempotency-Key header: 1 to 255 letters, digits and symbols with no spaces, new for each change, such as the record's own id in your tool. For 24 hours the same key with the same request answers with what the first one did, marked Idempotent-Replayed: true, and saves nothing again. The answer is the record as it is now; if it has since been deleted, only its id. The same key with a different request is 422; while the first is still being saved, 409. A change that was refused or failed does not use up its key.
This is for adding and changing records. An enquiry sent twice makes two, so send it once. Asking twice for the same webhook answers with the one already there.
Webhooks
Fylely posts a short JSON message to an https address when something happens. The firm's owner can add up to 5 by hand under Settings → Connections → Webhooks, each for any of the events below. A tool whose key has “Can also set up its own webhooks” can add its own with POST /api/v1/hooks, one event per address, up to 25 per key. The address must be public, on the standard https port, and not Fylely's own.
Each delivery is a POST with the body { "id", "event", "created_at", "data" } and the headers Fylely-Event, Fylely-Delivery and Fylely-Signature. It carries ids, names, statuses, dates and amounts, and nothing longer: read the rest through the API with the id.
Answer with any 2xx status within 5 seconds. Anything else, a redirect included, is tried again after each of these waits in turn: 1 minute, 5 minutes, 30 minutes, 2 hours, 12 hours and 24 hours. Then it is given up on. A retry can arrive a little after its wait. After 20 failures in a row the webhook is switched off and the owner is told. Answer a delivery to a webhook your tool set up with 410 and that webhook is removed. The same delivery can arrive more than once: its id does not change, so use it to ignore a repeat.
Events
matter.created A matter is opened
{
"id": "sample-matter.created-00000000-0000-4000-8000-000000000000",
"event": "matter.created",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"kind": "estate",
"name": "Sample: Estate of Jordan Reed",
"status": "open",
"case_number": null,
"opened_on": "2026-01-15",
"closed_on": null,
"created_at": "2026-01-15T17:00:00.000Z"
}
}matter.closed A matter is closed
{
"id": "sample-matter.closed-00000000-0000-4000-8000-000000000000",
"event": "matter.closed",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"kind": "estate",
"name": "Sample: Estate of Jordan Reed",
"status": "closed",
"case_number": "PR-2026-0142",
"opened_on": "2026-01-15",
"closed_on": "2026-09-30",
"created_at": "2026-01-15T17:00:00.000Z"
}
}intake.received An enquiry arrives from your intake form
{
"id": "sample-intake.received-00000000-0000-4000-8000-000000000000",
"event": "intake.received",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"name": "Sample: Grace Lin",
"matter_type": "Probate",
"status": "new",
"created_at": "2026-01-15T17:00:00.000Z"
}
}deadline.created A deadline is added
{
"id": "sample-deadline.created-00000000-0000-4000-8000-000000000000",
"event": "deadline.created",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"matter_id": "00000000-0000-4000-8000-000000000000",
"matter_kind": "estate",
"matter_name": "Sample: Estate of Jordan Reed",
"title": "Sample: file the inventory",
"category": "court",
"due_date": "2026-03-16",
"status": "upcoming",
"completed_at": null,
"created_at": "2026-01-15T17:00:00.000Z"
}
}deadline.completed A deadline is marked done
{
"id": "sample-deadline.completed-00000000-0000-4000-8000-000000000000",
"event": "deadline.completed",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"matter_id": "00000000-0000-4000-8000-000000000000",
"matter_kind": "estate",
"matter_name": "Sample: Estate of Jordan Reed",
"title": "Sample: file the inventory",
"category": "court",
"due_date": "2026-03-16",
"status": "done",
"completed_at": "2026-01-15T17:00:00.000Z",
"created_at": "2026-01-15T17:00:00.000Z"
}
}invoice.sent An invoice is sent
{
"id": "sample-invoice.sent-00000000-0000-4000-8000-000000000000",
"event": "invoice.sent",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"number": 1001,
"matter_id": "00000000-0000-4000-8000-000000000000",
"matter_kind": "estate",
"matter_name": "Sample: Estate of Jordan Reed",
"status": "sent",
"issue_date": "2026-01-15",
"due_date": "2026-02-14",
"sent_at": "2026-01-15T17:00:00.000Z",
"emailed": true
}
}payment.recorded A payment is recorded
{
"id": "sample-payment.recorded-00000000-0000-4000-8000-000000000000",
"event": "payment.recorded",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"invoice_id": "00000000-0000-4000-8000-000000000000",
"invoice_number": 1001,
"amount": 250,
"currency": "USD",
"method": "check",
"paid_on": "2026-01-15",
"created_at": "2026-01-15T17:00:00.000Z"
}
}signature.completed A document is signed by everyone
{
"id": "sample-signature.completed-00000000-0000-4000-8000-000000000000",
"event": "signature.completed",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"kind": "engagement",
"title": "Sample: engagement letter",
"status": "completed",
"estate_id": "00000000-0000-4000-8000-000000000000",
"guardianship_id": null,
"case_id": null,
"client_id": null,
"sent_at": "2026-01-15T17:00:00.000Z",
"completed_at": "2026-01-15T17:00:00.000Z"
}
}These are the made-up samples. GET /api/v1/hooks/samples?event=matter.created shows the same shape from the firm's own recent records where a key can read them.
Checking a signature
The Fylely-Signature header is t=<unix seconds>,v1=<hex>, where v1 is the HMAC-SHA256 of the time, a full stop and the body exactly as it arrived, keyed with the webhook's signing secret. The secret is shown once, to the owner, when they add the webhook. Refuse a delivery whose time is more than 5 minutes from your clock. In Node.js:
const crypto = require('node:crypto')
// rawBody: the body exactly as it arrived, before any JSON parsing.
// header: the Fylely-Signature header. secret: the signing secret shown when the webhook was made.
function isFromFylely(rawBody, header, secret) {
const parts = Object.fromEntries(header.split(',').map((part) => part.trim().split('=')))
const t = Number(parts.t)
if (!Number.isInteger(t) || Math.abs(Date.now() / 1000 - t) > 300) return false
const expected = crypto.createHmac('sha256', secret).update(t + '.' + rawBody).digest()
const given = Buffer.from(parts.v1 || '', 'hex')
return given.length === expected.length && crypto.timingSafeEqual(given, expected)
}A webhook a tool sets up for itself is signed too, but its secret is not handed back, so it cannot be checked this way.
Works with
Ways other tools connect to Fylely today, with what exists now. Each request is checked against the API whenever Fylely changes.
An answering service or a website form sends in an enquiry
For: A receptionist or answering service, a chat widget, a form builder, or a lead vendor whose leads the firm wants to look at first. Key: Can also create enquiries.
- The firm’s owner makes a key with “Can also create enquiries” ticked and gives it to you.
- Your server, or a Zapier or Make step, posts each enquiry. It lands in the firm’s Potential matters, the same list its own intake form fills, and the firm decides what it becomes.
- Send a name and an email or phone at least. Any field the endpoint does not take is listed back under ignored, not saved, so a misspelt name shows up while you set it up.
Send in one enquiry
curl -X POST https://fylely.com/api/v1/enquiries \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"name": "Grace Lin",
"email": "grace@example.com",
"phone": "555-0142",
"matter_type": "Probate",
"description": "Caller says her father died last month and she is named executor. Best time to call: mornings.",
"source_page": "https://yourfirm.com/contact",
"utm_source": "answering-service"
}'Call it from a server, never from a web page’s own JavaScript, where every visitor could read the key.
Post new matters and enquiries to Slack or Microsoft Teams
For: A firm that wants a message in a channel when a matter is opened or an enquiry arrives. Key: Any key.
- In Zapier, Make or n8n, start a flow with its catch-a-webhook trigger (in Zapier: Webhooks by Zapier, then Catch Hook) and copy the https address it gives you. A Microsoft Teams workflow that starts when it receives a webhook request gives you an address too.
- The firm’s owner adds that address as a webhook under Settings → Connections → Webhooks in Fylely and ticks “A matter is opened” and “An enquiry arrives from your intake form”. Or a tool whose key has “Can also set up its own webhooks” adds it with the request below, one event per address.
- In the flow, add a step that posts to Slack or Teams, built from the fields under data, such as data.name and data.matter_type.
Or let the tool set up its own webhook (needs “Can also set up its own webhooks”)
curl -X POST https://fylely.com/api/v1/hooks \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-d '{
"target_url": "https://hooks.zapier.com/hooks/catch/123456/abcde12/",
"event": "intake.received"
}'What Fylely posts for matter.created
{
"id": "sample-matter.created-00000000-0000-4000-8000-000000000000",
"event": "matter.created",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"kind": "estate",
"name": "Sample: Estate of Jordan Reed",
"status": "open",
"case_number": null,
"opened_on": "2026-01-15",
"closed_on": null,
"created_at": "2026-01-15T17:00:00.000Z"
}
}What Fylely posts for intake.received
{
"id": "sample-intake.received-00000000-0000-4000-8000-000000000000",
"event": "intake.received",
"created_at": "2026-01-15T17:00:00.000Z",
"data": {
"id": "00000000-0000-4000-8000-000000000000",
"name": "Sample: Grace Lin",
"matter_type": "Probate",
"status": "new",
"created_at": "2026-01-15T17:00:00.000Z"
}
}Fylely has no Slack or Teams app and does not post to either itself. It posts the JSON below to an https address, and Slack’s own incoming-webhook addresses expect Slack’s message format, so put a flow in between to turn it into a message.
Send time from another tool
For: A timer, a phone system or a calendar tool that records time worked. Key: Allow changes.
- The firm’s owner makes a key and chooses “Allow changes” on it. The key logs time as the person who made it, at their usual rate unless one is sent.
- Find the matter’s id once: GET /api/v1/matters lists each matter with its id, name and file_number.
- Post the time in whole minutes, never hours. Send an Idempotency-Key, such as the entry’s own id in your tool, so a retry never logs it twice.
Log 1h 30m on a matter
curl -X POST https://fylely.com/api/v1/matters/3f0c9a52-8d1e-4b7a-9c2f-6e5d4a3b2c1d/time-entries \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: timer-entry-48213" \
-d '{
"entry_date": "2026-12-01",
"minutes": 90,
"description": "Call with the client about the inventory",
"billable": true
}'Copy matters and deadlines into a spreadsheet every night
For: A firm’s IT person, with Make, n8n or a script, and Google Sheets or Excel. Key: Any key.
- A key that only reads is enough.
- Schedule a flow to run each night with an HTTP request step and the key in an Authorization header. Or import the OpenAPI file into a tool that reads it, to get each request ready to send.
- For each item in data, add or update a row, matched on id.
- If next_cursor is not null, ask again with cursor set to it, until it is null.
Upcoming deadlines from a date
curl "https://fylely.com/api/v1/deadlines?status=upcoming&due_from=2026-12-01&limit=200" \ -H "Authorization: Bearer fy_live_…"
Matters changed since yesterday
curl "https://fylely.com/api/v1/matters?updated_since=2026-11-30&limit=200" \ -H "Authorization: Bearer fy_live_…"
A lead vendor adds a contact and opens a matter
For: A lead vendor or referral network the firm trusts to open matters directly. Key: Allow changes.
- The firm’s owner makes a key and chooses “Allow changes” on it. If the firm would rather look at each lead first, send an enquiry instead (the first recipe).
- Post the contact. The answer’s data.id is the contact’s id.
- Post the matter with that id as client_id. It opens with the starter checklist and sends the matter.created webhook. The firm’s automatic file numbers are not applied to it: send file_number if the firm wants one.
- Send an Idempotency-Key with each, from the lead’s own id, so a retry never makes a second contact or matter.
1. The contact
curl -X POST https://fylely.com/api/v1/contacts \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: leadco-90211-contact" \
-d '{
"name": "Grace Lin",
"email": "grace@example.com",
"phone": "555-0142",
"category": "potential_client",
"referral_source": "LeadCo"
}'2. The matter, with the contact’s id
curl -X POST https://fylely.com/api/v1/matters \
-H "Authorization: Bearer fy_live_…" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: leadco-90211-matter" \
-d '{
"kind": "case",
"name": "Lin – car accident",
"type": "Personal injury",
"client_id": "5b8e2f4a-1c3d-4e5f-8a9b-0c1d2e3f4a5b",
"state": "WA",
"county": "King"
}'OpenAPI file
The whole API, events included, as an OpenAPI 3.1 file. It needs no key. Postman and other tools that read OpenAPI can import it, to get every request ready to send with your key.
Claude and other assistants
Fylely is also an MCP server, for an AI assistant the firm already uses. Its address, with nothing after it:
https://fylely.com/api/mcp
One JSON-RPC message or batch per POST, one JSON answer, no sessions and no stream. The assistant signs in and the firm's owner allows it, or it is given a key in an Authorization header. It reads what a key reads, through these tools: firm, list_matters, get_matter, list_deadlines, list_contacts, list_invoices. It cannot change anything. Each call counts against the 120 requests a minute. So far it has been tried with Claude only.
If the owner turns on Allow suggestions for the connection, it can also suggest a change (suggest_task, suggest_deadline, suggest_hearing, suggest_time_entry, suggest_note, suggest_invoice, suggest_documents). Each suggestion waits in Fylely for someone at the firm to add or decline it, and nothing changes until they do.
Zapier
A Fylely app for Zapier is built, but it is not listed in Zapier, and will not be until Zapier approves it. Today firms connect through Zapier's own webhook steps, which work now:
- To start a Zap when something happens in Fylely: Webhooks by Zapier, then Catch Hook, and add its address as a webhook in Fylely.
- To send an enquiry in: a Webhooks by Zapier POST step to /api/v1/enquiries with the key in an Authorization header, as in the first recipe.
What it does not do
- Read notes, messages, the contents of documents, the trust ledger, identity checks or the lines of an invoice. An enquiry cannot be read back either.
- Delete anything. A key can remove only a webhook it set up itself.
- Post to Slack or Microsoft Teams itself. There is no Slack or Teams app: use a webhook and a flow, as above.
- Let a key read or change another firm's records. The firm is always the key's, whatever a body says.
Building something and stuck? Email help@fylely.com.