POST | /servicecontracts/ |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
CIAMId | body | string | No | |
ChassisNumber | body | string | No | |
ItemsPerPage | body | short | No | |
PageNumber | body | short | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Status | form | ReturnStatus | No | |
NumberOfPages | form | short | No | |
Contracts | form | List<Contract> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ReturnCode | form | string | No | |
Message | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ContractNumber | form | string | No | |
StartDate | form | DateTime? | No | |
EndDate | form | DateTime? | No | |
TerminationDate | form | DateTime? | No | |
ServicesSold | form | short | No | |
ServicesTaken | form | short | No | |
Status | form | string | 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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /servicecontracts/ HTTP/1.1
Host: webservices.mbukdatabase.co.uk
Accept: application/json
Content-Type: application/json
Content-Length: length
{"CIAMId":"String","ChassisNumber":"String","ItemsPerPage":0,"PageNumber":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Status":{"ReturnCode":"String","Message":"String"},"NumberOfPages":0,"Contracts":[{"ContractNumber":"String","StartDate":"\/Date(-62135596800000-0000)\/","EndDate":"\/Date(-62135596800000-0000)\/","TerminationDate":"\/Date(-62135596800000-0000)\/","ServicesSold":0,"ServicesTaken":0,"Status":"String"}]}