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”There is no shared layer catalog. Three Levers provisions one or more named service values on your API key—each service is a boundary layer, lookup dataset, or proxy you licensed separately. Example names in screenshots (e.g. KCDistricts) are illustrative only. Your onboarding email lists every service name active on your key.
One API key, many services
Section titled “One API key, many services”| Concept | Meaning |
|---|---|
| API key | One production credential per org (Named Principal + custom setting) |
service | Named layer or proxy on that key—you choose which one each API call uses |
| Salesforce | One External Service import per service; reuse the same Named Credential for all |
Add layers over time without a new key—Three Levers registers additional service names on your existing key when you expand coverage.
Same managed package as Map Records
Section titled “Same managed package as Map Records”Map Records and Take Action and GIS API callouts share one install:
| Piece | Shipped in package |
|---|---|
Lightning map component (reportMapWithFence) | Yes |
Named Credential Three_Levers_API | Yes |
External Credential Three_Levers_API | Yes |
Custom setting Three_Levers_GIS_Setting__c | Yes |
After install, configure your client API key (see Salesforce setup)—do not create a second Named Credential unless your integration architect requires a separate credential for a non-standard pattern.
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 | Short-lived token for hosted map iframe |
| 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”- Install Map Records and Take Action (managed package).
- Set your API key on the External Credential Named Principal and in Three Levers GIS Setting (Salesforce setup).
- Import each licensed service OpenAPI as an External Service (OpenAPI import).
- Call from Flow or Apex (Lookup, Extract, Proxy).
- Optional: configure hosted map
servicein the map component (Hosted map).
Start with Authentication, then Salesforce setup.
Support: documentation + email + phone (paid API clients).
Still stuck? Contact support.
Related products
Section titled “Related products”- Map Records and Take Action — free managed package; uses GIS API for hosted map + overlay
- Lightning Flow iFrame — separate package