API: Getting Started
Base URL, authentication, rate limits, and response formats explained simply.
What the API is for
The TowerCoverage API lets other software (your CRM, website forms, scripts) read and update your TowerCoverage data: sites, coverages, links, maps, devices, and leads (EUS). It is the modern replacement for the old Towercoverage.asmx web service, and old URLs still work — see Legacy ASMX Compatibility.
What you need
| Credential | Where to get it |
|---|---|
| Account ID | Your TowerCoverage account number |
| API Key | Account → API settings (not your login password) |
How to send credentials
Recommended — HTTP headers:
X-TowerCoverage-Account-Id: 12345
X-TowerCoverage-Api-Key: your-api-key-hereAlso supported (legacy) — query string or form fields: ?accountid=12345&key=your-api-key
Rules of the road
- Routing:
/{Controller}/{Action}, e.g./Sites/GetSiteList. - Rate limit: 120 requests per minute (HTTP 429 if exceeded).
- Max upload: 12 MB (bulk EUS files).
- Read endpoints use
GET; create/update usePOST(form or JSON).
Account requirements
Most endpoints require a valid Account ID + key, a premium subscription, and available monthly API quota. If any is missing you'll get a clear message (see Errors & Troubleshooting).
No-auth health checks
GET /Health/Ping— is the API up?GET /Diagnostics/CheckTest— echo test.GET /Diagnostics/TestLongitudeAndLatitude— validate coordinates.