| GET,OPTIONS | /v1/integrations/{Provider}/runs |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Provider | path | string | No | |
| Top | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Runs | form | List<RunView> | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| At | form | DateTime? | No | |
| Kind | form | string | No | |
| Outcome | form | string | No | |
| Detail | 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.
GET /v1/integrations/{Provider}/runs HTTP/1.1
Host: api.dev.dynamics.trendsic.com
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Runs":[{"At":"0001-01-01T00:00:00.0000000","Kind":"String","Outcome":"String","Detail":"String"}],"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}