POST /api/v1/evidence
Use this API endpoint to create evidence items within Monolith.
Either case_id, case_uuid, or case_number is required.
If evidence_number is not provided, Monolith will automatically generate a value.
Request Body
case_id
number
Unique ID of a case to link evidence.
case_uuid
string
Unique ID of a case to link evidence.
case_number
string
Case number to link evidence.
evidence_number
string
Evidence number of the evidence being created.
item_name
string
Name of the evidence item.
type
string
The type of evidence item: (Smartphone, Server, Email, etc...)
location_id
number
Sets the location of the evidence item at creation. Location ID can be retreived from locations API.
provider
string
Service provider or manufacturer of evidence.
model_number
string
Evidence model number.
unique_id
string
Unique ID associated with the device - usually a serial number or account name.
size
number
Capacity of the evidence
size_unit
string
Unit of capacity: KB, MB, GB, TB, PB
description
string
Description of the item
custom_fields
array
Array of custom field objects
To create custom fields for your evidence in an API request, you must include a custom_fields value that consists of an array of JSON objects in the following form:
field_id
integer
Unique id of the custom field
value
string
This is the value to be set for the custom field
The field_id is the numeric identifier for the custom field you are setting a value for.
GET /api/v1/evidence/:uuid?
Retrieves a list of evidence items. Calling with no parameters returns a paginated list of all evidence items in your Monolith database. Use the uuid query param to get details for one item or use the case_uuid param to get a list of evidence items for one Monolith case.
Query Params
uuid
string
Monolith unique identifier for evidence item.
evidence_id
number
Monolith unique identifier for evidence item.
case_uuid
string
Monolith unique identifier for a Monolith case.
case_id
number
Monolith unique identifier for a Monolith case.
user_id
number
Unique identifier for a user.
location_id
number
Unique identifier for an evidence location.
include_coc
boolean
Attaches chain of custody records to each evidence item as an array.
created_on
ISO Date
Date that the evidence was entered into Monolith.
created_before
ISO Date
Evidence items that were created before this Date.
created_after
ISO Date
Evidence items that were created after this Date.
updated_on
ISO Date
Evidence items that were created on this Date.
updated_before
ISO Date
Evidence items that were created before this Date.
updated_after
ISO Date
Evidence items that were created after this Date.
intake_date
ISO Date
The initial intake date of the evidence.
intake_before
ISO Date
Evidence items that were initially received before this Date.
intake_after
ISO Date
Evidence items that were initially received after this Date.
POST /api/v1/evidence/migrate
Use this API endpoint to migrated chosen evidence items from one case to another.
Request Body
uuid*
array
Array of evidence item UUIDs that are to be migrated. REQUIRED
case_uuid*
string
The UUID of the case that the evidence items will be migrated to.
REQUIRED
PUT /api/v1/evidence/:uuid?
Use this API endpoint to update evidence items within Monolith.
uuid is required.
Request Body
uuid
string
Unique ID of the evidence to be updated. REQUIRED
evidence_number
string
Evidence number of the evidence being created.
item_name
string
Name of the evidence item.
type
string
The type of evidence item: (Smartphone, Server, Email, etc...)
location_id
number
Changes the location of the evidence item. Location ID can be retrieved from the Locations API.
provider
string
Service provider or manufacturer of evidence.
model_number
string
Evidence model number.
unique_id
string
Unique ID associated with the device - usually a serial number or account name.
size
number
Capacity of the evidence
size_unit
string
Unit of capacity: KB, MB, GB, TB, PB
description
string
Description of the item