Equipment
Manage equipment, including registration, update, deletion, and advanced search.
Equipment can be linked to offices, projects, and categories, and supports metadata and filtering.
- Version
- 2.0.0
- OpenAPI version
- 3.0.0
Operations
Section titled “Operations” POST /v2/equipment/index
Returns a paginated and filterable list of equipment.
Use POST to allow complex filters via JSON payload.
Request Body
Section titled “Request Body ”Parameters for searching equipment
object
object
The field of the model to sort the list for, use a minus to revert the sort. Es -name is to require the sort in reverse order
The field establishes whether to also include historized elements that are no longer active in the results. If you leave this parameter empty the response returns only actual entries.
Example
{ "filter": { "name": "Excavator", "office_id": "off-1" }, "per-page": 10, "page": 1, "sort": "name"}
Responses
Section titled “ Responses ”List of equipment
object
Example
{ "office_equipment_id": "oe-1", "office_id": "off-1", "equipment_id": "eq-1", "code": "EQ-001", "name": "Excavator", "description": "Heavy duty excavator", "project_id": "proj-1", "serial": "SN123456", "vendor": "Caterpillar", "model": "CAT320"}
Headers
Section titled “Headers ”Current page
Total number of pages
Number of items per page
Total number of items
create
Section titled “create” POST /v2/equipment/create
Create a new equipment entry by providing the required details.
Request Body required
Section titled “Request Body required ”Equipment object to be created
object
Example
{ "office_id": "off-1", "code": "EQ-002", "name": "Bulldozer", "description": "Tracked bulldozer", "project_id": "proj-1", "serial": "SN654321", "vendor": "Komatsu", "model": "D65EX"}
Responses
Section titled “ Responses ”Equipment created successfully
object
Example
{ "office_equipment_id": "oe-2", "office_id": "off-1", "equipment_id": "eq-2", "code": "EQ-002", "name": "Bulldozer", "description": "Tracked bulldozer", "project_id": "proj-1", "serial": "SN654321", "vendor": "Komatsu", "model": "D65EX"}
GET /v2/equipment/view/{id}
Retrieve an equipment entry by its unique ID.
Path Parameters
Section titled “Path Parameters ”ID of the equipment to retrieve
Responses
Section titled “ Responses ”Equipment found
object
Example
{ "office_equipment_id": "oe-1", "office_id": "off-1", "equipment_id": "eq-1", "code": "EQ-001", "name": "Excavator", "description": "Heavy duty excavator", "project_id": "proj-1", "serial": "SN123456", "vendor": "Caterpillar", "model": "CAT320"}
Equipment not found
delete
Section titled “delete” DELETE /v2/equipment/delete/{id}
Delete an equipment entry by its unique ID.
If force=true, all related entities will also be deleted.
Path Parameters
Section titled “Path Parameters ”ID of the equipment to delete
Query Parameters
Section titled “Query Parameters ”Force the deletion of the entity and all related entities
Responses
Section titled “ Responses ”Equipment deleted successfully
If force=false, the operation is interrupted and the list of connected entities that will be deleted in case of confirmation (force=true) is returned
update
Section titled “update” PUT /v2/equipment/update/{id}
Update an existing equipment entry by its unique ID.
Path Parameters
Section titled “Path Parameters ”ID of the equipment to update
Request Body required
Section titled “Request Body required ”Equipment object with updated data
object
Example
{ "name": "Updated Excavator", "description": "Updated description"}
Responses
Section titled “ Responses ”Equipment updated successfully
object
Example
{ "office_equipment_id": "oe-1", "name": "Updated Excavator", "description": "Updated description"}
Equipment not found