# Optimize the order of delivery stops (route optimization)

**Use case:** 

A delivery round from Melbourne GPO via Werribee, Dandenong, Frankston, Ringwood, Sunbury and Craigieburn and back. The Actor picks the shortest visiting order, depot first and last, and returns optimizedOrder with the route and legs in that order. One route ($0.003) plus the place-name lookups.

## Input

```json
{
  "origin": "Torquay VIC",
  "destination": "Apollo Bay VIC",
  "profile": "car",
  "mode": "route",
  "routes": [
    {
      "id": "melbourne-delivery-round",
      "locations": [
        "Melbourne GPO",
        "Werribee VIC",
        "Dandenong VIC",
        "Frankston VIC",
        "Ringwood VIC",
        "Sunbury VIC",
        "Craigieburn VIC",
        "Melbourne GPO"
      ],
      "profile": "car",
      "optimize": true
    }
  ],
  "geometry": "all",
  "steps": "none",
  "units": "km",
  "language": "en-GB",
  "elevationIntervalM": 0,
  "geocodeCountry": "AU",
  "looseGeocoding": false,
  "concurrency": 4
}
```

## Output

```json
{
  "input.id": {
    "label": "ID",
    "format": "string"
  },
  "kind": {
    "label": "Kind",
    "format": "string"
  },
  "status": {
    "label": "Status",
    "format": "string"
  },
  "profile": {
    "label": "Profile",
    "format": "string"
  },
  "route.distanceM": {
    "label": "Distance (m)",
    "format": "number"
  },
  "route.durationS": {
    "label": "Duration (s)",
    "format": "number"
  },
  "route.hasToll": {
    "label": "Tolls",
    "format": "boolean"
  },
  "route.hasFerry": {
    "label": "Ferry",
    "format": "boolean"
  },
  "summary.lengthM": {
    "label": "Line length (m)",
    "format": "number"
  },
  "summary.gainM": {
    "label": "Climb (m)",
    "format": "number"
  },
  "summary.lossM": {
    "label": "Descent (m)",
    "format": "number"
  },
  "query.text": {
    "label": "Geocode query",
    "format": "string"
  }
}
```

## About this Actor

This example demonstrates how to use [Directions, Routing & Distance Matrix API — no API key](https://apify.com/davidar/openstreetmap-directions-api.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/davidar/openstreetmap-directions-api.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/davidar/openstreetmap-directions-api.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).