CL$WS Host : D5239-staging-cl

cr_controle_camionRequest

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

**cr_controle_camionRequest** Parameters:
Name	Parameter	Data Type	Required
id_controleur	path	string	No
id_tournee	path	string	No
cr_controles_camion	body	List<_cr_controle_camion>	No

**_cr_controle_camion** Parameters:
Name	Parameter	Data Type	Required
id_controleur	form	string	No
id_tournee	form	string	No
id_formulaire	form	string	No
id_type_formulaire	form	string	No
id_type_reponse	form	string	No
value	form	string	No
date	form	string	No

**cr_controle_camionResponse** Parameters:
Name	Parameter	Data Type	Required
id_controleur	form	string	No
id_tournee	form	string	No
cr_controles_camion	form	List<_cr_controle_camion>	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_controle_camion/{id_controleur}/{id_tournee} HTTP/1.1 
Host: freemotion-staging.milliet.paris 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"id_controleur":"String","id_tournee":"String","cr_controles_camion":[{"id_controleur":"String","id_tournee":"String","id_formulaire":"String","id_type_formulaire":"String","id_type_reponse":"String","value":"String","date":"String"}]}

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

{"id_controleur":"String","id_tournee":"String","cr_controles_camion":[{"id_controleur":"String","id_tournee":"String","id_formulaire":"String","id_type_formulaire":"String","id_type_reponse":"String","value":"String","date":"String"}]}