| All Verbs | /Event/Contribution/MyEvents |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Token | query | string | No | |
| UserId | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Data | form | MyEventsGpDto[] | No | |
| Error | form | bool | No | |
| ErrorMessage | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Name | form | string | No | |
| Description | form | string | No | |
| Url | form | string | No | |
| EventFrom | form | DateTime | No | |
| EventTill | form | DateTime | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UID | form | int | 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 /json/reply/MyEventsRequest HTTP/1.1
Host: data.oriem.cz
Content-Type: application/json
Content-Length: length
{"Token":"String","UserId":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Data":[{"Name":"String","Description":"String","Url":"String","EventFrom":"\/Date(-62135596800000-0000)\/","EventTill":"\/Date(-62135596800000-0000)\/","UID":0}],"Error":false,"ErrorMessage":"String"}