Endpoint
PUT /equipments/{equipmentId}/manual-operating-hoursA single upsert call for both create and update — you never need to know whether a value already exists. The operation is idempotent: sending the same request twice leaves the same result.
Authentication
Required: Authorization header with valid token
Path Parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| equipmentId | uuid | Yes | The equipment to set the value for | 8f14e45f-ceea-467a-9f4d-1a2b3c4d5e6f |
Request Body
{
"minutes": 75030,
"updatedBy": "user-uuid"
}Request Field Descriptions:
| Field | Type | Required | Description |
|---|---|---|---|
| minutes | number | Yes | The value in minutes. Range 0 – 60000000, max 2 decimal places. Must be a JSON number — a string fails validation |
| updatedBy | string | No | An author reference (user ID). Omitting it overwrites the stored author with null |
Response
Success (200)
{
"equipmentId": "8f14e45f-ceea-467a-9f4d-1a2b3c4d5e6f",
"minutes": 75030,
"updatedBy": "user-uuid",
"updatedAt": "2026-08-10T09:00:00.000Z"
}A body that fails validation (minutes negative, over the max, more than 2 decimals, or not a number) returns 400. If the equipment is not known to the platform yet, the request fails with 404 EQUIPMENT_NOT_FOUND.
Response Field Descriptions:
See ManualOperatingHours Schema
Error
See Error Schema documentation
Example Usage
Bash
curl -X PUT "https://integration-api.ram.syniotec.com/master-data/v1/equipment-telemetry/equipments/8f14e45f-ceea-467a-9f4d-1a2b3c4d5e6f/manual-operating-hours" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"minutes":75030,"updatedBy":"user-uuid"}'