Getting Started

The Neos Partner API is a REST API that lets third-party integrators build on top of Neos, a legal case management platform used by law firms. Through the API, integrators can create and manage cases, intakes, contacts, documents, calendar events, webhooks, and more — enabling workflows like intake capture, document sync, and bi-directional data exchange with external systems.

Access to the API is granted through an onboarding process managed by Assembly Software.

Onboarding Steps

Create an Account — Register in the Neos Developer Portal. You will be asked to agree to our API agreement during signup.
Submit an Integration Request — Share your goals, target firms, and integration requirements with Assembly Software.
Sign the API Agreement — Required before staging access is granted.
Subscribe to an API — Once approved, subscribe to an API product to receive your Subscription Key and access the documentation.

Integration Phases

Phase	Description
Discovery	Initial meeting to align on integration goals and requirements.
Approval	Internal review and approval of your integration request.
Development	Access to a shared partner environment for building and testing.
API Review	Assembly Software reviews your API calls and error handling. Required before production access.
Go-Live	Production credentials issued after API Review approval.

Any new features or updates to an existing integration must also go through API Review before being deployed to production.

Key Standards

Before you start building, be aware of the following non-negotiable requirements:

Test only in the staging partner environment — never in production.
Implement duplicate checks before creating cases, intakes, or contacts.
Use POST /v1/advancedsearch/search/results for searching — do not use GET-based search for bulk queries.
Use PATCH for partial updates. Only use PUT when replacing a full object, and always retrieve the current state first.
Implement retry logic with exponential backoff and log all failures.
Protect data with encryption in transit and at rest, and use role-based access controls.

What's Next

Authentication — How to create an integration user, activate your integration, and obtain a Bearer Token.
Neos API Guidelines & Best Practices — Full onboarding expectations, credential details, and integration standards.
Frequently Asked Questions — Common error codes and troubleshooting.

Support

Submit a Neos Integration Support Request with request samples, API details, error logs, and steps to reproduce.