Using Contacts

Using the Whispir API to store and retrieve Contacts

The Whispir API provides secure cloud based storage for your contact information.  This can then easily be retreived by any application or device that requires access, and has permission to do so.

This section describes the process of storing, retrieving, updating and deleting Contact information using the Whispir API.

  1. How to retrieve the Contacts from the Company Workspace
  2. How to retrieve the Contacts from another Workspace
  3. How to retrieve a single Contact from the Company or a Workspace
  4. How to search for Contacts using the API
  5. How to send messages to Contacts
  6. How to create new Contacts
  7. How to update Contacts
  8. How to delete Contacts

How to retrieve the Contacts from the Company Workspace

Name

Value

Service URL

https://api.whispir.com/contacts?apikey=

Method

GET

Request Headers

Authorization

The Base 64 representation of the Whispir Username and Password.

Accept

application/vnd.whispir.contact-v1+xml
application/vnd.whispir.contact-v1+json

Query String

apikey=

The Mashery API key to authenticate the request.

searchCriteria=
The search criteria that you would like to filter the request with (described in more detail below)

Response

200 OK

The request was processed successfully

401 Unauthorized

The authorization details were incorrect

415 Unsupported Media Type

The MIME type requested is not supported for the requested resource

Request/Response Example

After performing this request, the response contains a list of URLs to each of the Contacts that the API user has access to. 

Each URL is stored within a 'Link' element.  Each 'Link' element that is returned contains the following information:

Element Name

Description

Method

The HTTP Method that is available on this particular URI
Rel

The searchable description about what this URI should be used for.

URI The URI in focus.  This can be used by the developer to perform some action on the resource.
Type (Optional) When the type is update or create, the applicable Content Type header and Accept header are supplied for the developer to use.

This information allows the application client to traverse the available resources easily:

HTTP1.1 GET https://api.whispir.com/contacts?apikey=DFD0FD90u809SDF90832FDS
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Accept: application/vnd.whispir.contact-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:return xmlns:ns2="http://schemas.api.whispir.com/dap" xmlns:ns3="http://schemas.api.whispir.com">
    <status>1 to 1 of 1</status>
    <ns2:contacts>
        <ns2:contact>
            <id>AF48A9EC3F02E43C</id>
            <firstName>Fred</firstName>
            <lastName>Smith</lastName>
            <status>A</status>
            <messagingoptions/> 
            <ns2:link method="GET" 
                      rel="self" 
                      uri="http://api.whispir.com/contacts/AF48A9EC3F02E43C?apikey=DFD0FD90u809SDF90832FDS"/>
        </ns2:contact>
    </ns2:contacts>
</ns2:return>

The elements returned in the response are described as follows:

Element Name

Description

id

The unique Contact ID for this Contact
firstName

The First Name of the Contact

lastName The Last Name of the Contact
status

The status of the Contact:
A: Active
D: Disabled (i.e. contact not available to be used or accessed) 

messagingoptions
The messaging options that have been set up for this contact
link The URL for the user/application to access this specific contact record.

How to retrieve the Contacts from the another Workspace

Name

Value

Service URL

https://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts?apikey=

Method

GET

Request Headers

Authorization

The Base 64 representation of the Whispir Username and Password.

Accept

application/vnd.whispir.contact-v1+xml
application/vnd.whispir.contact-v1+json

Query String

apikey=

The Mashery API key to authenticate the request.

searchCriteria=
The search criteria that you would like to filter the request with (described in more detail below)

Response

200 OK

The request was processed successfully

401 Unauthorized

The authorization details were incorrect

415 Unsupported Media Type

The MIME type requested is not supported for the requested resource

Request/Response Example

After performing this request, the response contains a list of URLs to each of the Contacts that the API user has access to. 

Each URL is stored within a 'Link' element.  Each 'Link' element that is returned contains the following information:

Element Name

Description

Method

The HTTP Method that is available on this particular URI
Rel

The searchable description about what this URI should be used for.

URI The URI in focus.  This can be used by the developer to perform some action on the resource.
Type (Optional) When the type is update or create, the applicable Content Type header and Accept header are supplied for the developer to use.

This information allows the application client to traverse the available resources easily:

HTTP1.1 GET https://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts?apikey=DFD0FD90u809SDF90832FDS
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Accept: application/vnd.whispir.contact-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:return xmlns:ns2="http://schemas.api.whispir.com/dap" xmlns:ns3="http://schemas.api.whispir.com">
    <status>1 to 1 of 1</status>
    <ns2:contacts>
        <ns2:contact>
            <id>AF48A9EC3F02E43C</id>
            <firstName>Fred</firstName>
            <lastName>Smith</lastName>
            <status>A</status>
            <messagingoptions/> 
            <ns2:link method="GET" 
                      rel="self" 
                     
uri="http://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts/AF48A9EC3F02E43C?apikey=DFD0FD90u809SDF90832FDS"/>
        </ns2:contact>
    </ns2:contacts>
</ns2:return>

The elements returned in the response are described as follows:

Element Name

Description

id

The unique Contact ID for this Contact
firstName

The First Name of the Contact

lastName The Last Name of the Contact
status

The status of the Contact:
A: Active
D: Disabled (i.e. contact not available to be used or accessed) 

messagingoptions
The messaging options that have been set up for this contact
link The URL for the user/application to access this specific contact record.

How to retrieve a single Contact from the company or a workspace

Name

Value

Service URL

https://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts/AF48A9EC3F02E43C

Method

GET

Request Headers

Authorization

The Base 64 representation of the Whispir Username and Password.

Accept

application/vnd.whispir.contact-v1+xml
application/vnd.whispir.contact-v1+json

Query String

apikey=

The Mashery API key to authenticate the request.

Response

200 OK

The request was processed successfully

401 Unauthorized

The authorization details were incorrect

415 Unsupported Media Type

The MIME type requested is not supported for the requested resource

Request/Response Example

After performing this request, the response contains the Contact object specified in the request URL.

HTTP1.1 GET https://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts?apikey=DFD0FD90u809SDF90832FDS
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Accept: application/vnd.whispir.contact-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:contact xmlns:ns2="http://schemas.api.whispir.com" 
             xmlns:ns3="http://schemas.api.whispir.com/dap">
    <firstName>Fred</firstName>
    <lastName>Smith</lastName>
    <status>A</status>
    <companyName></companyName>
    <jobTitle></jobTitle>
    <division></division>
    <businessUnit></businessUnit>
    <department></department>
    <teamName1></teamName1>
    <teamName2></teamName2>
    <role1></role1>
    <role2></role2>
    <timezone>+11</timezone>
    <personalEmailAddress1></personalEmailAddress1>
    <personalEmailAddress2></personalEmailAddress2>
    <personalPhoneAreaCode1></personalPhoneAreaCode1>
    <personalPhone1></personalPhone1>
    <personalPhoneAreaCode2></personalPhoneAreaCode2>
    <personalPhone2></personalPhone2>
    <workEmailAddress1>fred.smith@test.com</workEmailAddress1>
    <workEmailAddress2></workEmailAddress2>
    <workMobilePhone1>61426549873</workMobilePhone1>
    <workPhoneAreaCode1></workPhoneAreaCode1>
    <workPhone1></workPhone1>
    <workPhoneAreaCode2></workPhoneAreaCode2>
    <workPhone2></workPhone2>
    <workSetellitePhone></workSetellitePhone>
    <workOtherPhone></workOtherPhone>
    <title></title>
    <personalFaxAreaCode1></personalFaxAreaCode1>
    <personalFax1></personalFax1>
    <workFaxAreaCode1></workFaxAreaCode1>
    <workFax1></workFax1>
    <personalAddress1></personalAddress1>
    <personalAddress2></personalAddress2>
    <personalSuburb></personalSuburb>
    <personalState></personalState>
    <personalPostCode></personalPostCode>
    <personalCountry></personalCountry>
    <workAddress1></workAddress1>
    <workAddress2></workAddress2>
    <workSuburb></workSuburb>
    <workState></workState>
    <workPostCode></workPostCode>
    <workCountry>Australia</workCountry>
    <workPostalAddress1></workPostalAddress1>
    <workPostalAddress2></workPostalAddress2>
    <workPostalSuburb></workPostalSuburb>
    <workPostalState></workPostalState>
    <workPostalPostCode></workPostalPostCode>
    <workPostalCountry></workPostalCountry>
    <otherTitle></otherTitle>
    <otherFirstName></otherFirstName>
    <otherLastName></otherLastName>
    <otherMobile></otherMobile>
    <otherPhoneAreaCode1></otherPhoneAreaCode1>
    <otherPhone1></otherPhone1>
    <mri>Fred_Smith.341550.Sandbox@Contact.whispir.com</mri>
    <userName></userName>
    <password></password>
    <secretQuestion></secretQuestion>
    <secretAnswer></secretAnswer>
    <messagingoptions>
        <messagingoption channel="sms">
            <enabled>true</enabled>
            <primary>WorkMobilePhone1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
        <messagingoption channel="email">
            <enabled>true</enabled>
            <primary>WorkEmailAddress1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
        <messagingoption channel="voice">
            <enabled>true</enabled>
            <primary>WorkMobilePhone1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
    </messagingoptions>
    <ns3:link method="GET" rel="self" 
              uri="https://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts?apikey=DFD0FD90u809SDF90832FDS"/>
</ns2:contact>  

How to search for Contacts using the API

When using the Whispir API to manage Contacts, API Users can easily query the API for any of the fields available on the Contact records and retrieve only the Contacts that meet this criteria.

This searching mechanism can be useful to see if any contacts exist in the system with a specific email address, phone number, or job role.

The key parameters that are required on the URL to facilitate this search are as follows:

Name

Value

Example

FieldName e.g. firstName or lastName

Value to search for e.g. jordan

&firstName=jordan

sortOrder

The order in which you require the results to be returned. Either asc or desc.

&sortOrder=asc

sortFields

The fields that you require the ordering to be performed on. Multiple fields can be provided, separated by a comma.

&sortFields=lastName,jobTitle

These can then be combined to construct your Contact Search e.g.

Request/Response Example

After performing this request, the response contains the Contact object specified in the request URL.

HTTP1.1 GET https://api.whispir.com/contacts?apikey=DFD0FD90u809SDF90832FDS&firstName=fred&sortOrder=desc&sortFields=workEmailAddressPrimary
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Accept: application/vnd.whispir.contact-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:return xmlns:ns2="http://schemas.api.whispir.com/dap" xmlns:ns3="http://schemas.api.whispir.com">
    <status>1 to 1 of 1</status>
    <ns2:contacts>
        <ns2:contact>
            <id>AF48A9EC3F02E43C</id>
            <firstName>Fred</firstName>
            <lastName>Smith</lastName>
            <status>A</status>
            <messagingoptions/> 
            <ns2:link method="GET" 
                      rel="self" 
                     
uri="http://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts/AF48A9EC3F02E43C?apikey=DFD0FD90u809SDF90832FDS"/>
        </ns2:contact>
    </ns2:contacts>
</ns2:return>

 

How to send messages to Contacts (from the company or a workspace)

Once you have retrieved the contact you are looking for from the Company Workspace, or a separate Workspace, the contact information can then be inserted into a message request to send a message to this contact.

More information about sending messages can be found here.

The key piece of information that you require to send a message to a contact is the MRI (Message Resource Identifier).

HTTP1.1 GET https://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts?apikey=DFD0FD90u809SDF90832FDS
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Accept: application/vnd.whispir.contact-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:contact xmlns:ns2="http://schemas.api.whispir.com" 
             xmlns:ns3="http://schemas.api.whispir.com/dap">
    <firstName>Fred</firstName>
    <lastName>Smith</lastName>
    <status>A</status>
    . . .
    <mri>Fred_Smith.341550.Sandbox@Contact.whispir.com</mri>
	. . .
    <ns3:link method="GET" rel="self" 
              uri="https://api.whispir.com/workspaces/D9FD0F2SFMFG903FJ/contacts?apikey=DFD0FD90u809SDF90832FDS"/>
</ns2:contact>

The 'To' field of the Message resource can be populated with this MRI in order to send this contact a message.

For example: 

HTTP 1.1 POST http://api.whispir.com/messages?apikey=;
Authorization: Basic am9obi5zbWl0aDpteXBhc3N3b3Jk
Content-Type: application/vnd.whispir.message-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:message xmlns:ns2="http://schemas.api.whispir.com">
    <to>Fred_Smith.341550.Sandbox@Contact.whispir.com</to>
    <subject>Test Message</subject>    
    <body>This is the body of my test SMS message</body>
</ns2:message>

How to create new Contacts (in the Company Workspace)

Name

Value

Service URL

https://api.whispir.com/contacts?apikey=

Method

POST

Request Headers

Authorization

The Base 64 representation of the Whispir Username and Password.

Content-Type

application/vnd.whispir.contact-v1+xml
application/vnd.whispir.contact-v1+json

Query String

apikey=

The Mashery API key to authenticate the request.

Response

201 Created

The request was accepted and the contact was created

400 Bad Request

The reqest was formatted incorrectly

401 Unauthorized

The authorization details were incorrect

415 Unsupported Media Type

The MIME type requested is not supported for the requested resource

422 Unprocessable Entity

The reqest was formatted correctly but could not be processed due to a validation error

Request/Response Example

After performing this request, the response body contains the resulting Contact that has been created from the request. 

The response headers provide the Location of the newly created contact in the form of a URL.

Example Request:

HTTP1.1 POST https://api.whispir.com/contacts?apikey=DFD0FD90u809SDF90832FDS
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Content-Type: application/vnd.whispir.contact-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:contact xmlns:ns2="http://schemas.api.whispir.com" xmlns:ns3="http://schemas.api.whispir.com/dap">
    <firstName>John</firstName>
    <lastName>Smith</lastName>
    <status>A</status>
    <timezone>+10</timezone>
    <workEmailAddress1>jsmith@testcompany.com</workEmailAddress1>
    <workMobilePhone1>61423456789</workMobilePhone1>
    <workCountry>Australia</workCountry>
    <messagingoptions>
        <messagingoption channel="sms">
            <enabled>true</enabled>
            <primary>WorkMobilePhone1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
        <messagingoption channel="email">
            <enabled>true</enabled>
            <primary>WorkEmailAddress1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
        <messagingoption channel="voice">
            <enabled>true</enabled>
            <primary>WorkMobilePhone1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
    </messagingoptions>
</ns2:contact>

Example Response:

Status Code: 201 Created
Cache-Control: max-age=0
Connection: keep-alive
Content-Length: 1738
Content-Type: application/vnd.whispir.contact-v1+xml
Date: Mon, 26 Nov 2012 05:49:12 GMT
Expires: Mon, 26 Nov 2012 05:49:12 GMT
Location: http://api.whispir.com/contacts/124F6B2D46A5A268?apikey=DFD0FD90u809SDF90832FDS
Server: Mashery Proxy
X-Mashery-Responder: javaproxy-au-worker-1.mashery.com
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:contact xmlns:ns2="http://schemas.api.whispir.com" xmlns:ns3="http://schemas.api.whispir.com/dap">
    <type>COMPANY</type>
    <firstName>John</firstName>
    <lastName>Smith</lastName>
    <status>A</status>
    <timezone>+10</timezone>
    <workEmailAddress1>jsmith@testcompany.com</workEmailAddress1>
    <workMobilePhone1>61423456789</workMobilePhone1>
    <workCountry>Australia</workCountry>
    . . .
	<mri>John_Smith.549065@Contact.whispir.com</mri>
    <messagingoptions>
        <messagingoption channel="sms">
            <enabled>true</enabled>
            <primary>WorkMobilePhone1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
        <messagingoption channel="email">
            <enabled>true</enabled>
            <primary>WorkEmailAddress1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
        <messagingoption channel="voice">
            <enabled>true</enabled>
            <primary>WorkMobilePhone1</primary>
            <secondary></secondary>
            <tertiary></tertiary>
        </messagingoption>
    </messagingoptions>
    <ns3:link method="GET" 
              rel="self" 
              uri="http://api.whispir.com/contacts/124F6B2D46A5A268?apikey=DFD0FD90u809SDF90832FDS"/>
    <ns3:link type="application/vnd.whispir.contact-v1+json,application/vnd.whispir.contact-v1+xml" 
              method="PUT" 
              rel="updateContact" 
              uri="http://api.whispir.com/contacts/124F6B2D46A5A268?apikey=DFD0FD90u809SDF90832FDS"/>
    <ns3:link method="DELETE" 
              rel="deleteContact" 
              uri="http://api.whispir.com/contacts/124F6B2D46A5A268?apikey=DFD0FD90u809SDF90832FDS"/>
</ns2:contact> 

How to edit/update Contacts in the Company Workspace

Name

Value

Service URL

https://api.whispir.com/contacts?apikey=

Method

PUT

Request Headers

Authorization

The Base 64 representation of the Whispir Username and Password.

Content-Type

application/vnd.whispir.contact-v1+xml
application/vnd.whispir.contact-v1+json

Query String

apikey=

The Mashery API key to authenticate the request.

Response

204 No Content

The request was accepted and the contact was updated. No data will be returned as it is unncessary

400 Bad Request

The reqest was formatted incorrectly

401 Unauthorized

The authorization details were incorrect

415 Unsupported Media Type

The MIME type requested is not supported for the requested resource

422 Unprocessable Entity

The reqest was formatted correctly but could not be processed due to a validation error

Request/Response Example

After performing this request, the response does not contain any information other than the headers as it is not necessary.

The user has requested to update a contact, and when the response of 204 is returned, the contact is successfully updated.

Please note: any information that is not included in the request message will be automatically removed from the existing contact record.  Users must specify all fields, even if they are not being updated.

Example Request:

HTTP1.1 PUT https://api.whispir.com/contacts/124F6B2D46A5A268?apikey=DFD0FD90u809SDF90832FDS
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Content-Type: application/vnd.whispir.contact-v1+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:contact xmlns:ns2="http://schemas.api.whispir.com" xmlns:ns3="http://schemas.api.whispir.com/dap">
    <firstName>John</firstName>
    <lastName>Smith</lastName>
    <status>A</status>
    <companyName>New Company Name</companyName> <!-- Updated -->
    <jobTitle></jobTitle>
    <division></division>
    <businessUnit></businessUnit>
    <department></department>
    <teamName1></teamName1>
    <teamName2></teamName2>
    <role1></role1>
    <role2></role2>
    <timezone>+11</timezone>
    <personalEmailAddress1></personalEmailAddress1>
    <personalEmailAddress2></personalEmailAddress2>
    <personalPhoneAreaCode1></personalPhoneAreaCode1>
    <personalPhone1></personalPhone1>
    <personalPhoneAreaCode2></personalPhoneAreaCode2>
    <personalPhone2></personalPhone2>
    <workEmailAddress1>jwalsh@whispir.com</workEmailAddress1>
    <workEmailAddress2></workEmailAddress2>
    <workMobilePhone1>61423556682</workMobilePhone1>
    <workPhoneAreaCode1></workPhoneAreaCode1>
    <workPhone1></workPhone1>
    <workPhoneAreaCode2></workPhoneAreaCode2>
    <workPhone2></workPhone2>
    <workSetellitePhone></workSetellitePhone>
    <workOtherPhone></workOtherPhone>
    <title></title>
    <personalFaxAreaCode1></personalFaxAreaCode1>
    <personalFax1></personalFax1>
    <workFaxAreaCode1></workFaxAreaCode1>
    <workFax1></workFax1>
    <personalAddress1></personalAddress1>
    <personalAddress2></personalAddress2>
    <personalSuburb></personalSuburb>
    <personalState></personalState>
    <personalPostCode></personalPostCode>
    <personalCountry></personalCountry>
    <workAddress1></workAddress1>
    <workAddress2></workAddress2>
    <workSuburb></workSuburb>
    <workState></workState>
    <workPostCode></workPostCode>
    <workCountry>Australia</workCountry>
    <workPostalAddress1></workPostalAddress1>
    <workPostalAddress2></workPostalAddress2>
    <workPostalSuburb></workPostalSuburb>
    <workPostalState></workPostalState>
    <workPostalPostCode></workPostalPostCode>
    <workPostalCountry></workPostalCountry>
    <otherTitle></otherTitle>
    <otherFirstName></otherFirstName>
    <otherLastName></otherLastName>
    <otherMobile></otherMobile>
    <otherPhoneAreaCode1></otherPhoneAreaCode1>
    <otherPhone1></otherPhone1>
</ns2:contact>

Example Response:

Status Code: 204 No Content
Cache-Control: max-age=0
Connection: keep-alive
Content-Length: 1738
Content-Type: application/vnd.whispir.contact-v1+xml
Date: Mon, 26 Nov 2012 05:49:12 GMT
Expires: Mon, 26 Nov 2012 05:49:12 GMT
Server: Mashery Proxy
X-Mashery-Responder: javaproxy-au-worker-1.mashery.com
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1

How to delete Contacts in the Company Workspace

Name

Value

Service URL

https://api.whispir.com/contacts?apikey=

Method

DELETE

Request Headers

Authorization

The Base 64 representation of the Whispir Username and Password.

Content-Type

application/vnd.whispir.contact-v1+xml
application/vnd.whispir.contact-v1+json

Query String

apikey=

The Mashery API key to authenticate the request.

Response

204 No Content

The request was accepted and the contact was updated. No data will be returned as it is unncessary

400 Bad Request

The reqest was formatted incorrectly

401 Unauthorized

The authorization details were incorrect

415 Unsupported Media Type

The MIME type requested is not supported for the requested resource

Request/Response Example

After performing this request, the response does not contain any information other than the headers as it is not necessary.

The user has requested to delete a contact, and when the response of 204 is returned, the contact is successfully deleted.

Example Request:

HTTP1.1 DELETE https://api.whispir.com/contacts/124F6B2D46A5A268?apikey=DFD0FD90u809SDF90832FDS
Authorization: Basic asdf98nf89asdvasd2r398h8sdf
Content-Type: application/vnd.whispir.contact-v1+xml

Example Response:

Status Code: 204 No Content
Cache-Control: max-age=0
Connection: keep-alive
Content-Length: 1738
Content-Type: application/vnd.whispir.contact-v1+xml
Date: Mon, 26 Nov 2012 05:49:12 GMT
Expires: Mon, 26 Nov 2012 05:49:12 GMT
Server: Mashery Proxy
X-Mashery-Responder: javaproxy-au-worker-1.mashery.com
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1