TicketUserServices

<back to all web services

TicketHoldReleaseRequest

The following routes are available for this service:
POST/ticketHold/release
TicketHoldReleaseRequest Parameters:
NameParameterData TypeRequiredDescription
ReservationTokenIdbodystringNo
RequestUnixUTCTimeStampbodylongNo
SignaturebodyRequestSignatureNo
RequestSignature Parameters:
NameParameterData TypeRequiredDescription
SystemIdformstringNo
SystemSecretformstringNo
SignatureformstringNo
TicketHoldResult Parameters:
NameParameterData TypeRequiredDescription
StatusCodeformintNo
MessageformstringNo
ReservationTokenIdformstringNo
ExpiresUtcformDateTime?No
LinesformList<CategoryHoldLine>No
PerCategoryformList<CategoryAvailability>No
ScarcityformboolNo
CategoryHoldLine Parameters:
NameParameterData TypeRequiredDescription
EventSeriesTicketTypeformint?No
EventSeriesOwnerTicketTypeformint?No
QuantityformintNo
CategoryAvailability Parameters:
NameParameterData TypeRequiredDescription
EventSeriesTicketTypeformint?No
EventSeriesOwnerTicketTypeformint?No
MaxTicketsformint?No
RemainingformintNo

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 /ticketHold/release HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	reservationTokenId: String,
	requestUnixUTCTimeStamp: 0,
	signature: 
	{
		systemId: String,
		systemSecret: String,
		signature: String
	}
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	statusCode: 0,
	message: String,
	reservationTokenId: String,
	expiresUtc: 0001-01-01,
	lines: 
	[
		{
			eventSeriesTicketType: 0,
			eventSeriesOwnerTicketType: 0,
			quantity: 0
		}
	],
	perCategory: 
	[
		{
			eventSeriesTicketType: 0,
			eventSeriesOwnerTicketType: 0,
			maxTickets: 0,
			remaining: 0
		}
	],
	scarcity: False
}