Advottic
Sign in

Developers

Build on the Advottic API.

Read-only REST endpoints for cases, documents, and signing requests, plus outbound webhooks for partner intake tickets. Mint a token from your profile settings and start; there is no waiting list. Questions go to partnerships@advottic.com.

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

Partner intake tickets emit 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?
    Webhooks are for partner intake tickets, and they are configured per firm rather than through the API. Five events are sent: ticket.created, ticket.employee_replied, ticket.legal_replied, ticket.status_changed, and ticket.reminder. Delivery is a single attempt with a 10-second timeout and is not retried, so treat it as a hint to refresh rather than a guaranteed feed, and poll if you need certainty.
  • Are there SDKs?
    No. There is no published SDK and no OpenAPI document. The endpoints are plain REST over HTTPS returning JSON, so any HTTP client will do.

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.

Create a tokenRead security overview