API: Legacy ASMX Compatibility
How old Towercoverage.asmx URLs keep working with the new API.
Old URLs still work
The old service lived at URLs like /Towercoverage.asmx/GetSiteList. The new API automatically:
- Rewrites ASMX method names to the new controller routes.
- Promotes GET→POST for methods that now require POST, moving parameters to form data.
- Repairs malformed URLs where a query string was embedded in the path.
- Redirects
/Towercoverage.asmx(no method) to the API home page.
Mapping (selected)
| Legacy ASMX method | New route |
|---|---|
| GetSiteList | /Sites/GetSiteList |
| SitesAPI | /Sites/SitesAPI |
| CoverageAPI | /Coverage/CoverageAPI |
| BulkCoverageAPI | /Coverage/BulkCoverageAPI |
| LinkPathAPI | /Links/LinkPathAPI |
| MultiCoverageAPI | /MultiCoverage/MultiCoverageAPI |
| EUSPrequalAPI | /EndUserSubmission/EUSPrequalAPI |
| EUSsubmisssion | /EndUserSubmission/EUSsubmisssion |
| GetFrequencyList | /GlobalValues/GetFrequencyList |
| GetAntennaTypeList | /GlobalValues/GetAntennaTypeList |
Newer features (devices, radio systems, polygons, fiber, REST site CRUD) exist only on the new routes.