| GET,POST | /ActivityStatement | Generate activity statement for client | Generate activity statement for client as part of compliance requirement |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| DocumentName | body | string | Yes | Activity Statement Name |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Data | form | ActivityStatement | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ErrorNo | form | int | No | |
| Message | form | string | No | |
| Identity | form | long? | No | |
| ErrorSource | form | string | No | |
| DisplayOnUI | form | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ClientId | form | int | No | |
| FileName | form | string | No | |
| Bytes | form | byte[] | 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 /ActivityStatement HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"DocumentName":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Data":{"ClientId":0,"FileName":"String","Bytes":"AA=="},"ErrorNo":0,"Message":"String","Identity":0,"ErrorSource":"String","DisplayOnUI":false}