(314) 878-1200



The Voice Signature ServiceSM (VSS) is offered as a transaction-based RESTful Web Service that can be implemented by service users (Requestors) through either the VSS API or the VSE API (VoiceSig ExpressTM).

The VSS interface is not tied to a specific technology and a Requester may implement it using a wide range of technologies, including VoiceXML, and XML RPC. A typical VoiceXML integration of the VSS is can be accomplished in less than an hour.


Requestor systems can invoke the VSS API through either the VoiceXML or XML interface.
The Voice Signature ServiceSM system (VSS) supports VXML v2.X. A VSS Session is implemented through a VXML sub-dialog call.
The VSS also supports XML for implementation as a Web Service or with legacy IVR platforms (that may not be VXML compliant).

The VSS VXML sub-dialog has been tested and is in use with many platforms and hosted services: Twilio, Genesys/Interactive Intelligence, BeVocal (Nuance), Voxeo (Aspect), Convergys, USAN, Genesys, PlumVoice, Tellme, Intervoice, etc.


The VoiceSig ExpressTM  VSE API provides a hosted telephony platform. The VSE API can be invoked from a web page using simple server-side scripts (sample scripts are available in several scripting languages – PHP, Ruby, Perl, CGI, Java, etc.).

VoiceSig ExpressTM is designed to support Requesters or applications that require TradeHarbor to provide the telephony interface. The VSE API supports two basic telephone interactions – an inbound Call and an Outbound Call:

  • Inbound Call
    In an Inbound Call session the VSE returns a phone number to be called along with an extension number, which is actually a temporary key* to tie the data session to the phone call placed to the VSE telephony platform.
  • Outbound Call
    In an Outbound Call session the VSE telephony platform makes a call to the phone number provided through the API to acquire a Voice Signature.

Contact us for more info: info@tradeharbor.com

The VSS Web Service only accepts service requests from valid Requesters with a current VSS SLA through secure communications over the Internet using SSL, TLS/SSL, VPN, or other protocols. Communication can also occur over a dedicated connection between the Requester and VSS, such as ATM, Frame-Relay, dedicated T1 or other methods as specified by the Requester and agreed to by TradeHarbor in the VSS SLA.