Three Levers GIS API
Turn latitude and longitude into boundary answers your Salesforce org can use—in Flow, Apex, or on the Map Records and Take Action hosted map.
Marketing page: Three Levers GIS API
No public catalog
Section titled “No public catalog”Each service name is provisioned per client and wired only to your API key. Example names in screenshots (e.g. KCDistricts) are illustrative only.
Service types
Section titled “Service types”| Type | Used for | Billing |
|---|---|---|
| Map boundary layer | Hosted map overlay, click-to-select, extract | Setup per service + API usage |
| Geolocation lookup | Flow/Apex inside/near/distance | Same model (bundled with map program) |
| CensusGeocoder proxy | Geocode + optional TIGER layers | Same model as map layers |
Capabilities
Section titled “Capabilities”| Endpoint style | Job |
|---|---|
| Lookup | Point-in-polygon or nearest feature |
| Extract | GeoJSON features within a radius |
| Map token / v1 | Hosted map for reportMapWithFence |
| Proxy | Normalized public geodata (e.g. Census) for Flow |
| OpenAPI | Per-service Swagger for External Service import |
Limits
Section titled “Limits”- Boundary GeoJSON is not unlimited—reviewed and possibly simplified at setup
- ~2,000 report rows when used with the map component (Salesforce API)
- Sandbox API keys: not offered today
- No published API rate caps (fair use in agreement)
Typical Salesforce path
Section titled “Typical Salesforce path”- Store ApiKey in a Named Credential
- Import service OpenAPI as an External Service
- Call from Flow or Apex
Start with Authentication, then Salesforce setup.
Support: documentation + email + phone (paid API clients).
Still stuck? Contact support.