GeminiHost

EventContributionUpdateRequest

The following routes are available for this service:
All Verbs	/Event/Contribution/Update

**EventContributionUpdateRequest** Parameters:
Name	Parameter	Data Type	Required
Token	query	string	No
UserId	query	int	No
Data	query	EventContributionGpDto	No

**EventContributionGpDto** Parameters:
Name	Parameter	Data Type	Required
Name	form	string	No
Event	form	int	No
ExternalDoctor	form	int	No
Abstract	form	string	No
CoAuthor	form	string	No
Workplace	form	string	No
UrlAttachment	form	string	No
PhotoBase64	form	string	No

**BaseXpoDto** Parameters:
Name	Parameter	Data Type	Required	Description
UID	form	int	No

**EventContributionUpdateReturn** Parameters:
Name	Parameter	Data Type	Required
Data	form	EventContributionGpDto	No
Error	form	bool	No
ErrorMessage	form	string	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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/EventContributionUpdateRequest HTTP/1.1 
Host: data.oriem.cz 
Content-Type: application/json
Content-Length: length

{"Token":"String","UserId":0,"Data":{"Name":"String","Event":0,"ExternalDoctor":0,"Abstract":"String","CoAuthor":"String","Workplace":"String","UrlAttachment":"String","PhotoBase64":"String","UID":0}}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Data":{"Name":"String","Event":0,"ExternalDoctor":0,"Abstract":"String","CoAuthor":"String","Workplace":"String","UrlAttachment":"String","PhotoBase64":"String","UID":0},"Error":false,"ErrorMessage":"String"}