Proxy
Why proxy exists
Section titled “Why proxy exists”Raw responses from sources like the U.S. Census Geocoder can be wide, nested, and awkward for declarative Flow. Proxy paths normalize selected responses into predictable buckets—collections you can loop in Flow, plus shortcuts when you only need the top match.
Behavior
Section titled “Behavior”- GET-only routing with optional host allowlists
- Errors return JSON with a clear status—not HTML error pages
- Field names align with the proxy service’s OpenAPI spec
Salesforce setup
Section titled “Salesforce setup”- Complete Salesforce setup (same Three_Levers_API credential).
- Import the proxy Swagger URL separately from boundary lookup services, for example:
https://apis.threelevers.com/gis/v1/proxy/swagger.php?service=CensusGeocoder- Wire Flow Actions from the generated proxy External Service—do not assume lookup operation names apply to proxy operations.
CensusGeocoder is an example service name—use only proxy services Three Levers has added to your API key (you may have boundary and proxy services on the same key).