Back to Platform API Guides
LegalReady to build

Neos API

Neos (by Assembly Software) has no public developer API, leaving matter management, contact, time, document, and billing workflows completely inaccessible programmatically. Integuru can generate a production-ready HTTP API: chat with us to get started.

Overview

Neos is a cloud-based legal case management platform developed by Assembly Software, built as the modern successor to Needles, one of the most widely installed case management systems for plaintiff-side personal injury firms. Neos runs on Microsoft Azure infrastructure and focuses on AI-assisted workflows including medical record extraction, demand letter drafting, and statute-of-limitations tracking, primarily serving personal injury and mass tort practices.

Neos exposes no public developer API. There is no developer portal, no documented API reference, and no partner program for programmatic access. Every interaction with matter records, contacts, time entries, documents, and billing data must go through the Neos web interface manually. For development teams building legaltech tools, AI assistants, or automation workflows on top of Neos, this is a complete block: the data exists in the system, but there is no legitimate path to it outside the browser.

The pattern Integuru solves. Platforms like Neos invest in their web application as the primary product surface. The HTTP requests the web application sends internally are well-structured and stable: they are the same requests the product engineering team builds and tests. Integuru maps these requests, manages authentication, and exposes them as a clean, documented HTTP API your team calls directly.

This is Integuru's core capability: generating production-ready APIs for platforms that never built a public one. Neos is among the most-requested legal platforms in this category.


Why Teams Need This Integration

Neos is built for high-volume personal injury and mass tort practices that move large quantities of medical records, demand packages, and case documents through their workflow daily. The absence of any API creates bottlenecks at every stage of that workflow.

AI medical record extraction and ingestion. Neos includes its own AI medical record extraction feature (NeosAI), but external AI vendors (tools that specialize in medical chronologies, record review, or demand letter generation) need write access to push extracted data back into Neos as structured matter fields. Without an API, these tools stop at the extraction step and require a paralegal to manually enter the results.

Statute-of-limitations and deadline tracking. The list_tasks action exposes Neos's deadline tracking, including statute-of-limitations reminders, to external calendaring and docketing systems. Firms that run a separate docketing tool alongside Neos currently maintain these deadlines in two places, a reconciliation problem that creates malpractice exposure. A live integration eliminates the duplication.

Settlement and lien management platforms. Third-party settlement management and medical lien tracking tools need read access to the billing summary and matter status to match settlements against outstanding balances. get_billing_summary covers this, including the lien tracking data that personal injury practices require alongside standard billing fields.

Mass document intake. Personal injury firms receive medical records, deposition transcripts, and third-party correspondence that must be filed into the correct matter. The upload_document action routes incoming documents to the correct Neos matter record automatically, replacing the manual triage that paralegals currently perform for every incoming file.


Legal Workflows This Integration Covers

The ten planned actions cover the full matter lifecycle for a personal injury or mass tort practice:

  • Matter management: list_matters and get_matter_detail surface active caseload data (including Neos's AI-extracted medical record fields and custom form data) to downstream tools in real time.
  • Client and contact records: list_contacts and create_contact enable automated intake, conflict checking, and referral source tracking.
  • Time capture: list_time_entries and create_time_entry connect external time capture tools and AI assistants to Neos's time log, closing the loop on billable time without attorney data entry.
  • Document handling: list_documents and upload_document automate the intake and filing of medical records, court documents, and correspondence into the correct matter.
  • Deadline tracking: list_tasks feeds external docketing and calendaring systems with live statute-of-limitations and task deadlines from Neos.
  • Billing and lien data: get_billing_summary provides settlement management, lien tracking, and finance tools with structured billing data per matter.

Adjacent Integrations

Personal injury and mass tort practices frequently work alongside commercial real estate attorneys on property disputes and premises liability matters. The Dealground integration provides programmatic access to commercial real estate listing and deal data from the same Integuru account, supporting practices that span litigation and real estate transactional work. The Wefunder integration illustrates Integuru's capability with authentication-gated platforms that use complex session flows, the same technical pattern that Neos and court-filing portals represent.

What Neos currently offers publicly

No API

Neos (by Assembly Software, formerly Needles) does not expose a public developer API of any kind. The platform has no documented API, no developer portal, and no partner program for programmatic access. Teams that need to read or write matter, contact, time entry, document, or billing data must do so manually through the Neos web interface.

Neos official site

Actions Integuru could expose

list_matters

Return a paginated list of matters with status, matter type, assigned attorney, and client information

get_matter_detail

Retrieve the complete record for a single matter including custom form fields, assigned team, and linked contacts

list_contacts

List client and contact records with type, email, phone, and linked matter associations

create_contact

Create a new client or contact record associated with one or more matters

list_time_entries

Return time entries for a matter or date range with activity type, duration, and billable status

create_time_entry

Log a time entry against a specific matter and user

list_documents

List documents attached to a matter with file name, document type, and upload date

upload_document

Upload a document (medical records, deposition transcripts, court filings) to a specific matter

list_tasks

Return tasks and statute-of-limitations reminders linked to a matter with due dates and completion status

get_billing_summary

Retrieve billing data for a matter including invoiced amounts, outstanding balances, and lien tracking

...many more

These actions reflect what Integuru would generate based on the workflows Neos exposes through its web interface. Final scope is confirmed when the integration is built.

Integuru already supports these platforms in the same vertical

These are live, production-ready integrations (not requests). They show that Integuru has working knowledge of this space.

Frequently Asked Questions

Ready to integrate Neos?

Integuru builds a production-ready API using direct HTTP requests. 24/7 maintenance included on production plans.

npm install -g integuru