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.
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
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}"
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.