The 1.0bulk TransitionalEN"upload "
API is a feature of Tower Coverage.com that is only usable by Unlimited Tier Accounts. This API allows End User Submission Data to be added to the TowerCoverage.com EUS Data. All Bulk Upload entries are flagged as Low Priority and will take longer to receive the results than a normal EUS Submission API push. Each POST to this API counts as a call from your account.
This field is a number value only. Each Multi Map on your account is assigned an ID when it is created. This number will never change until the map is deleted. You can locate the Multi Coverage ID by using the Get Multicoverage List API or by opening the map that you wish to use. The ID can also be found in the URL of the map or in the iframe code on the update tab.
The Submission ID is a number value but is not a required field. When using the Bulk Upload API you can choose whether to create new entries or to update your existing data on your account. The submission ID can be found by downloading the CSV of your data. Each row of the CSV will contain all stored data for each submission as well as the ID.
You can locate your Account ID in the API's Tab of your account settings and also within the iframe of your Multi Coverage.
These fields can only contain text values and special characters are not allowed.
When entering addresses, your state must be spelled out, abbreviations are not allowed. It is also suggested to get your country ID number by using the Get Country List API but you can spell out your country as well (example: United States). Although the address fields are required for the request to be successful, it is advised that you utilize the Latitude and Longitude if known. If you enter a Latitude and Longitude, the address, city, state, country and Zip will be ignored.
Serviceable = 2 New EUS = 3 No Service = 4 Installed = 5
The Pin Status field is required and only the above given values are acceptable.
Your API key can be located on the API's tab of your account settings. This is a required field and is what the API server will use to determine if you have sufficient API calls available on your account.
All other fields of the API are required and will only allow text, numbers, periods and hyphens. No special characters can be included as well as no return characters. Although they do have a specific label for purposes of database entry, you can utilize these fields for any type of data you wish. An example of this would be using the preferred Method of Contact field to store a service level or package (your customer) signed up for.
The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.
The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values.
The following is a sample HTTP GET request and response. The placeholders shown need to be replaced with actual values.
The following is a sample HTTP POST request and response. The placeholders shown need to be replaced with actual values.