Contents
Introduction
A SOAP (Simple Object Access Protocol)
webservice is available for email address searches and
is described below.
Webservice location
English descriptions of the methods and data types are lower down the page.
Protected
service
(strongly recommended) |
https://www.contactclean.com/soap/ |
Methods |
WSDL |
Non-encrypted service
(strongly deprecated) |
http://www.contactclean.com/soap/ |
Methods |
WSDL |
Note: you must use the lowercase domain name otherwise the webserver will issue a "301"
redirect which can frustrate some SOAP clients.
Methods
Method: addr_search
SearchResult addr_search(string, string, ArrayOfstring)
This method takes three arguments:
- key:string - the 32 character "Search License Key" found in the the user's
account
- encoding:string - currently one of This describes the encoding type
for the email addresses passed in the third argument. Although SSL encryption is available for SOAP access it is
still recommended that email addresses are encoded.
- emails:array - a simple array of email addresses, either md5 encoded or plaintext, to query against the
database.
The method returns one argument, a SearchResult structure
Note: the emails supplied must be in a canonical form (particularly if they are then md5 encoded!). Ie.
jo.bloggs@example.com
is acceptable, but not any of:
Jo.Bloggs@example.com
Jo Bloggs <jo.bloggs@example.com>
"Jo Bloggs" <jo.bloggs@example.com>
etc.
Method: address_search
array address_search(int, int, int,
string, array)
This method takes five arguments:
1. id: int - Your account number
2. v1: int - The first part of your license string
3. v2:int - The second part of your license string
4. encoding:string - either the string ‘plaintext’
or ‘md5’ (without the quote marks)
5. emails:array - a simple array of email addresses
to query against the database.
The method returns one argument: an array
of LookupResult structs, one for each address in the
query array.
If you give ‘md5’ as the 4th
argument then each address in the query array should
be encoded using the MD5 message digest algorithm.
Method: address_search_as
array address_search_as(int, int, int,
string, array, string)
This method takes six arguments:
1. id:int - Your account number
2. v1:int - The first part of your license string
3. v2:int - The second part of your license string
4. encoding:string - either the string ‘plaintext’
or ‘md5’ (without the quote marks)
5. emails:array - a simple array of email addresses
to query against the database.
6. search_as:string - the email address of the user
you’re searching on behalf of.
The method returns one argument: an array of LookupResult
structs, one for each address in the query array.
If you give ‘md5’ as
the 4th argument then each address in the query array
should be encoded using the MD5 message digest algorithm.
This method is identical to address_search above except
for the extra 6th argument. If you hold a number of
address books for various users, e.g. if you are an
email provider, then you can use this method to spring-clean
each address book on behalf of the user. In which case
you should supply the address-book user’s email
address as the 6th argument.
Data Types
Data Type: LookupResult
A struct of two parts:
- query
- string
- result
- string
The values returned in the result field are one of:
- the target's preferred email address. Note this could be the same as the query address.
- the string noforward if the target
is registered with ContactClean but hasn't confirmed
their forwarding address yet.
- the string norecord if there is
no record of the target on the system, or if they have
not given their permission for their new address details
to be released.
- the string remove if the target
wishes to be removed from your address list!
The type ArrayOfLookupResult is an anonymous array of
LookupResult structs
Data Type: NVP
A struct of two parts:
- name
- string
- value
- string
The type ArrayOfNVP is an anonymous array of NVP structs
Data Type: SearchResult
A struct of two parts:
- search_result
- ArrayOfLookupResult
- report
- ArrayOfNVP
Example clients
|