• Home
  • Guides
  • Reference
  • Support
Search Results for

    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. You may use Verizon Connect Reveal or Fleet credentials to access the RouteCloud API. If you do not already have an account, contact Verizon Connect sales.

    Basic Authentication

    HTTP Basic Authentication is supported for both Verizon Connect Reveal and Fleet accounts.

    curl -u "user@domain.com:password" "https://routecloud.telogis.com/v1/build" -H "Content-Type: application/json" --data-binary "@multiday.json"
    

    Verizon Connect Fleet 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"
    

    If your client supports cookies a session token will be set in the response, your client will still need to handle re-authenticating on session expiry.

    Verizon Connect Reveal JWT Authentication

    JWT Bearer authentication is supported for Reveal

    curl -H "Authorization: Bearer {JWT}" "https://routecloud.telogis.com/v1/build" -H "Content-Type: application/json" --data-binary "@multiday.json"
    

    Verizon Connect Fleet Session ID Authentication

    To get a session ID from the Fleet authentication service:

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

    Example result:

    {"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 Fleet 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
    In this article
    Back to top
    © 2023 Verizon. All rights reserved. Verizon Privacy policy California Privacy Notice Your Privacy Choices Privacy request