Get the available appointments for a shipment

post

/custom-actions/getAvailableAppointments/shipments/

Request

There are no request parameters for this operation.

Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Appointment End Time at the stop in yyyy-MM-dd HH:mm:ss format
  • Appointment Start Time at the stop in yyyy-MM-dd HH:mm:ss format
  • Location ID - Shipment appointment location must be specified using either a Stop Number OR a Stop Location ID
  • Location Resource Type Gid - Filter the appointment options based on the location resource type
  • Number of appointment options requested - maximum is 50
  • Shipment ID - Shipment must be identified using one of Shipment ID OR Shipment Reference Number
  • Shipment Reference Number Qualifier ID - In the absence of a Shipment ID, a shipment can be identified using a combination of a Shipment Reference Qualifier ID AND Shipment Reference Number.
  • Shipment Reference Number - In the absence of a Shipment ID, a shipment can be identified using a combination of a Shipment Reference Qualifier ID AND Shipment Reference Number.
  • When set to true, the action will return appointment options for all resources from the next available slot. If set to false, the action will return appointment options for all resources from all time slots.
  • Stop Number - Shipment appointment location must be specified using one of Stop Number OR Stop Location ID
Back to Top

Response

Supported Media Types

200 Response

Success! A successful POST method returns a 200 status code.
Body ()
Root Schema : availableAppointmentOptionsResponse
Type: object
Available Appointment Options
Show Source
Nested Schema : appointmentOptions
Type: array
List of available appointment options
Show Source
Nested Schema : responseStatus
Type: object
Show Source
Nested Schema : appointmentOption
Type: object
Available Appointment Option Details
Show Source
Nested Schema : infeasiblityCodes
Type: array
List of Infeasiblity Codes when appointment is not feasible
Show Source

400 Response

Your request couldn't be processed because it contains missing or invalid information, such as a validation error on an input field, a missing required value, and so forth.
Body ()
Root Schema : errorResponse
Type: object
Show Source

401 Response

Unauthorized, the request was not successful because it lacks valid authentication credentials for the requested resource.
Body ()
Root Schema : errorResponse
Type: object
Show Source

403 Response

Access to the specified resource has been forbidden.
Body ()
Root Schema : errorResponse
Type: object
Show Source

500 Response

The server encountered something unexpected that prevented it from completing the request.
Body ()
Root Schema : errorResponse
Type: object
Show Source
Back to Top