GET | /activities/{Id} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | path | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ActivityId | form | string | No | |
CustomerId | form | string | No | |
OrderId | form | string | No | |
Description | form | string | No | |
AdditionalInformation | form | string | No | |
StartDate | form | DateTime | No | |
DueDate | form | DateTime | No | |
Category | form | ActivityCategory? | No | |
Purpose | form | string | No | |
ContactInformation | form | string | No | |
Type | form | string | No | |
ActionType | form | string | No | |
ActivityType | form | string | No | |
UserGroup | form | string | No | |
Dispatched | form | string | No | |
DispatchDateTime | form | DateTime | No |
Name | Value |
---|---|
Appointment | 1 |
Task | 2 |
Action | 3 |
Event | 4 |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /activities/{Id} HTTP/1.1 Host: azs-stg-lotteries-web.azurewebsites.net Accept: text/jsv
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length { activityId: String, customerId: String, orderId: String, description: String, additionalInformation: String, startDate: 0001-01-01, dueDate: 0001-01-01, category: 0, purpose: String, contactInformation: String, type: String, actionType: String, activityType: String, userGroup: String, dispatched: String, dispatchDateTime: 0001-01-01 }