Find routes around a point
USPS carrier routes within a radius of a latitude and longitude — the same search the Oppizi map runs when you drop a pin on a store.
Pair it with the geocoder to start from a street address.
Pass each result's raw object straight into Set EDDM routes.
This endpoint caps results rather than paging them: it accepts first but has no skip. If totalCount is larger than what you got back, raise first — there is no second page to fetch.
Authorization
ClientBearer Client-scoped key as a Bearer JWT; always pinned to your own client.
In: header
Query Parameters
Latitude (decimal degrees).
Longitude (decimal degrees).
Search radius in meters (default 3000, ≤20000).
Max routes (default 200, ≤500).
true to include route polygons as [{lng,lat}] paths.
Response Body
application/json
curl -X GET "https://example.com/client/carrier-routes/search?lat=string&lng=string"{ "success": true, "data": { "nodes": [ { "zip": "60614", "croute": "C021", "zipName": "CHICAGO", "residentCount": 512, "businessCount": 14, "totalCount": 526, "raw": { "ZIP": "60614", "CROUTE": "C021", "TOTAL_COUN": 526 } } ], "totalCount": 1 }}Cancel a draft POST
Abandons a campaign while it is still a draft. Needs an OAuth access token carrying the `campaigns:create` scope — a plain client key is refused. The campaign must be one of yours; anything else returns 404.
Suggest the best-fit routes GET
Carrier routes around a point, ranked by how well they match the audience you describe rather than purely by distance. Build `targetSelection` from [the attribute catalog](/docs/api-reference/targeting/listdemographicattributes), and give a latitude, longitude and radius to search in. Use this when you care who receives the mail; use [route search](/docs/api-reference/targeting/searchcarrierroutes) when you just want everything nearby.