| All Verbs | /profile |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| query | string | Yes |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/reply/profile HTTP/1.1
Host: app.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<profile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService">
<email>String</email>
<token>String</token>
<tokensecret>String</tokensecret>
</profile>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <AppResponse.ProfileData xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService"> <_x003C_besttime_x003E_k__BackingField>String</_x003C_besttime_x003E_k__BackingField> <_x003C_email_x003E_k__BackingField>String</_x003C_email_x003E_k__BackingField> <_x003C_found_x003E_k__BackingField>String</_x003C_found_x003E_k__BackingField> <_x003C_ownername_x003E_k__BackingField>String</_x003C_ownername_x003E_k__BackingField> <_x003C_phone_x003E_k__BackingField>String</_x003C_phone_x003E_k__BackingField> <_x003C_validtoken_x003E_k__BackingField>String</_x003C_validtoken_x003E_k__BackingField> <_x003C_workphone_x003E_k__BackingField>String</_x003C_workphone_x003E_k__BackingField> </AppResponse.ProfileData>