• Home
  • Guides
  • Reference
  • Support

    Show / Hide Table of Contents
    • API Overview
      • Overview
      • Authentication
      • Retrieving API Results
      • Referenced vs Inline Entities
      • Choosing API Response Data
      • Handling API Errors
    • separator
    • Vehicle Routing Endpoints
      • Path
    • Optimization Endpoints
      • Instantiate
      • Build
      • Assignment Restrictions
      • Optimize
      • Sequence
      • Evaluate
      • Recommend
      • Insert
      • Centroids
      • Zones
      • Consolidate By Job Restrictions
      • Consolidate By Route Assignments
    • Geocoding Endpoints
      • Geocode
      • Reverse Geocode
    • Task Endpoints
      • List
      • Status
      • Result
      • Cancel
    • Sandbox Endpoints
      • List
      • Create
      • Rename
      • Retrieve
      • Update
      • Delete
      • Revisions
      • Add Revision
      • Expiry
      • Permissions
    • Verizon Connect Fleet Integration Endpoints
      • Pull Platform Data
      • Sync Platform Data
      • List Platform Territories
    • Other Endpoints
      • Canonicalize
      • Route Cards
      • Validate
      • Version
    • separator
    • Request Types
      • problem
      • capacity_metric
      • depot
      • driver
      • driver_break
      • job
      • job_template
      • job_type
      • load_amount
      • marker
      • problem_defaults
      • route
      • schedule
      • settings
      • shift
      • shift_override
      • shift_pattern
      • shift_pattern_assignment
      • stop
      • vehicle
      • zone
      • variance
    • Response Types
      • instantiate_response
      • problem_response
      • problem_aggregates
      • driver_response
      • geocoded_location
      • recommend_option
      • route_response
      • schedule_response
      • schedule_instantiate_response
      • stop_response
      • violation
    • Meta Types
      • task_redirect_response
      • task_status_response
      • validate_response
    • Sandbox Types
      • delta
      • array_delta
      • dict_delta
      • keyed_array_delta
      • object_delta
      • set_delta
      • revision
      • revision_created_response
      • revision_response
      • sandbox_response
    • Common Types
      • date_range
      • day_of_week
      • hazmat_load_type
      • id
      • latlon
      • stop_type
      • time_window
      • custom
      • polygon
    • Primitive Types
      • boolean
      • date
      • datetime
      • float
      • integer
      • string
      • timespan

    Authentication

    Every request to RouteCloud must be authenticated. Use your Verizon Connect Enterprise username and password to authenticate with the RouteCloud API. To get a username and password, contact Verizon Connect sales.

    Basic Authentication

    For convenience, authentication can be done on every request with Basic Auth. Verizon Connect usernames contain a colon (:), which must be url-encoded as %3A. For example:

    curl -u "youraccount%3Amain:password" "https://routecloud.telogis.com/v1/build" -H "Content-Type: application/json" --data-binary "@multiday.json"
    

    Using the Verizon Connect Authentication Service

    The most secure way to authenticate is to make a separate POST call to the Verizon Connect authentication service, then pass your session ID into RouteCloud API calls as a header.

    To get a session ID from the Verizon Connect authentication service:

    curl "https://login.telogis.com/login" -H "Content-Type: application/json" --data-ascii '{"username":"youraccount:main", "password":"pass123", "application":"session"}'
    

    Example result from Verizon Connect authentication service:

    {"success":true,"sessionId":"e938d41c-d519-4f07-b0a9-26d4745d6e74"}
    

    Example call to RouteCloud API with the session ID:

    curl "https://routecloud.telogis.com/v1/build" -H "Content-Type: application/json" -H "X-Telogis-Session-Id: e938d41c-d519-4f07-b0a9-26d4745d6e74" --data-binary "@multiday.json"
    

    Session Lifetime

    A Verizon Connect authentication session times out after approximately one hour of non-usage. Every call that uses the session ID extends the lifetime of the session.

    See Also

    • API Overview