| GET | /Common/Dictionary/Cars/{Id} | ||
|---|---|---|---|
| GET | /Common/Dictionary/Cars |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | path | int? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Status | form | ResponseStatus | No | |
| Result | form | List<Car> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ID | form | int | No | |
| Number | form | string | No | |
| Description | form | string | No | |
| DriverId | form | int? | No | |
| CarType | form | int? | 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.
GET /Common/Dictionary/Cars/{Id} HTTP/1.1
Host: apex.nikoratrade.ge
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Status":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}},"Result":[{"ID":0,"Number":"String","Description":"String","DriverId":0,"CarType":0}]}