doesRegistrationUserIdExist API

Description

The doesRegistrationUserIdExist API call is used to check whether or not a user has been registered with TextKey™.

API Testing Page

To test the doesRegistrationUserIdExist API Call in a fully interactive environment, click here.

Input Parameters

Name Data Type Description Required
apiKey String This is a unique key that is used to authenticate an API request. It should never be exposed. Yes
userID Integer The unique identifier that was used when the user was registered with TextKey™. This userID is stored within the TextKey™ registration database and is encrypted internally to ensure it is secure. Yes
isHashed Integer True indicates if the userID was hashed before the user was registered. Yes

Output

Name Data Type Description
cellNumberCount Integer The count of Cell Numbers on this account that match the input (normally 0 or 1). If an error is detected, the cellNumberCount will be -2. For the UserId calls, this is always 0.
userIDCount Integer The count of UserIDs on this account that match the input (normally 0 or 1). If an error is detected, the userIDCount will be -2. For the Cell Number calls, this is always 0.
errorDescr String If a error occurs, this is the error message. This will be blank if the call was successful.

REST Example

RESTful URL

The TextKey™ Restful interface consists of the secure URL path followed by the appropriate CommandName.

For instance:

 https://secure.textkey.com/REST/TKRest.asmx/CommandName

The CommandName is the API call itself which in this case is doesRegistrationUserIdExist.

Here is what the complete URL for this API call would look like:

https://secure.textkey.com/REST/TKRest.asmx/doesRegistrationUserIdExist

All Restful calls must be made using the POST method and should be of the content type application/json.

Here is an example of what a request header should look like:

POST /REST/TKRest.asmx/doesRegistrationUserIdExist HTTP/1.1
Host: secure.textkey.com
Accept: */*
Content-Type:application/json
Content-Length: 136

JSON Input Payload

All TextKey™ Restful service commands take a JSON object as the input and return a JSON object as the resulting payload. Authentication is handled via an API key as one of the parameters in the JSON input.

The JSON Input payload for the doesRegistrationUserIdExist API call should look something like this:

{
    "DataIn": {
        "apiKey": "9021fa44-f1bc-4590-b975-42fee031e078",
        "userId": "Stan",
        "isHashed": "true"
    }
}

JSON Output Payload

The JSON response should look something like this:

JSON Response with a valid payload
{
    "d":{
        "__type":"TextKeyCommon.TKStructures+RegistrationExistence",
        "cellNumberCount":-2,
        "userIDCount":1,
        "errorDescr":""
    }
}
__type: TextKeyCommon.TKStructures+RegistrationExistence
cellNumberCount: -2
userIDCount: 1
errorDescr:

OR

JSON Response with an error
{
    "d":{
        "__type":"TextKeyCommon.TKStructures+RegistrationExistence",
        "cellNumberCount":0,
        "userIDCount":0,
        "errorDescr":"No GUID Validation Row: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)."
    }
}
Error: No GUID Validation Row: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

REST Code Examples

PHP

Example 1 - Using the TextKey™ PHP Helper Library

The simplest way to use TextKey™ REST API calls, is to include the TextKey™ REST Helper Library and then use the TextKey object to handle all of the heavy lifting.

You will be returned a PHP object and can reference all of the payload values directly from that object.

// Include the TextKey classes
include_once("textkey_rest.php");

// Setup the API call parameters
$testuserid ="Stan";
$isHashed = TRUE;

// Set the authentication
$apikey = "9021fa44-f1bc-4590-b975-42fee031e078";

// Create a TK object
$tk = new textKey($apikey);

// Handle the operation
$textkey_result = $tk->perform_DoesRegistrationUserIDExist($testuserid, $isHashed);

// Handle the results
if ($textkey_result->errorDescr == "") {
  $tkResultsArr = get_object_vars($textkey_result);
	$results = "";
  foreach($tkResultsArr as $key => $value) { 
    $results .= $key . ': ' . $value . "<BR>";
  } 			
  echo $results;
}
else {
  $results = 'Error: ' . $textkey_result->errorDescr . "<BR>";
  echo $results;
}

Here is an example of the PHP object returned:

stdClass Object
(
    [__type] => TextKeyCommon.TKStructures+RegistrationExistence
    [cellNumberCount] => -2
    [userIDCount] => 1
    [errorDescr] => 
)
Example 2 - Using the REST API Call directly

In order to use the TextKey™ REST API calls directly, you will need to setup the API payload using the appropriate parameters and the API key formatted as a JSON string and then make a CURL POST request.

The POST header does need to be setup as a JSON request (i.e. an application/json header) or you will not get a response.

You will be returned a JSON string as the API call payload. That can be converted into a PHP object using the json_decode call.

// TextKey REST path
define('TK_REST', 'https://secure.textkey.com/REST/TKRest.asmx/');

// Setup the API call parameters
$testuserid ="Stan";
$isHashed = TRUE;

// Set the authentication
$apikey = "9021fa44-f1bc-4590-b975-42fee031e078";

// Build the REST API URL
$url = TK_REST . 'doesRegistrationUserIdExist';

// Setup data
$postdata = json_encode(
	array('DataIn' => 
		array(
			'apiKey' => urlencode($apikey),
			'userID' => urlencode($testuserid),
			'isHashed' => urlencode($isHashed?"true":"false"),
		)
	),
JSON_PRETTY_PRINT);

// Handle the API request via CURL
$curl = curl_init($url);

// Set the CURL params and make sure it is a JSON request
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_POST, true);
curl_setopt($curl, CURLOPT_POSTFIELDS, $postdata);
curl_setopt($curl, CURLOPT_HTTPHEADER, array('Content-Type:application/json'));
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, 0);  // Wildcard certificate

$response = curl_exec($curl);
curl_close($curl);

// Handle the payload
$textkey_payload = json_decode($response);
if ($textkey_payload->d) {
	$textkey_result = $textkey_payload->d;
}
else {
	$textkey_result = $textkey_payload;
};

// Handle the results
if ($textkey_result->errorDescr == "") {
  $tkResultsArr = get_object_vars($textkey_result);
	$results = "";
  foreach($tkResultsArr as $key => $value) { 
    $results .= $key . ': ' . $value . "<BR>";
  } 			
  echo $results;
}
else {
  $results = 'Error: ' . $textkey_result->errorDescr . "<BR>";
  echo $results;
}

JAVA

Example - Using the TextKey™ JAVA Helper Library

The simplest way to use TextKey™ REST API calls, is to include the TextKey™ REST Helper Library and then use the TextKeyRest object to handle all of the heavy lifting.

You will be returned a JSON string.

package com.textkey.rest.examples;

import org.json.JSONObject;
import com.textkey.rest.TextKeyRest;

public class TestDoesRegistrationUserIdExist {

	public static void main(String[] args) {
		/* Setup */
		String TK_API = "9021fa44-f1bc-4590-b975-42fee031e078";
		  
		/* Create the TextKey object */
		TextKeyRest textkey = new TextKeyRest(TK_API, false);
		
		/* Setup the API call parameters */
		String UserID = "Stan";
		String isHashed = "TRUE";

		/* Make the REST API Call */
		String JSONpayload =  textkey.perform_DoesRegistrationUserIDExist(UserID, 
																          isHashed);
		
		/* Display the API Results */
		try {
			JSONObject results = new JSONObject(JSONpayload).getJSONObject("d");
		    System.out.println("Test Results: \n" + TextKeyRest.toPrettyFormat(results.toString()));
		} catch(Exception pe){
			pe.printStackTrace();
		} 				
	}
	
}

Here is an example of the JSON string with the d wrapper removed:

Test Results: 
{
  "__type": "TextKeyCommon.TKStructures+RegistrationExistence",
  "cellNumberCount": -2,
  "errorDescr": "",
  "userIDCount": 1
}

NOTE: For more detais on the JAVA Library object and methods, you can take a look at the online documentation at http://textpower.github.io/RESTLibrary-java/.

RUBY

Example - Using the TextKey™ RUBY Helper Library

The simplest way to use TextKey™ REST API calls, is to include the TextKey™ REST Helper Library and then use the TextKeyRest object to handle all of the heavy lifting.

You will be returned a JSON string.

NOTE: To install the textkey_rest gem you can run gem install textkey_rest from a command line. To build the testkey_rest gem locally, get the latest repository at github and follow the instructions.

require 'json'
require 'textkey_rest'

# Setup
apiKey = "9021fa44-f1bc-4590-b975-42fee031e078"

# Create the textkey object
textkey = TextKeyRest.new(apiKey, false)

# Setup the API parameters
userID = "Stan"
isHashed = "TRUE"

# Make the API Call
response = textkey.perform_DoesRegistrationUserIDExist(userID, isHashed)

# Pull out the data from the response
response_obj = JSON.parse(response)
response_data = response_obj['d']

# Display the response 
puts "TextKey Results:"
puts JSON.pretty_generate response_data

Here is an example of the JSON string with the d wrapper removed:

Test Results: 
{
  "__type": "TextKeyCommon.TKStructures+RegistrationExistence",
  "cellNumberCount": -2,
  "errorDescr": "",
  "userIDCount": 1
}

NOTE: For more detais on the RUBY Library object and methods, you can take a look at the online documentation at http://textpower.github.io/RESTLibrary-ruby/.

Javascript

All of the TextKey™ REST API calls are CORS compliant so they can be called via an Ajax request with no cross domain issues.

In order to user the TextKey™ REST API calls via javascript, you will need to setup the API payload using the appropriate parameters and the API key formatted as a JSON string and then make an Ajax POST request. The POST header does need to be setup as a JSON request (i.e. an application/json header) or you will not get a response.

You will be returned a JSON string as the API call payload.

NOTE: Exposing your API key via any client side code is not recommended. If you choose to use the TextKey™ API calls via a Javascript call, make sure to create a temporary API Key using the getTempAPIKey API call server side and then use that temporary key during its lifespan on any client side API calls.

<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script type="text/javascript">
// Build a class to handle the API call input payload
function textkeyPayload(apiKey, userID, isHashed) {
    this.apiKey = apiKey;
    this.userID = userID;
    this.isHashed = isHashed;
    this.toJsonString = function () { 
      return JSON.stringify({ 'DataIn': this }); 
    };
};

// Handle the API Request and response
function textkeyAPIRequest(txtCommand, APIJSONData) {
	// Setup the API URL
	var urlAPI = 'http://www.textkey.com/REST/TKRest.asmx/'+txtCommand;

	// Make the API call via a JSON Ajax request
	$.ajax({
		type: "POST",
		contentType: "application/json; charset=utf-8",
		url: urlAPI,
		data: APIJSONData,
		dataType: "json",
		success: function (APIResponse, textStatus) {
			document.write("textStatus: "+textStatus+ "<HR>");
			document.write("API Response: "+JSON.stringify(APIResponse, null, 4) + "<HR>");
			if (textStatus == 'success') {
				if (APIResponse.hasOwnProperty('d')) {
					APIPayload = APIResponse.d;
				} else {
					APIPayload = APIResponse;
				}
				document.write("API Payload: "+JSON.stringify(APIPayload, null, 4) + "<HR>");
				if (APIPayload.errorDescr == "") {
					document.write("userIDCount: " + APIPayload.userIDCount);
				}
				else {
					document.write("Error: " + APIPayload.errorDescr);
				}
			}
			else {
				document.write("Error: " + textStatus);
			}
		},
		error: function (jqXHR, textStatus, errorThrown) {
			document.write("Error: " + jqXHR.status);
		}
	});
}

// Setup the API command
var txtCommand = 'doesRegistrationUserIdExist';
// Build the API payload
var DoesRegistrationUserIdExist = new textkeyPayload("9021fa44-f1bc-4590-b975-42fee031e078", "Stan", true);
// Make the API Call
textkeyAPIRequest(txtCommand, DoesRegistrationUserIdExist.toJsonString());
</script>

SOAP Example

Authentication Settings

A SOAP header is required on all SOAP API calls using the _Key variant and the header information is identical on all calls.

doesRegistrationUserIdExist requires a SOAP header.
doesRegistrationUserIdExist_Key does not require a SOAP header but uses the API Key in the body of the SOAP request.

Authentication Settings using an API Key
API Key: 9021fa44-f1bc-4590-b975-42fee031e078

OR

Authentication Settings using an UserID/Password Combination
userId: 1ed93006208f0540e452e3a37d8299bc
Password: Password12345
Campaign: 
Keyword:

The WSDL document for the TextKey™ SOAP interface is located at: https://secure.textkey.com/ws/textkey.asmx?wsdl.

The address for the SOAP calls on the TextKey™ interface is: https://secure.textkey.com/ws/textkey.asmx.

The name space for the SOAP calls on the TextKey™ interface is: https://secure.textkey.com/services/.

Call Parameters

The parameters should look something like this:

apiKey: 9021fa44-f1bc-4590-b975-42fee031e078
userID: Stan
isHashed: 1

SOAP Request

The SOAP request should look something like this:

SOAP Request using the API Key

OR

SOAP Request using the UserID/Password

SOAP Response

The SOAP response should look something like this:

SOAP Response with an valid payload

OR

SOAP Response with an error

Output Results

The final results will need to be extracted from the XML response payload should look something like this:

SOAP Response with a valid payload
stdClass Object
(
    [cellNumberCount] => -2
    [userIDCount] => 0
    [errorDescr] => 
)
cellNumberCount: -2
userIDCount: 0
errorDescr:

OR

SOAP Response with an error
stdClass Object
(
    [cellNumberCount] => 0
    [userIDCount] => 0
    [errorDescr] => No GUID Validation Row: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
)
Error: No GUID Validation Row: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

SOAP Code Examples

PHP

The PHP Helper library contain a textkey class that makes calling TextKey™ SOAP API functions simple. Just include the helper file textkey_soap.php in your PHP code, inititalize a textkey object using your credentials (i.e. either an API key or a UserID/Password), and then make the API call with the appropriate parameters. You will be returned an object with the API call payload. 

// Include the TextKey classes
include_once("../textkey_soap.php");

// Setup the API call parameters
$testuserid ="Stan";
$isHashed = TRUE;

// Set the authentication
$apikey = "9021fa44-f1bc-4590-b975-42fee031e078";

// Create a textkey object
if ($apikey != "") {
    $tk = new textKey("", "", "", "", $apikey);
}

// Handle the operation
$textkey_result = $tk->perform_DoesRegistrationUserIDExist($testuserid, $isHashed);

// Show the textkey API payload object
print_r($textkey_result);
echo "<HR>";

// Handle the results
if ($textkey_result->errorDescr == "") {
    $tkResultsArr = get_object_vars($textkey_result);
  	$results = "";
  foreach($tkResultsArr as $key => $value) { 
        $results .= $key . ': ' . $value . "<BR>";
    } 			
}
else {
    $results = 'Error: ' . $textkey_result->errorDescr . "<BR>";
}
echo $results;

CURL

From a command line, you can test the SOAP API calls using a CURL request:

The SOAP doesRegistrationUserIdExist Request is stored in a file called doesRegistrationUserIdExist.xml
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" >
    <soap:Body>
        <doesRegistrationUserIdExist_Key xmlns="https://secure.textkey.com/services/">
            <apiKey>9021fa44-f1bc-4590-b975-42fee031e078</apiKey>
                <userID>Stan</userID>
                    <isHashed>true</isHashed>
                    </doesRegistrationUserIdExist_Key>
                </soap:Body>
            </soap:Envelope>
CURL command using doesRegistrationUserIdExist.xml
curl -H "Content-Type: text/xml; charset=utf-8" -H "SOAPAction:" -d @doesRegistrationUserIdExist.xml -X POST https://secure.textkey.com/ws/textkey.asmx
XML Response from API doesRegistrationUserIdExist Request
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
        <doesRegistrationUserIdExist_KeyResponse xmlns="https://secure.textkey.com/services/">
            <doesRegistrationUserIdExist_KeyResult>
                <cellNumberCount>-2</cellNumberCount>
                    <userIDCount>1</userIDCount>
                        <errorDescr />
                    </doesRegistrationUserIdExist_KeyResult>
                </doesRegistrationUserIdExist_KeyResponse>
            </soap:Body>
        </soap:Envelope>