• 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

    dict_delta

    A dict_delta is a type of delta that unassigns, moves, or assigns fields in a JSON object, creating it if it does not yet exist. The dict_delta can be used on the route.custom or job.custom fields, for example. If multiple operations are specified, the fields are applied in the following order: unassign, move, assign.

    Name Type Description
    $collection string Required. Must be "dict" for a dict_delta.
    $path string Required on top-level deltas. The JSON path to modify. See Paths for a list of valid paths.
    assign custom Optional. Assign the fields to the existing object.
    move custom Optional. Rename the fields on the existing object.
    unassign string[] Optional. Use unassign to remove the specified fields from the existing object.

    Example

    A revision modifying route.custom using a dict_delta:

    {
      "deltas": [{
        "$path": ["route"],
        "$collection": "keyed_array",
        "ids": ["route0", "route1"],
        "assign": {
          "custom": {
            "$collection": "dict",
            "assign": {
              "custom_123": "456",
            },
            "move": {
              "custom_rename_from": "custom_rename_to",
            },
            "unassign": ["custom_789"],
          },
        },
      }]
    }
    

    See Also

    • delta.
    • Sandboxes.