RequestAuthorization Documentation
RequestAuthorization
Draft documentation version
Documentation is partial and not validated !
Description
Version | Alpha |
---|---|
Require User context | |
Authorization | |
Errors |
Request
Route
Parameters
Parameter | Required | Sample | Description |
---|---|---|---|
AccountID | 2 | ID of BusinessAccount or Organization |
Remarks
- To override Content-type in your clients HTTP Accept Header, append the
.xml
suffix or?format=xml
- To embed the response in a jsonp callback, append
?callback=myCallback
Post Data sample
POST /xml/reply/RequestAuthorization HTTP/1.1
Host: localhost
Content-Type: application/xml
Content-Length: length
<RequestAuthorization xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/WIT.DataCenter.DTOs.Request">
<AccountID>0</AccountID>
</RequestAuthorization>
cURL command sample
curl -k -H "Authorization: Bearer [YOUR_ACCESS_TOKEN]" -H "Content-Type:application/xml" -X POST -d @filename.xml https://api.wit-datacenter.com/Authorization
Remark
@filename.xml
contain your request parameters serialized in XML as described in Post Data sample bottom
Response
Returned Entity
Requested AuthorizationXML Sample
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <Authorization xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://api.wit-datacenter.com/"> <AccountID>0</AccountID> <CreationDate>0001-01-01T00:00:00</CreationDate> <RolesStatus> <RoleStatus> <ID>0</ID> <RoleID>0</RoleID> <Status>NotValidated</Status> </RoleStatus> </RolesStatus> <UpdateDate>0001-01-01T00:00:00</UpdateDate> <User> <ID>0</ID> <Name>String</Name> <Picture>00000000-0000-0000-0000-000000000000</Picture> <CultureID>0</CultureID> <Mail>String</Mail> <ReferenceKey>00000000-0000-0000-0000-000000000000</ReferenceKey> </User> </Authorization>