Skip to main content
Live. Requires the walks:read scope.
A walk is a route of door-to-door stops. These endpoints let you list a campaign’s walks and read the stops of any one walk.

List walks

Returns the campaign’s active walks (archived and deleted walks are excluded).

Query parameters

integer
default:"50"
Maximum walks to return. Between 1 and 200.

Response

string
The walk’s unique id (use it with the detail endpoint).
string
Human-readable walk name.
number | null
Centroid latitude of the walk’s stops.
number | null
Centroid longitude of the walk’s stops.
integer
Total number of stops on the walk.
object
Stop counts broken down by status. Every status key is always present (0 when none). See stop statuses.
string
Link to open the walk in the Culper dashboard.
Universal link to open the walk in the mobile app (falls back to the web view when the app isn’t installed).
A campaign with no walks returns { "ok": true, "data": [], "meta": { "count": 0 } } — that’s a valid, successful response, not an error.

Get a walk

Returns a single walk and its ordered stops. Returns 404 not_found if the walk doesn’t exist or isn’t part of your campaign.

Path parameters

string
required
The walk id from the list endpoint (a UUID).

Response

string
The walk’s id.
string
The walk’s name.
object[]
Ordered list of stops on the walk.

Stop statuses

counts keys and a stop’s status field use these values: