TicketUserServices

<back to all web services

TransferTicketToEventRequest

Requires Authentication
Requires any of the roles:Admin, TeamAdminRequires the permission:ReadData
The following routes are available for this service:
POST/TransferTicketToEventTransfer a ticket to a different event with automatic price reconciliation
TransferTicketToEventRequest Parameters:
NameParameterData TypeRequiredDescription
TicketTokenIdbodystringNo
ToEventIdbodyintNo
UserIdbodyint?No
ReasonbodystringNo
IdempotencyKeybodystringNo
ExpectedPriceDifferencebodydecimalNo
ToOwnerTicketTypeIdbodyint?No
ToSeriesTicketTypeIdbodyint?No
ToSeatIdbodyint?No
TransferTicketToEventResult Parameters:
NameParameterData TypeRequiredDescription
OkformboolNo
StatusCodeformintNo
CodeformstringNo
MessageformstringNo
TransferLogIdformint?No
NewTicketTokenIdformstringNo
DirectionformstringNo
PriceDifferenceformdecimal?No
OriginalTicketPriceformdecimal?No
TargetTicketPriceformdecimal?No
SourceEventPaidOutformbool?No
OutstandingCostHandledByServerformbool?No
RefundformTransferRefundInstructionNo
TopupformTransferTopupInstructionNo
QuoteformTransferTicketQuoteResultNo
TransferRefundInstruction Parameters:
NameParameterData TypeRequiredDescription
AmountIskformdecimalNo
PaymentReferenceformstringNo
InstructionformstringNo
TransferTopupInstruction Parameters:
NameParameterData TypeRequiredDescription
AmountIskformdecimalNo
PaymentLinkUrlformstringNo
SessionTokenformstringNo
ExpiresAtformDateTime?No
TransferTicketQuoteResult Parameters:
NameParameterData TypeRequiredDescription
OkformboolNo
StatusCodeformintNo
CodeformstringNo
MessageformstringNo
FromformTransferQuoteEventSideNo
ToformTransferQuoteEventSideNo
PriceDifferenceformdecimalNo
DirectionformstringNo
RefundableViaBorgunformboolNo
AfterPayoutformboolNo
TransferQuoteEventSide Parameters:
NameParameterData TypeRequiredDescription
EventIdformintNo
EventNameformstringNo
TimeOfEventformDateTime?No
TicketPriceformdecimalNo
PaymentMethodIdformstringNo
PaymentReferenceformstringNo
AvailableSeatsformint?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 /TransferTicketToEvent HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	ticketTokenId: String,
	toEventId: 0,
	userId: 0,
	reason: String,
	idempotencyKey: String,
	expectedPriceDifference: 0,
	toOwnerTicketTypeId: 0,
	toSeriesTicketTypeId: 0,
	toSeatId: 0
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	ok: False,
	statusCode: 0,
	code: String,
	message: String,
	transferLogId: 0,
	newTicketTokenId: String,
	direction: String,
	priceDifference: 0,
	originalTicketPrice: 0,
	targetTicketPrice: 0,
	sourceEventPaidOut: False,
	outstandingCostHandledByServer: False,
	refund: 
	{
		amountIsk: 0,
		paymentReference: String,
		instruction: String
	},
	topup: 
	{
		amountIsk: 0,
		paymentLinkUrl: String,
		sessionToken: String,
		expiresAt: 0001-01-01
	},
	quote: 
	{
		ok: False,
		statusCode: 0,
		code: String,
		message: String,
		from: 
		{
			eventId: 0,
			eventName: String,
			timeOfEvent: 0001-01-01,
			ticketPrice: 0,
			paymentMethodId: String,
			paymentReference: String,
			availableSeats: 0
		},
		to: 
		{
			eventId: 0,
			eventName: String,
			timeOfEvent: 0001-01-01,
			ticketPrice: 0,
			paymentMethodId: String,
			paymentReference: String,
			availableSeats: 0
		},
		priceDifference: 0,
		direction: String,
		refundableViaBorgun: False,
		afterPayout: False
	}
}