TicketUserServices

EventOwnerOutstandingCreateRequest

**Requires Authentication**
Requires the role:	Admin

The following routes are available for this service:
POST	/eventowner/{EventOwnerId}/outstanding

**EventOwnerOutstandingCreateRequest** Parameters:
Name	Parameter	Data Type	Required
EventOwnerId	path	int	No
Amount	body	long	No
Reason	body	string	No
RelatedEventId	body	int?	No
RelatedTicketId	body	int?	No

**EventOwnerOutstandingResult** Parameters:
Name	Parameter	Data Type	Required
Item	form	EventOwnerOutstanding	No
StatusCode	form	int	No
Message	form	string	No

**EventOwnerOutstanding** Parameters:
Name	Parameter	Data Type	Required
Id	form	int	No
EventOwnerId	form	int	No
Amount	form	long	No
Reason	form	string	No
RelatedEventId	form	int?	No
RelatedTicketId	form	int?	No
AppliedToEventPayoutId	form	int?	No
CreatedAt	form	DateTime	No
AppliedAt	form	DateTime?	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 /eventowner/{EventOwnerId}/outstanding HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"eventOwnerId":0,"amount":0,"reason":"String","relatedEventId":0,"relatedTicketId":0}

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

{"item":{"id":0,"eventOwnerId":0,"amount":0,"reason":"String","relatedEventId":0,"relatedTicketId":0,"appliedToEventPayoutId":0,"createdAt":"0001-01-01T00:00:00.0000000","appliedAt":"0001-01-01T00:00:00.0000000"},"statusCode":0,"message":"String"}