1. Driver-schedule-exceptions
eLogii
  • Introduction
  • Entities
  • FAQs
  • Query parameters
  • Webhooks
  • Tasks
    • Task Elements
    • createOrUpdateMany
      POST
    • Get tasks
      GET
    • Create tasks
      POST
    • Delete tasks
      POST
    • Update a task
      PUT
    • Get Proof of Delivery
      GET
    • Cancel tasks
      POST
    • Post Tasks Create Return
      POST
    • Move tasks to another date
      POST
    • postTasksReattempt
      POST
    • Start tracking a task (webhook)
      POST
  • Drivers
    • Driver Elements
    • Get drivers
      GET
    • Create multiple drivers
      POST
    • Update drivers
      POST
    • Delete drivers
      POST
  • Customers
    • Customer Elements
    • Get customers
    • Create customers
    • Update customers
    • Delete customers
  • Depots
    • Depot Elements
    • Get depots
    • Create depots
    • Update depots
    • Delete depots
  • Driver-schedule-exceptions
    • Driver-schedule-exception elements
    • Get all exceptions
      GET
    • Get schedule exception for a specific driver
      GET
    • Update a schedule exception
      PUT
    • Create multiple schedule exceptions
      POST
    • Delete multiple schedule exceptions
      POST
  • Route-template-groups
    • Route-template-groups elements
    • Get route template groups
    • Create a route-template-group
    • Update a route template group
    • Delete multiple route template groups
    • Schedule for dates
  • Routes
    • Route Elements
    • Get routes
    • Clear route(s)
    • Lock route(s)
    • Unlock route(s)
    • Set planned ETAs
    • Setting the task order
  • Task-template-groups
    • Task-template-groups Elements
    • Get task-template-groups
    • Create task-template-groups
    • Get one task-template-group by _id
    • Update task-template-group
    • Delete one task-template-group
    • Delete multiple task-template-groups
    • Schedule task-template-groups for dates
    • Add tasks to group
  • Vehicles
    • Vehicle Elements
    • Create multiple vehicles
    • Get vehicles
    • Update multiple vehicles
    • Delete multiple vehicles
  • Zones
    • Zones Elements
    • getZones
    • postZones
    • putZones_id
    • deleteZones_id
  • Optimization
    • Optimization Elements
    • Run optimization for provided data set
    • Run optimization for one or multiple dates
    • Run optimization for one or multiple existing routes
    • Optimize tasks in a period (e.g. 1 month), where some of the tasks have varying intervals - e.g. weekly, every 2 weeks, monthly
    • Run optimization for a date range
  • Forms
    • Get all forms
    • Create and design a form
    • Update many forms
    • Delete many forms
  • Form submissions
    • Get all form submissions
    • Get a specific form's submissions
    • Update many form submissions
    • Delete many form submissions
  1. Driver-schedule-exceptions

Driver-schedule-exception elements

Schedule Exceptions#

Schedule exceptions are temporary schedule overrides that are applied to drivers’ schedules within a specific period. After that period passes, the driver’s schedule will follow the default setup..
reference - text value which can be used to query a schedule exception.
driver -
id - driver ID which can be found on the driver's profile.
uid - This is a unique code that eLogii assigns each driver upon creation and can be found on the driver's profile.
reference- The driver reference also available on the driver's profile.
dateRange - The span over which the exception takes effect. Required field.
startDate - required field. Marks the start date of the exception. Format YYYYMMDD
endDate - required field. Marks the end date of the exception. Format YYYYMMDD
description - Information about what the exception is for.
dayOff - Whether the exceštion means the driver won’t be working. Default: false. if true, the driver will be temporarily disabled from optimization.
overrides - Specific overrides which will temporarily be applied.
schedule - Schedule overrides
timeWindows
start -Expressed in minutes. 0…1440
end - Expressed in minutes. 0…2880
breaks
timeWindow
start - Expressed in minutes. 0…1440
end - Expressed in minutes. 0…2880
offset - Break offset from route start.
start - Expressed in minutes. 0…1440
end - Expressed in minutes. 0…2880
duration - The duration of the break. (in minutes)
skills - Temporary override of the skills the driver possesses.
maxMultiDayRouteDays - The maximum number of days the driver can be on the road when doing multiday routes.
startLocation - Contains fields used to specify the start location of the driver, i.e. the starting point of their route.
type - Enum indicating the type of task location:
0
1
2
3
Predefined depot, used in conjunction with uid field for depot UID.

uid - Required for types 0 and 1 – unique identifier of the depot or customer location
address - Contains the address of the location
addressLine2 - Contains the 2nd address of the location
postCode - Contains the location post code
city - Contains the location city
country - Contains the country of the location
what3words - Contains the what3words location coordinates of the location
coordinates - Contains the location coordinates. Format: [longitude, latitude]
contactName - Stores the contact name
contactPhone - Stores the contact phone number
contactEmail - stores the contact email address
setupDuration - Setup and service duration define the time needed to complete a task at the pickup location (e.g., 10 minutes to drop off a delivery or 30 minutes to replace equipment). Setup duration only applies to the first task at a location. Any value set here overrides the default set in Configuration → Optimization.
serviceDuration - Setup and service duration define how long it takes to complete a task at the pickup location (e.g., 10 minutes to drop off a delivery or 30 minutes to replace equipment). Service duration is always added to the total stop time, even if other tasks exist at the same location. Any value set here overrides the default set in Configuration → Optimization.
customerId - contains the customer id
customerUID - contains the customer UID
meta - Contains metadata.
comments
userId
text
timestamp
originalCoordinates Format [longitude, latitude]
overriden
endLocation - Contains fields used to specify the end location of the driver, i.e., the starting point of their route.
type - Enum indicating the type of task location:
0
1
2
3
Predefined depot, used in conjunction with uid field for depot UID.

uid - Required for types 0 and 1 – unique identifier of the depot or customer location.
name - Shows the displayed name of the location.
address - Contains the address of the location.
addressLine2 - Contains the 2nd address of the location.
postCode - Contains the location post code.
city - Contains the location city
country - Contains the country of the location
what3words - Contains the what3words location coordinates of the location
coordinates - Contains the location coordinates. Format: [longitude, latitude]
contactName - Stores the contact name
contactPhone - Stores the contact phone number
contactEmail - stores the contact email address
setupDuration - Setup and service duration define the time needed to complete a task at the pickup location (e.g., 10 minutes to drop off a delivery or 30 minutes to replace equipment). Setup duration only applies to the first task at a location. Any value set here overrides the default set in Configuration → Optimization.
serviceDuration - Setup and service duration define how long it takes to complete a task at the pickup location (e.g., 10 minutes to drop off a delivery or 30 minutes to replace equipment). Service duration is always added to the total stop time, even if other tasks exist at the same location. Any value set here overrides the default set in Configuration → Optimization.
customerId - contains the customer id
customerUID - contains the customer UID
meta - Contains metadata.
comments
userId
text
timestamp
originalCoordinates Format [longitude, latitude]
overriden
Modified at 2025-11-24 19:18:24
Previous
Delete depots
Next
Get all exceptions
Built with