| GET | /assignment/reminder |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Result | form | T | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ProfileUserId | form | uint | No | |
| Schedule | form | string | No | |
| Notify | form | bool | No | |
| NotificationConfigId | form | ulong | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| CreatedById | form | uint | No | |
| ModifiedById | form | uint | No | |
| CreatedDate | form | DateTime | No | |
| ModifiedDate | form | DateTime | No | |
| Id | form | uint | 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 /assignment/reminder HTTP/1.1 Host: api.chmuradokumentow.pl Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"result":{"profileUserId":0,"schedule":"String","notify":false,"notificationConfigId":0,"createdById":0,"modifiedById":0,"createdDate":"0001-01-01T00:00:00.0000000Z","modifiedDate":"0001-01-01T00:00:00.0000000Z","id":0}}