Suggest the best-fit routes
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, and give a latitude, longitude and radius to search in.
Use this when you care who receives the mail; use route search when you just want everything nearby.
Authorization
ClientBearer Client-scoped key as a Bearer JWT; always pinned to your own client.
In: header
Query Parameters
Latitude.
Longitude.
Search radius around the point.
JSON array of demographic attribute groups (from /client/eddm/demographic-attributes). Omit for geo-only suggestions.
Max routes (cap 500).
Pagination cursor (pageInfo.endCursor).
Response Body
application/json
curl -X GET "https://example.com/client/carrier-routes/suggest?lat=string&lng=string&radius=string"{ "success": true, "data": { "suggestions": [ { "zip": "33130", "croute": "C012", "fit": 0.87 } ], "totalCount": 42, "pageInfo": { "hasNextPage": true, "endCursor": "eyJ..." } }}Find routes around a point GET
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](/docs/api-reference/targeting/geocodeaddress) to start from a street address. Pass each result's `raw` object straight into [Set EDDM routes](/docs/api-reference/campaign-builder/setcampaignareas). 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.
List a city’s routes GET
Every USPS carrier route covering a city, each with its ZIP, route code and how many residential and business addresses it reaches. Add `includePaths=true` for the map polygon of each route, or `zips=` to narrow to particular ZIP codes. Each route's `raw` object is what [Set EDDM routes](/docs/api-reference/campaign-builder/setcampaignareas) expects.