CL$WS Host : D5239-staging-cl

cr_photoRequest

The following routes are available for this service:
GET, POST	/cr_photo/{id_cr}/{id_tournee}

**cr_photoRequest** Parameters:
Name	Parameter	Data Type	Required
id_cr	path	string	No
id_tournee	path	string	No
multi_photos	body	List<_cr_photo>	No

**_cr_photo** Parameters:
Name	Parameter	Data Type	Required
id_cr	form	string	No
id_tournee	form	string	No
num_facture	form	string	No
type	form	int	No
index	form	int	No
path	form	string	No
photo	form	string	No
photo_light	form	string	No
date	form	string	No
latitude	form	double	No
longitude	form	double	No

**cr_photoResponse** Parameters:
Name	Parameter	Data Type	Required
id_cr	form	string	No
id_tournee	form	string	No
multi_photos	form	List<_cr_photo>	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /cr_photo/{id_cr}/{id_tournee} HTTP/1.1 
Host: freemotion-staging.milliet.paris 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"id_cr":"String","id_tournee":"String","multi_photos":[{"id_cr":"String","id_tournee":"String","num_facture":"String","type":0,"index":0,"path":"String","photo":"String","photo_light":"String","date":"String","latitude":0,"longitude":0}]}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"id_cr":"String","id_tournee":"String","multi_photos":[{"id_cr":"String","id_tournee":"String","num_facture":"String","type":0,"index":0,"path":"String","photo":"String","photo_light":"String","date":"String","latitude":0,"longitude":0}]}