Why OData v4?

OData (Open Data Protocol) is an industry standard backed by Microsoft, SAP, IBM, and Red Hat for building and consuming RESTful APIs.

Industry Standard

Backed by Microsoft, SAP, IBM, and Red Hat — ensuring long-term stability and wide ecosystem support.

Native BI Support

Direct connectivity with Power BI, Tableau, and Excel — no middleware needed for reporting and analytics.

Full CRUD Operations

Create, read, update, and delete operations on companies, orders, and order items with advanced filtering and sorting.

IntegrationId Support

Link your ERP primary keys directly — no need to fetch TSC internal IDs first, simplifying integration development.

Supported Integrations

Connect Time Slot Control with the tools your organization already uses.

SAP

Bidirectional data exchange with SAP ERP for automated order processing and logistics planning.

Power BI

Native OData connector for real-time dashboards, KPIs, and automatic report refresh.

M3 (Infor)

Integration with Infor M3 for manufacturing and distribution logistics coordination.

Business Central

Microsoft Dynamics 365 Business Central (formerly Navision) integration for SMB logistics.

Asseco Helios

Connection with the widely used Czech and Slovak ERP system for order synchronization.

Tableau

OData-compatible data source for advanced visual analytics and interactive dashboards.

Microsoft Excel

Direct OData data feed connection for ad-hoc analysis and reporting in Excel.

Timocom

Transport auctions can be published on the Timocom exchange to reach carriers outside your own network.

Camera systems (LPR)

REST interface for receiving licence plates from LPR cameras of any manufacturer – the basis of the Automatic Gate.

Developer-Friendly API

Everything you need to build robust integrations with confidence.

Sandbox Environment

Full production copy for safe testing — email and SMS disabled to prevent user confusion.

Modern Scalar UI

Interactive API playground for exploring endpoints, testing queries, and prototyping integrations.

Secure Authentication

JWT Bearer tokens and Basic authentication — choose the method that fits your infrastructure.

Two Environments

Production API at api.timeslotcontrol.com and sandbox at api.tscsandbox.com with identical endpoints.

Outbound Webhooks

Configure webhooks to receive real-time event notifications in your own systems — no polling required.

Documentation and developer access

Everything your IT needs to assess the integration is public – no NDA and no sales call required.

API Reference (Scalar)

Interactive documentation of 205 endpoints in 44 sections – Token, Reservation, Order, Company, Driver, Visitor and more. Test calls directly in the browser against the sandbox.

Open api.tscsandbox.com

API reference guide

Step-by-step guide: creating an API account, obtaining a token, the OData entities Company, Order and OrderRow, and the recommended ERP integration procedure.

Open the guide on the wiki

OData metadata

A machine-readable description of all entities and fields of your tenant at /odata/v1/{tenant}/$metadata – consumed by Power BI, Excel and client generators.

How to connect from Excel and Power BI

What you get and send through the API

Company: Company directory – carriers, suppliers, customers, recipients. Matched to your ERP via IntegrationId, no lookup of internal IDs needed.
Order / OrderRow: Transport orders and their lines from the ERP. They fill the Stack of Orders, from which the carrier books without retyping anything.
Reservation: Time slot reservations including statuses, timestamps and custom fields. Created directly from an external system via REST v3.
Workflow: Programmatic reservation status changes: arrival, start and end of handling, departure – for connecting a WMS or the gatehouse.
LPR: Receives licence plates read by camera systems from any manufacturer – vehicle arrival and departure.
Callout (webhooks): Calls your API when a licence plate is detected or a reservation changes – no polling.

Example: token and creating a reservation

Two requests are enough. The tenant is the name of your instance – for yourcompany.timeslotcontrol.com it is yourcompany.

curl -X POST "https://api.tscsandbox.com/v1/{tenant}/Token"   -H "Content-Type: application/json"   -d '{"username": "api@yourcompany.com", "password": "..."}'

{ "token": "eyJhbGciOi..." }

curl -X POST "https://api.tscsandbox.com/v3/{tenant}/Reservations"   -H "Authorization: Bearer eyJhbGciOi..."   -H "Content-Type: application/json"   -d '{"ResourceId": "<resource-guid>",
       "Start": "2026-09-15T08:00:00Z",
       "UnitId": "<unit-guid>",
       "NumberOfUnits": 10}'

GET https://api.timeslotcontrol.com/odata/v1/{tenant}/$metadata

Where the data flows

Green lines are integrations over OData v4, grey lines are the devices and people in the yard. Every arrow is a named data flow.

Integration Workflow

How data flows between your systems and Time Slot Control.

Your ERP ERP sends orders via OData API

OData API TSC processes reservations & scheduling

Time Slot Control Real-time status updates flow back

BI & Reports BI tools generate reports & dashboards

Need a custom integration?

Our technical team will help you design and implement the perfect integration for your infrastructure.

Schedule a technical consultation

Security & compliance: where the data lives and how it is protected

Connect TSC with your entire ecosystem