# Three ways to get stops into Pathway

> CSV for the morning upload, the Stops API for your own tools and webhooks for orders that arrive all day.

- URL: https://nextjs-example.notra.site/blog/importing-stops
- Published: 2026-08-20
- Authors: Kwame Mensah
- Tags: engineering

Every route starts with a list of stops. How that list reaches Pathway depends on where your orders live, so we support three ways in, and you can mix them.

## Pick the one that fits

CSV upload

One file each morning, exported from your WMS or a spreadsheet.

Stops API

Your own scripts push stops whenever they’re ready.

Webhooks

Shopify or your order system sends each order as it comes in.

## Sending a stop

The CSV needs one row per stop with an address, and everything else is optional. The API takes the same fields as JSON:

**CSV**

```csv
reference,address,window_start,window_end,service_minutes
ORD-10482,"Rua Augusta 120, Lisboa",09:00,11:00,4
ORD-10483,"Av. da Liberdade 45, Lisboa",11:00,13:00,12
```

**API**

```bash
curl https://api.pathway.example/v1/stops \
  -H "Authorization: Bearer $PATHWAY_KEY" \
  -d '{"reference":"ORD-10482","address":"Rua Augusta 120, Lisboa","window":{"start":"09:00","end":"11:00"}}'
```

## Duplicates are safe

All three paths use `reference` as the key. Sending the same reference again updates the stop instead of creating a second one, so a retried webhook or a re-uploaded file never puts a parcel on two routes.

> **Note**
>
> Stops that arrive after routes are locked go to **Unplanned** for the next planning run, unless you turn on **Add late stops to live routes** for the depot.
