• Home
  • Guides
  • Reference
  • Support
Search Results for

    Show / Hide Table of Contents
    • Support
      • Frequently Asked Questions
      • Release Notes
      • Advanced Optimizer Settings
      • Contact Verizon Connect Support
      • Limitations
    • UI (Verizon Connect Scenarios)
      • Overview

    Release notes

    1.60

    • Added settings.centroid_strength.

    1.23

    • Added recommend_request.max_results_per_route, recommend_request.max_results_per_driver, and recommend_request.max_results_per_date.

    1.22

    • Added settings.enable_legal_breaks, settings.legal_break_duration and settings.legal_break_interval. Added legal_break to stop_type
    • Added settings.defaults

    1.20

    • Added job.forbidden_drivers
    • Added driver.first_name, driver.middle_name, driver.last_name

    1.19

    • Added settings.clustering field.
    • Added problem.vehicles field. See Routing with Vehicles.

    1.17

    • Improved handling of geocoding and reverse geocoding errors.

    1.16

    • Sandboxes have been added to the API.

    1.15.2

    • Fixed a number of issues that could cause tasks to hang.

    1.14

    • The build.return_request, evaluate.return_request, insert.return_request, sequence.return_request fields were added. When set to true, RouteCloud returns a full request which can be fed back into a subsequent call. See Full vs Partial Responses.
    • The sequence of a route can now be specified on the new route.stops field instead of route.jobs. This allows users to input stops of all types (including depot, break as well as job type stops), and have their stop.id and stop.custom fields preserved.

    1.12

    • Added the route.name, job.name, driver.name, schedule.name fields.
    • Added the route.custom, job.custom, driver.custom, schedule.custom fields.

    1.11

    • The marker class was added. job.location, route.location, route.start_location, route.end_location and depot.location were all changed to accept a marker instead of a simple latlon.

    1.10.1

    • The geocode call was made more efficient and robust.

    1.10

    • Automatic driver.centroid placement has been added. See the Centroids call.

    1.9

    • Added the allowed_days_of_week, allowed_variance_before, allowed_variance_after fields to job
    • Added the allowed_days_of_week, allowed_variance_before, allowed_variance_after and latest_date fields to schedule

    1.8

    • Added the loads field to job and the load_capacities field to route.

    1.7

    • Added the required_driver field to job.

    1.6

    • Added the geocode and reverse_geocode endpoints.
    • Added the route_paths and route_paths_type fields to settings.

    1.5

    • Added the enable_front_loading field to settings.

    1.4

    • Added the insert endpoint.

    1.3

    • Added the schedule_response entity to responses.

    1.2

    • Added multi-day routes.

    1.1

    • Added recurring schedules.

    1.0

    • Initial release of the RouteCloud API.
    In this article
    Back to top
    © 2023 Verizon. All rights reserved. Verizon Privacy policy California Privacy Notice Your Privacy Choices Privacy request