TicketUserServices

EventSeatingMoveConfirmedSeatsRequest

**Requires Authentication**
Requires any of the roles:	Admin, TeamAdmin	Requires the permission:	ReadData

The following routes are available for this service:
POST	/EventSeatingMoveConfirmedSeats

**EventSeatingMoveConfirmedSeatsRequest** Parameters:
Name	Parameter	Data Type	Required
EventId	body	int	No
Moves	body	List<MoveConfirmedSeatPair>	No
AllowCrossSection	body	bool	No
Reason	body	string	No
RequestUnixUTCTimeStamp	body	long	No
Signature	body	RequestSignature	No

**MoveConfirmedSeatPair** Parameters:
Name	Parameter	Data Type	Required	Description
FromSeatId	form	int	No
ToSeatId	form	int	No

**RequestSignature** Parameters:
Name	Parameter	Data Type	Required
SystemId	form	string	No
SystemSecret	form	string	No
Signature	form	string	No

**EventSeatingMoveConfirmedSeatsResult** Parameters:
Name	Parameter	Data Type	Required
StatusCode	form	int	No
Message	form	string	No
MovedSeatIds	form	List<int>	No
Failures	form	List<MoveConfirmedSeatFailure>	No

**MoveConfirmedSeatFailure** Parameters:
Name	Parameter	Data Type	Required
FromSeatId	form	int	No
ToSeatId	form	int	No
Reason	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 /EventSeatingMoveConfirmedSeats HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"eventId":0,"moves":[{"fromSeatId":0,"toSeatId":0}],"allowCrossSection":false,"reason":"String","requestUnixUTCTimeStamp":0,"signature":{"systemId":"String","systemSecret":"String","signature":"String"}}

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

{"statusCode":0,"message":"String","movedSeatIds":[0],"failures":[{"fromSeatId":0,"toSeatId":0,"reason":"String"}]}