What authentication does the Lexamica API use?

Lexamica uses OAuth 2.0 authorization code flow with granular read and write scopes and supports IP filtering on the client. The authorization endpoint is https://api.lexamica.com/oauth/authorize and tokens are issued at https://api.lexamica.com/oauth/token. Through Jentic the OAuth tokens are stored encrypted in your Jentic One instance.

Can I open and update cases with the Lexamica API?

Yes. POST /cases creates a new matter, GET /cases/{id} retrieves it, and PUT /cases/{id} updates fields such as status or assigned attorney. GET /cases lists matters for the authenticated firm so an integration can paginate the active book.

What are the rate limits for the Lexamica API?

Lexamica does not publish exact rate-limit numbers in the public spec. Treat the 9 endpoints as standard OAuth-secured REST: paginate /cases and /documents listings, retry idempotent reads on 429 with backoff, and avoid concurrent writes on the same case_id.

How do I create a new case through Jentic?

Run 'pip install jentic', search for 'open a new legal case', and Jentic returns POST /cases with its schema. Load the operation, supply the matter type, client, and metadata, and execute. Jentic injects the OAuth bearer token automatically and refreshes it as needed.

Can I limit what my agent is allowed to do with the Lexamica API?

Yes. Because Jentic One is self-hosted, your own rules decide which Lexamica operations and which OAuth scopes your agent may use. Since Lexamica carries the case id in the URL path (/cases/{id}) and offers separate read and write scopes, you can pin an agent to reading and updating a specific case and its documents while leaving out others. If you do not grant the referral operations, POST /referrals stays off limits, so the agent cannot capture new referrals unless you explicitly add that call.