Professional API: Changelog

Additive, and no action is required. Existing endpoints keep receiving exactly the events they were subscribed to.

• referral.will_started: fires when someone who arrived through your white-label partner page starts a will
• referral.will_completed: fires when a will started through your partner page is signed and completed

Both carry the event slug, a referral identifier and its status. They never include the person’s name, contact details or anything from the will.

Additive. The matter collection gained a brief endpoint at /api/v1/pro/ext/matters/{id}/brief/, so drafting software can pull a matter’s brief without a person copying it out by hand.

• The client’s consent for that matter is re-read on every call and never cached, so withdrawing consent takes effect on the next request
• Every fetch is written to the matter’s disclosure log, recording the key prefix used and never the key itself
• The endpoint carries its own hourly cap, separate from your plan allowance and shared with the signed bundle download
• Responses are marked no-store, so intermediaries do not retain a copy

Additive, and no action is required. Existing endpoints keep receiving exactly the events they were subscribed to.

• appointment.rescheduled: fires when an existing appointment moves, so a calendar integration no longer has to infer a move from a cancellation followed by a creation
• message.received: fires when a new message arrives in a conversation

Both carry the same three-key payload as the original events: the event slug, an identifier, and a status.

The first release of the Professional API, a read-only surface under /api/v1/pro/ext/.

• Profile: me/, your professional profile
• Appointments: list and detail
• Approaches: list and detail
• Matters: list only
• Engagement letters: list and detail
• Authentication: personal API keys sent as Authorization: Bearer pk_…, issued with the pro:read scope
• Rate limiting: plan-driven, on a one-hour sliding window; the current figures for each plan are under Rate Limits below
• Webhooks: appointment.created, appointment.cancelled, engagement_letter.signed and approach.received, signed with HMAC-SHA256

Limits are counted on a sliding window. When you go over one, the API answers 429 Too Many Requests with a Retry-After header telling you how long to wait.

These figures come from the limits the API enforces, also served as JSON at /api/v1/portfolio/rate-limits/.

The Professional API uses URL versioning: every endpoint is prefixed with /api/v1/pro/ext/. The same rules apply to every external surface, including the tools our MCP server offers AI agents.

• This page: the record of every change to the Professional API, worth a look once a month
• The schema: the machine-readable description at /api/v1/pro/ext/schema/ changes with the surface, so you can diff it between releases
• Webhooks: they tell you about activity in your practice, not about API versions. Deprecation notices are never delivered by webhook
• Contact support: get in touch if you need help migrating