EUS PUSH API
The EUS API, End User Submissionn API, allows a TowerCoverage premium subscriber, to receive End User Submissions via automated XML pushes to a URL of your choice. The goal is to integrate applications, such as a CRM (customer relation management) system, into the EUS process. This allows a CRM system to receive the web inquiry electronically, without having to rely on other services, such as e-mail, to get this data.
WHAT SYSTEMS SUPPORT THE EUS API?
The EUS API does not belong or operate with any specific system. Your programmer, CRM or other system can be used to receive
this data. We provide all the data necessary information for your web developer/programmer to configure and use the EUS API. We
do have a list of CRM systems that are known to integrate with the TowerCoverage EUS API, and have the receiving system already
built in;
VISP
Powercode – www.powercode.com
BillMax – www.billmax.com
Azotel – www.azotel.com
I USE ONE OF THESE SYSTEMS, HOW DO I GET THE API TO WORK WITH THEIR SYSTEM?
Each vendor is responsible for providing documentation on how to enable this feature with their system. If your vendor is not listed
here, please contact them and have them send this documentation to support@towercoverage.com forthose companies, integration documentation is below if provided:
What is the charge for EUS API?
The EUS used the website integration of TowerCoverage.com, this feature requires you to have an active premium account. Due to this, the API does require a premium account, however there is no other charge, charge per use, etc, for the EUS API over the premium account.
HOW DOES THE EUS API WORK?
End User (your customer) visits your webpage
TowerCoverage.com system, finds the 6 best coverages. Generates path analysis for each tower using the site and coverage information already in the system for each tower.
Upon completion, TowerCoverage.com sees that the EUS API is enabled and attempts to push the XML data to the PUSH URL provided by you.
How often should I see this data?
The standard push attempts every 5 minutes, 24 hours a day, 365 days a week. Due to the processing time required to generate all of the link path analysis, we typically expect this data to be pushed within 10 minutes of the EUS website submission. This data is also accessible via the web data page on TowerCoverage.com.
Where can the data come from?
The Subnets you may see are: 38.65.107.0/25 and 2001:550;2400:10::/64