| GET | /business-entities/{BeeNumber}/activities/{ActivityId} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BeeNumber | path | decimal | No | |
| ActivityId | path | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Item | form | TEntity | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BeeNumber | form | decimal | No | |
| UserName | form | string | No | |
| ActivityTime | form | DateTime | No | |
| ActivityCode | form | string | No | |
| ClientId | form | string | No | |
| SchemaPrimaryKey | form | string | No | |
| ActivityData | form | string | No |
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 /business-entities/{BeeNumber}/activities/{ActivityId} HTTP/1.1
Host: extensions.avon.ca
Accept: text/jsv
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
item:
{
beeNumber: 0,
userName: String,
activityTime: 0001-01-01T00:00:00,
activityCode: String,
clientId: String,
schemaPrimaryKey: String,
activityData: String
},
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}