Endpoint overview
GET/api/v1/meReturn the account or firm the token belongs to.GET/api/v1/casesList cases scoped to the token. A user token returns that user's cases; a firm token returns the firm's matters. Paginated via limit and offset.GET/api/v1/documentsList documents scoped to the token.GET/api/v1/signing-requestsList signing requests scoped to the token.
That is the whole published surface today. Everything is read-only; there is no endpoint that creates or changes data.
Authentication
Every request carries a Bearer token. Tokens begin adv_ and are tied to your account or your firm. Sample request:
curl https://advottic.com/api/v1/cases \ -H "Authorization: Bearer adv_..." \ -H "Accept: application/json"
A token missing the scope an endpoint needs is refused with 403. Tokens are revocable at any time from the same settings panel that issued them.
Webhooks
Firm owners and admins add webhook endpoints in Counsel settings. Each endpoint chooses which of three events it receives, and the signing secret is shown once when the endpoint is created.
request.createdA request is created.request.updatedA request changes status, owner, dates, or linked matter.case.updatedA firm matter changes status, owner, title, hearing, or close date.
Payloads carry ids, statuses, dates, and the names of the fields that changed. They never carry names, emails, summaries, or document contents; call the REST API with your own token for those. Each delivery has three headers, in the Standard Webhooks format:
webhook-id: the event id, the same on every retry, for ignoring duplicates.webhook-timestamp: Unix seconds when the attempt was sent.webhook-signature:v1,<base64>, the HMAC-SHA256 ofid.timestamp.bodykeyed with the base64-decoded part of yourwhsec_secret.
To verify, compute the signature over the raw request body before parsing it, compare it to the header in constant time, and reject a webhook-timestamp more than five minutes from your clock, so a captured request cannot be replayed. The Standard Webhooks libraries do all three.
Answer with any 2xx status within 10 seconds. Anything else, including a timeout or a redirect (redirects are not followed), counts as a failure. A failed event is tried up to 9 times in total, waiting 30 seconds, 2 minutes, 10 minutes, 1 hour, 3 hours, 6 hours, 12 hours, and 24 hours between attempts. An endpoint that fails continuously for 24 hours, with at least 10 failed attempts, is disabled, and firm owners and admins are told.
Partner intake ticket webhooks
Partner intake tickets emit their own webhooks, configured per firm. Payloads are signed with HMAC-SHA256 using your webhook secret; verify the X-Advottic-Signature header before processing. The event name arrives in X-Advottic-Event.
- ticket.created
- ticket.employee_replied
- ticket.legal_replied
- ticket.status_changed
- ticket.reminder
Delivery is a single attempt with a 10-second timeout and is not retried. Treat a webhook as a prompt to refresh, and poll if you need certainty.
Frequently asked
Is the Advottic API publicly available?
Yes. Mint a token yourself from API tokens in your profile settings. There is no waiting list and no application.How is auth handled?
Every request carries a Bearer token. Tokens carry one or more of three scopes: read, write, and admin. The endpoints published today all require read. Tokens can be given an expiry and can be revoked at any time from the same settings panel.What about webhooks?
There are two kinds, both configured per firm rather than through the API. Firm event webhooks send request.created, request.updated, and case.updated, are retried, and are added by firm owners and admins in Counsel settings. Partner intake ticket webhooks send five ticket events in a single attempt that is not retried. Both are described in the Webhooks section below.Is there an OpenAPI document?
Yes. The OpenAPI 3.1 description of the endpoints and the firm event webhooks is at /api/openapi.json. It needs no token.Are there SDKs?
No. There is no published SDK. The endpoints are plain REST over HTTPS returning JSON, so any HTTP client will do, and the OpenAPI document can feed a client generator.
Ready to build?
Mint a token from your profile settings. If you need something the endpoints above do not cover, write to partnerships@advottic.com and tell us what you're building.


