Telnic Ltd. provides a Java-based TelHosting Software application. This application interacts with the DNS directly, and exposes a publicly available web service, using SOAP over HTTP as its protocol. Client applications implementing this SOAP interface can work with the TelHosting Software application to perform all .tel-related operations.
All APIs work by receiving request messages from the clients and sending response messages back to them unless the request message requires no response. All messages are expressed in XML, and their respective syntax is speci๏ฌed by an XML schema; see List of Schema Files. The messages must follow the specific format, see Message Format.
In addition to the client service API, the TelHosting Software exposes an internal API for administration purposes. That API is available only to users with specific permissions (TelHosting Providers) and is not covered in this document.
Document about TelHosting SOAP API :
TelHosting Client SOAP API Reference
About this Document:
This document describes the TelHosting SOAP API, which can be used for managing and publishing contact information in .tel domain DNS records.
The reference is targeted at developers interested in creating new .tel client applications and enhancing existing ones. The document assumes that you are familiar with application programming standard SOAP (Simple Object Access Protocol) and that you understand the key concepts of the .tel innovative technology. See Related Links for references to relevant materials.
With this reference, you will learn about:
*The objects used in the interface
*The functions available to manipulate all those objects: domains, resource records, and profiles
*Specific usage requirements for each function
-----------------------------------
1,) DNS TXT ".tad" has to be stored in a special sub-folder within the .tel domain.
2.) How do I store DNS TXT ".tad" in my special sub-folder?:
Go to:
storeRecord
About storeRecord:
This operation allows a single record to be stored.
storeRecordRequest
Exactly one of the top-level elements with its sub-elements must be present to signify the type of record. Each valid child element of the storeRecordRequest element (listed in the second part of the table below) specifies a DNS record type, and uses all the attributes .
-----------
Element Name:
txt
Description:
One or multiple subelements <text> to specify the free text contact data.
Conclusion:
To specify a TXT advert text data, you must write:
<text>advertext<text>
-------------
Attribute Name:
owner
Description:
Optional Owner name of the record relative to the domain in which it is contained. Similar to the DNS notation, an at-sign (@) denotes the domainโs name itself.
--------------------
Example:
Create a new TXT record with the owner name sample.reggie.tel associated with profile 5:
Request:
<typ:storeRecordRequest domainName="reggie.tel">
<typ:txt ttl="3600" owner="sample" profiles="5" groups="">
<typ:text>Hello World!</typ:text>
</typ:txt>
</typ:storeRecordRequest>
Response:
<storeRecordResponse xmlns="http://xmlns.telnic.org/ws/nsp/client/record/types-1.0">
<id>61</id>
</storeRecordResponse>
.
Your ISP has to provide you with a adaptation / adjustment of the web interface, the so called
"Internal .Tel Adminsistration API". Otherwhise, you are not able to create advertisments within your .tel domain (as a developer).
.
