List targetable cities
The cities you can target, with the coordinates and state you need for targeting.
search matches either the name or "Name, ST", and state filters by state code.
Page with first (up to 1000) and skip.
Authorization
ClientBearer Client-scoped key as a Bearer JWT; always pinned to your own client.
In: header
Query Parameters
Case-insensitive city name, or "Austin, TX" to pin the state too.
State code (e.g. TX). Wins over a state parsed out of search.
Max rows per page (default 500, ≤1000).
Page offset (default 0).
Response Body
application/json
curl -X GET "https://example.com/client/cities"{ "success": true, "data": { "nodes": [ { "id": "55", "name": "Chicago", "state": "IL", "nameWithState": "Chicago, IL", "country_id": "1", "country_name": "United States", "latitude": "41.8781", "longitude": "-87.6298" } ], "returnedCount": 1, "totalCount": 42, "hasNextPage": true, "complete": false, "adjustments": [ { "code": "TRUNCATED", "field": "nodes", "requested": 1, "applied": 1, "affects": [ "nodes" ], "detail": "Showing 1 of 42 cities. Pass skip=1 for the next page." } ], "note": "Showing 1 of 42 cities…" }}Browse the template library GET
The shared template library to start a design from, with orientation, format, industry and whether the template is USPS-compliant. These are templates available to everyone — your own designs are at [GET /client/designs](/docs/api-reference/assets/listdesigns).
List your missions GET
The individual distribution runs behind your campaigns. Filter by `campaignId`, `ids` or status, search on the location name, and page with `first` and `skip`. Each mission carries the place it covered (for example "Kendall Square") and what kind of location that is.