| GET,OPTIONS | /v1/pm/project/activity |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Uid | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Activities | form | List<PmActivityItem> | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Type | form | string | No | |
| Name | form | string | No | |
| Status | form | string | No | |
| Note | form | string | No | |
| Date | 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/pm/project/activity HTTP/1.1 Host: api.dev.dynamics.trendsic.com Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Activities":[{"Type":"String","Name":"String","Status":"String","Note":"String","Date":"String"}],"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}