API Access
Understand the basic requirements for accessing and using the Monolith REST API.
The Monolith API provides programmatic access to supported Monolith resources through a REST API over HTTPS.
Organizations can use the API to integrate Monolith with external systems, automate supported workflows, retrieve structured data, or build custom reporting and operational processes.
Before You Begin
To make requests to the Monolith API, you will need:
Access to the Monolith tenant you want to work with
A valid Monolith API key
The API endpoint for your Monolith deployment or cloud region
Appropriate permissions for the resources and actions you want to use
API keys are created and managed from Settings > API in Monolith.
Treat API keys as sensitive credentials. Do not share them publicly or store them directly in source code or other locations where they may be exposed.
API Base URL
API requests are sent to the /api/v1 path for your Monolith environment.
Cloud-hosted customers should use the endpoint associated with their Monolith region.
On-premises customers should use the API address configured for their own Monolith deployment.
See API Endpoints for endpoint guidance.
Authentication
Authenticated API requests require a valid Monolith API key in the following HTTP request header:
X-API-KEY
See Authentication for an example request and additional guidance.
Test Your API Access
The Info API provides a simple way to confirm that your endpoint and API key are working correctly.
A successful request to:
GET /api/v1/info
returns basic information about the authenticated user and Monolith tenant.
See Info API for request and response examples.
API Resources
The Monolith API includes endpoints for supported resources such as:
Cases
Evidence
Acquisitions
Locations
Chain of Custody
Clients
Contacts
Inquiries
Tasks
Storage
Additional resources may be added as the API expands.
Each API section documents the supported endpoints, request parameters, and response structure for that resource.
Webhooks
Monolith also supports Webhooks for workflows where an external system should be notified when supported Monolith resources are created, updated, or deleted.
API keys and Webhooks are managed from Settings > API.
Use the API when another system needs to request or work with Monolith data.
Use Webhooks when another system needs to react to activity occurring in Monolith.
Related Documentation
Last updated
Was this helpful?