LocalizeLTU Documentation
LocalizeLTU
Draft documentation version
Documentation is partial and not validated !
Description
Version | V1 |
---|---|
Require User context | |
Authorization | |
Errors | BadLocalization NotExist |
Request
Route
Parameters
Parameter | Required | Sample | Description |
---|---|---|---|
InfrastructureID | 8 | ID of Site, Building or Zone | |
LTUID | 5 | ID of LTUBase | |
WAC | WAC123456789012 | Code of BusinessAccount | |
LocaliseRelatedEntities | true |
Connected Flux and ReflectionBase will be localized if |
Remarks
- To override Content-type in your clients HTTP Accept Header, append the
.csv
suffix or?format=csv
- To embed the response in a jsonp callback, append
?callback=myCallback
Post Data sample
POST /csv/reply/LocalizeLTU HTTP/1.1
Host: localhost
Content-Type: text/csv
Content-Length: length
LTUID,InfrastructureID,LocaliseRelatedEntities,WAC
0,0,False,String
cURL command sample
curl -k -H "Authorization: Bearer [YOUR_ACCESS_TOKEN]" -H "Content-Type:application/csv" -X PATCH -d @filename.csv https://api.wit-datacenter.com/WAC123456789012/LTU/5/Localize/8
Remark
@filename.csv
contain your request parameters serialized in CSV as described in Post Data sample bottom
Response
Returned Entity
Localized LTUBase on new InfrastructureBaseCSV Sample
HTTP/1.1 200 OK Content-Type: text/csv Content-Length: length {Unable to show example output for type 'LTUBaseDto' using the custom 'csv' filter}Impossible de créer une classe abstraite.