Time Slot Control provides a programming interface (API) for integration with external systems - ERP, WMS, BI tools and camera systems. All communication takes place exclusively over HTTPS.
The Time Slot Control API offers two distinct ways to communicate and integrate:
The primary interface for ERP integration. Supports both reading and writing data - working with the Company, Order and OrderRow entities. The OData specification is natively supported by market leaders - Microsoft, SAP, CA Technologies, Citrix Systems, IBM, Red Hat and others.
The
Reservationentity is also exposed via OData, but only for reading and for updating the note / custom fields (ExtCustomFieldVarchar1-15,ExtCustomFieldBit1-3) through the boundPatchaction. Creating a reservation or writing fields such as carrier, vehicle type, driver or license plates is not supported over OData - use the REST v3 endpoints below instead.
More information: https://www.odata.org/
A specific interface for three purposes:
Endpoint: POST /v3/{tenant}/Reservations
The request body is a direct JSON object (no wrapper). Minimum required fields:
ResourceId
Guid
Start
DateTimeOffset
2026-04-15T08:00:00Z)UnitId
Guid
NumberOfUnits
int
Optional fields for carrier / vehicle / driver information:
CarrierId
Guid
Carrier
string
CarrierDriverFullName
string
VehicleTypeId
Guid
VehicleNumberPlate
string
TrailerNumberPlate
string
Example request (cURL with Basic auth):
curl -X POST "https://api.tscsandbox.com/v3/{tenant}/Reservations" \
-H "Content-Type: application/json" \
-u "api@yourdomain.com:password" \
-d '{
"ResourceId": "<resource-guid>",
"Start": "2026-04-15T08:00:00Z",
"UnitId": "<unit-guid>",
"NumberOfUnits": 10,
"CarrierId": "<carrier-guid>",
"CarrierDriverFullName": "John Smith",
"VehicleTypeId": "<vehicletype-guid>",
"VehicleNumberPlate": "1AB2345",
"TrailerNumberPlate": "1CD6789"
}'
Endpoint: PUT /v3/{tenant}/Reservations/{id}
Unlike the OData Patch action (limited to the note and custom fields), this endpoint accepts the full set of reservation fields listed above, including carrier, driver, vehicle type and licence plates.
curl -X PUT "https://api.tscsandbox.com/v3/{tenant}/Reservations/<reservation-guid>" \
-H "Content-Type: application/json" \
-u "api@yourdomain.com:password" \
-d '{
"CarrierId": "<carrier-guid>",
"CarrierDriverFullName": "John Smith",
"VehicleTypeId": "<vehicletype-guid>",
"VehicleNumberPlate": "1AB2345",
"TrailerNumberPlate": "1CD6789"
}'
Converting Order records into a reservation (the equivalent of manually dragging orders from the order cart onto the schedule in the UI) is not automatic after creating orders via OData - it must be triggered explicitly, either in the UI or via this endpoint:
Endpoint: POST /v3/{tenant}/Reservations/CreateFromOrders
OrderIds
Guid[]
ResourceId
Guid
Date
DateTimeOffset
CarrierId, VehicleTypeId, VehicleNumberPlate and the other carrier/vehicle fields from the create endpoint can be supplied here as well. On success, the referenced orders are flagged as ExistsInReservation = true and the new reservation appears on the schedule at the given resource and time.
The full, always up-to-date list of parameters for all three endpoints is available in the interactive API Reference (Scalar UI) - see the OData page for details.
Time Slot Control offers two environments - for both the web application and the API:
The sandbox environment is a one-time copy of production. It has email and SMS notifications disabled - preventing confusion for users. It is ideal for developing and testing integrations without any impact on production.
The sandbox is not continuously synchronised with production - it is a copy created at the time it was set up.