Skip to main content

Overview

The PADS4 scheduling engine. Manages dayparts, playlist assignments to time slots, scheduling exceptions, and the calendar of what content plays on which displays at what times.

Authentication

All endpoints use the standard PADS4 session cookie. Obtain it once and reuse:
Replace https://<your-server> with your PADS4 server address and <ServiceName> with the service path shown above.

Endpoint Reference


Request & Response Examples

PUT /api/v1/Exception

Request:
Response 200 OK:

GET /api/v1/Exception

Request:
Response 200 OK:

DELETE /api/v1/Exception

Request:
Response 200 OK:

POST /api/v1/Exception/create

Request:
Response 200 OK:

DELETE /api/v1/Exception/delete

Request:
Response 200 OK:

POST /api/v1/Exception/delete

Request:
Response 200 OK:

Additional endpoints follow the same patterns shown above. See the Swagger UI for full parameter schemas.