| POST,OPTIONS | /v1/dispatch/public/pickup/{SchedulerUrl}/quote |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SchedulerUrl | path | string | No | |
| Zone | body | string | No | |
| Bags | body | int | No | |
| Needs | body | List<string> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Zone | form | string | No | |
| Bags | form | int | No | |
| Fare | form | decimal | No | |
| ResponseStatus | form | ResponseStatus | 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 /v1/dispatch/public/pickup/{SchedulerUrl}/quote HTTP/1.1
Host: api.dev.dynamics.trendsic.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"SchedulerUrl":"String","Zone":"String","Bags":0,"Needs":["String"]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Zone":"String","Bags":0,"Fare":0,"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}