Public APIs in Eve

Last updated: September 29, 2026

Overview

Eve's public APIs are REST endpoints a firm's technical team can build against. They exist for firms running proprietary software, a legacy case management system, or a workflow none of the standard integrations covers.

Access and the full technical documentation come from a Customer Success Manager rather than being available by default.

What the APIs Cover

  • Creating, updating, and managing matters

  • Uploading and organizing documents into matters

  • Retrieving matter and document information

  • Deleting matters and documents

Requests and responses are JSON. Authentication is a bearer token sent with every request.

Two Ways to Keep Data Current

  • Push. The firm's system sends data to Eve the moment something changes in it. Closest to real time, and the integration the firm's own system controls.

  • Pull. Data is retrieved on a schedule the firm sets. Simpler to build, at the cost of a delay between a change and Eve seeing it.

Either way, the firm's system stays the record of truth and Eve holds a copy.

Getting Access

A Customer Success Manager provides API access and the technical documentation case by case. That documentation covers endpoint specifications, authentication, supported file types and size limits, error handling, and worked integration flows.

For large enterprise customers with complex needs, Eve's engineering team may build a custom integration instead. Those are assessed on contract size and volume, technical complexity, and fit with the product roadmap, so it is a conversation rather than a request form.

What the APIs Do Not Do

Key Terms

  • Endpoint: A specific URL in the API performing one function, such as creating a matter.

  • Bearer token: The credential included with every request to authorize it.

  • Push synchronization: The firm's system sending data to Eve as changes happen.

  • Pull synchronization: Eve retrieving data from the firm's system on a schedule.