EUS Submission API

Purpose

: The:The EUS Submission API has the same functionality of the website integration iframe. When a request is made to api.towercoverage.com, the server will check that all values are valid and to ensure you have available calls on your account. If calls are available and all values are valid, it will provide a response of success. It will then be passed to the processing server to be ran through the End User Submission process.

Fields

: MulticoverageID: 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.

Account: You can locate your Account ID in the API's Tab of your account settings and also within the iframe of your Multi Coverage.

First Name/Last Name: These fields can only contain text values and special characters are not allowed.

Address / City / Country / State / Zip Code / Latitude / Longitude: 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.

API Key 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.

Customer Notification This is the field that will enable this EUS submission to notify the customer. This will send a e-mail to the customer, all settings for this is in the EUS Settings page. This is NOT a required field. If the field is not present, it will assume 0 (zero) and not e-mail the customer. If the field is present and it is a 1 (one), it will then issue a e-mail to notify the customer.

All other fields 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.

Response Codes

200 OK: Everything is ok and accepted Anything else, the API will return with error message that explains why it was not accepted.

SOAP 1.1 Request

SOAP 1.1 Response

SOAP 1.2 Request / Response

HTTP GET

HTTP POST