# Stops

Stop management operations.
A stop is a place an order visits; orders and loads both point at it, so
editing one changes the journey for every order and load that visits it.


## Filter stops

 - [POST /stops/filter](https://docs.mvmnt.io/apis/openapi/stops/filterstops.md): Search for stops using filter criteria.

## Common Filters

- By location: { "filter": { "shipperLocationId": { "equalTo": "uuid" } } }
- By postal code: { "filter": { "postalCode": { "equalTo": "60601" } } }
- Recently updated: { "filter": { "updatedAt": { "greaterThan": "2025-01-01T00:00:00Z" } } }

To list the stops of one shipment, read the shipment instead: its orders
carry them in route order, which a filter cannot express.

## Create a stop

 - [POST /stops](https://docs.mvmnt.io/apis/openapi/stops/createstop.md): Create a stop on an order.

A stop is placed exactly one way — by location, postalCode, cityId
or airportCode. Only a location carries a street address; the other
three exist because freight is routinely tendered before an address is
known.

## What happens

- The stop is created and attached to the order
- sequence decides where it falls in the route

## Note

Stops are normally created with their shipment. Use this endpoint to add
one to an order that already exists.

## Get a stop

 - [GET /stops/{id}](https://docs.mvmnt.io/apis/openapi/stops/getstop.md)

## Update a stop

 - [PATCH /stops/{id}](https://docs.mvmnt.io/apis/openapi/stops/updatestop.md): Update a stop. Omitted fields keep their value; an explicit null
clears the field.

The change reaches every order and load that visits this stop.

## Delete a stop

 - [DELETE /stops/{id}](https://docs.mvmnt.io/apis/openapi/stops/deletestop.md): Remove a stop from its order.

## Prerequisites

- An order keeps at least an origin and a destination, so the last two
  stops of an order cannot be removed
- A stop a load already covers cannot be removed; take it off the load
  first