Update specific Ticket Type
PUT/ticket/:guid
Update a specific Ticket Type.
Request
Path Parameters
The guid of the Ticket Type.
- application/json
Body
Input data
Possible values: <= 255 characters
The name of the Ticket Type.
Possible values: <= 65536 characters
The description for the Ticket Type.
Possible values: <= 999999
The minimum price of this Ticket Type in cents, overwrites the mandatory Product Type prices.
Possible values: <= 100
The VAT percentage which applies to this Ticket Type. This is a float with at most 2 decimals, because VAT percentages in some countries have fractions of a percent.
Whether the Metadata within the Ticket Type can be LatePersonalized. When true Metadata is not asked in Shop but before download.
Possible values: [auto
, sold_out
]
One can overwrite the status for a Ticket Type here.
Possible values: [EventProtect
, RefundProtect
, RandomNumberGenerator
, PlayPass
, Co2Compensate
, Giro555
]
Which class the Ticket Type needs to trigger after for example a Payment.
Possible values: >= 1
Default value: 1
The Ticket Type can only be ordered in groups of this size, i.e. the count of ordered Ticket Types needs to be exactly divisible by this number. This should be less or equal to min_orderable_amount_per_order.
The start of the availability range for this Ticket Type. Has to be set when available_until is set.
The end of the availability range for this Ticket Type. Has to be set when available_from is set.
Possible values: <= 999999999
Default value: 0
The margin for which the Ticket Type will show-up (with countdown for example) in the Shop.
Possible values: >= 1
Default value: 1
Specifies the minimum number of Ticket Types a visitor can select within one Order. This should be less or equal to max_orderable_amount_per_order.
Possible values: <= 250
Default value: 20
Specifies the maximum number of Ticket Types a visitor can select within one Order. This should be greater or equal to min_orderable_amount_per_order.
Possible values: <= 100
Default value: 0
How many fees will be in the Ticket Type.
Possible values: <= 255
The category key from the Chart where the Ticket Type should be applied to (see Seats.io).
Whether to hide this Ticket Type when no Coupon is used.
Default value: true
Whether to combine the Products into the Ticket Type price or not. If false, Products show up separately on the receipt/invoices.
Default value: true
Whether it is possible to swap the Ticket Type.
The time it was created.
The time it was last updated.
Responses
- 200
- 403
- 404
- 406
Ticket Type updated.
- application/json
- Schema
- Example (from schema)
Schema
The guid of the the Ticket Type.
The guid of the Company associated with the Ticket Type.
The guid of the Event associated with the Ticket Type.
Possible values: <= 255 characters
The name of the Ticket Type.
Possible values: <= 65536 characters
The description for the Ticket Type.
Possible values: <= 999999
The minimum price of this Ticket Type in cents, overwrites the mandatory Product Type prices.
Possible values: <= 100
The VAT percentage which applies to this Ticket Type. This is a float with at most 2 decimals, because VAT percentages in some countries have fractions of a percent.
Whether the Metadata within the Ticket Type can be LatePersonalized. When true Metadata is not asked in Shop but before download.
Possible values: [auto
, sold_out
]
One can overwrite the status for a Ticket Type here.
Possible values: [EventProtect
, RefundProtect
, RandomNumberGenerator
, PlayPass
, Co2Compensate
, Giro555
]
Which class the Ticket Type needs to trigger after for example a Payment.
Possible values: >= 1
Default value: 1
The Ticket Type can only be ordered in groups of this size, i.e. the count of ordered Ticket Types needs to be exactly divisible by this number. This should be less or equal to min_orderable_amount_per_order.
The start of the availability range for this Ticket Type. Has to be set when available_until is set.
The end of the availability range for this Ticket Type. Has to be set when available_from is set.
Possible values: <= 999999999
Default value: 0
The margin for which the Ticket Type will show-up (with countdown for example) in the Shop.
Possible values: >= 1
Default value: 1
Specifies the minimum number of Ticket Types a visitor can select within one Order. This should be less or equal to max_orderable_amount_per_order.
Possible values: <= 250
Default value: 20
Specifies the maximum number of Ticket Types a visitor can select within one Order. This should be greater or equal to min_orderable_amount_per_order.
Possible values: <= 100
Default value: 0
How many fees will be in the Ticket Type.
Possible values: <= 255
The category key from the Chart where the Ticket Type should be applied to (see Seats.io).
Whether to hide this Ticket Type when no Coupon is used.
Default value: true
Whether to combine the Products into the Ticket Type price or not. If false, Products show up separately on the receipt/invoices.
Default value: true
Whether it is possible to swap the Ticket Type.
The time it was created.
The time it was last updated.
Whether a Ticket Type is available in Cashr.
Possible values: [sold_out
, not_sold_right_now
, available
]
The sale status of the Ticket Type.
Whether a Ticket Type is seated or not.
Whether to include the service costs into the price.
{
"guid": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"company_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"event_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"name": "string",
"description": "string",
"min_price": 0,
"vat_percentage": 0,
"late_personalization": true,
"status_overrule": "auto",
"class": "EventProtect",
"increment": 1,
"available_from": "2023-08-01T14:40:24+00:00",
"available_until": "2023-08-01T14:40:24+00:00",
"availability_margin": 0,
"min_orderable_amount_per_order": 1,
"max_orderable_amount_per_order": 20,
"seats_category_key": 0,
"hide_without_coupon": false,
"combines_products": true,
"swappable": true,
"created_at": "2023-08-01T14:40:24+00:00",
"updated_at": "2023-08-01T14:40:24+00:00",
"status": "sold_out",
"seated": true
}
Unauthorized. You do not have permission to manage the Ticket Type.
- application/json
- Schema
- Example (from schema)
Schema
The general error code.
The exact reason of failure.
{
"error_code": "string",
"error_description": "string"
}
Ticket not found.
- application/json
- Schema
- Example (from schema)
Schema
The general error code.
The exact reason of failure.
{
"error_code": "string",
"error_description": "string"
}
Request is invalid, see error context for validation errors.
- application/json
- Schema
- Example (from schema)
Schema
The general error code.
The exact reason of failure.
{
"error_code": "string",
"error_description": "string"
}