Parcel Request Facilities
The facilities we ship to, searched by name or by the code on the envelope.
Frederick, 2026-09-01: "letting it be an autocomplete only to the facilities that we have active contracts and shipping to. That way, it's guaranteed to resolve ... We should also accept the facility code."
⛔IT ANSWERS A LOOKUP, IT DOES NOT PUBLISH A CUSTOMER LIST. Three characters minimum for a name, matched at a word boundary, ten rows maximum, rate limited, and no empty-query listing. The roster is 44 facilities across 14 organizations (measured on production 2026-09-01), and every name and code on it is printed on the envelopes these senders already addressed -- so this is not a secret. It is also not a download.
⛔AND THE LIMITER IS A SPEED BUMP, NOT A BOUND. LOOKUP_RATE is per-IP: it stops one curious person and does nothing at all about somebody rotating addresses. What makes this safe to expose is the VALUE of the data, not the difficulty of collecting it -- no ADP, no contact, no contract, no org id, and nothing here that a competitor could not also get from procurement records. Do not let "rate limited" carry more weight than that.
⛔AND IT RETURNS THE NAME FOR A CODE. That is the whole point of accepting four digits: the sender types what they addressed the parcel to and the page shows them the facility it resolves to, so a mistyped digit is visible to the person who can tell it is wrong -- before it decides which account manager gets the ticket.
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/public/parcel-request/facilities
- Auth: none declared
Query parameters
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.