The product to edit is identified by the
id field in the request body, not by
the {id} segment in the URL path.Authorization
Example:
Authorization | Bearer Paste-Your-API-Key-HereRequest Body
Unique identifier of the event product to edit. This is read from the request
body.
Event product name.
Event product description in text or HTML format.
Event ticket or product price amount.
Crossed-out price displayed as the original price.
Event URL, such as an online meeting link.
URL where the customer will be redirected after completing payment.
Event product expiration date in ISO 8601 format.
Additional event details.
event Structure (Object)
Event location or address.
Indicates whether the event is conducted online.
Maximum number of tickets that can be purchased per transaction.
Response
Successful ResponseMain Structure (Root)
Status code from API.
Status message that describes the status code.
The updated event product data.
data Structure (Object)
Unique identifier of the event product.
Public URL of the updated event product.
Errors
When the request body fails validation, this endpoint still responds with HTTP
200 but sets messages to failed and returns the validator errors in
data: { "statusCode": 200, "messages": "failed", "data": { ... } }.Returned when the product does not belong to the authenticated account:
{ "statusCode": 401, "messages": "Unauthorized" }.Returned when the product does not exist:
{ "statusCode": 404, "messages": "Product not found" }.