TicketUserServices

<back to all web services

TransferTargetTicketTypesRequest

Requires Authentication
Requires any of the roles:Admin, TeamAdminRequires the permission:ReadData
The following routes are available for this service:
POST/transferTicket/targetTicketTypesList all ticket types available on the target event with price diff vs source
TransferTargetTicketTypesRequest Parameters:
NameParameterData TypeRequiredDescription
TicketTokenIdbodystringNo
ToEventIdbodyintNo
SectionIdbodyint?No
TransferTargetTicketTypesResult Parameters:
NameParameterData TypeRequiredDescription
OkformboolNo
StatusCodeformintNo
CodeformstringNo
MessageformstringNo
SourceTicketPriceformdecimalNo
SourceTicketTypeNameformstringNo
OptionsformList<TransferTargetTicketTypeOption>No
TransferTargetTicketTypeOption Parameters:
NameParameterData TypeRequiredDescription
OwnerTicketTypeIdformint?No
SeriesTicketTypeIdformint?No
NameformstringNo
PriceformdecimalNo
DirectionformstringNo
PriceDifferenceformdecimalNo
NameMatchesSourceformboolNo
BlockTransferformboolNo
HiddenformboolNo
MaxTicketsformint?No
TicketsSoldformint?No
TicketsLeftformint?No

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

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

POST /transferTicket/targetTicketTypes HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	ticketTokenId: String,
	toEventId: 0,
	sectionId: 0
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	ok: False,
	statusCode: 0,
	code: String,
	message: String,
	sourceTicketPrice: 0,
	sourceTicketTypeName: String,
	options: 
	[
		{
			ownerTicketTypeId: 0,
			seriesTicketTypeId: 0,
			name: String,
			price: 0,
			direction: String,
			priceDifference: 0,
			nameMatchesSource: False,
			blockTransfer: False,
			hidden: False,
			maxTickets: 0,
			ticketsSold: 0,
			ticketsLeft: 0
		}
	]
}