| All Verbs | /photoIdList |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| idcia | query | string | Yes | |
| idproject | query | string | Yes | |
| idtenant | 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/photoIdList HTTP/1.1
Host: app.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<photoIdList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService">
<idcia>String</idcia>
<idproject>String</idproject>
<idtenant>String</idtenant>
<token>String</token>
<tokensecret>String</tokensecret>
</photoIdList>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<AppResponse.ResPhotoIdList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService">
<_x003C_existyn_x003E_k__BackingField>String</_x003C_existyn_x003E_k__BackingField>
<_x003C_found_x003E_k__BackingField>String</_x003C_found_x003E_k__BackingField>
<_x003C_photoList_x003E_k__BackingField>
<AppResponse.ResPhoto>
<_x003C_date_x003E_k__BackingField>String</_x003C_date_x003E_k__BackingField>
<_x003C_idnumber_x003E_k__BackingField>String</_x003C_idnumber_x003E_k__BackingField>
<_x003C_note_x003E_k__BackingField>String</_x003C_note_x003E_k__BackingField>
<_x003C_username_x003E_k__BackingField>String</_x003C_username_x003E_k__BackingField>
</AppResponse.ResPhoto>
</_x003C_photoList_x003E_k__BackingField>
<_x003C_validtoken_x003E_k__BackingField>String</_x003C_validtoken_x003E_k__BackingField>
</AppResponse.ResPhotoIdList>