Update an eventCopy Pageput https://{hostname}/events/v3/events/{eventId}Updates the specified event.Path ParamseventIdintegerrequiredThe identifier of the event.Query ParamsaccountSwitchKeystringFor customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.Body ParamsContains information about the request body parameters that you can specify when updating an event. It also includes tags and objects that you can associate with an event.audienceLocationsarray of stringslength ≤ 20Two-letter ISO 3166 country codes that indicate geographic areas of audiences. This array can contain up to 20 unique items.audienceLocationsADD stringaudienceSizeintegerThe audience's size for the event. The minimum value is 1.coordinatorsarray of stringslength ≤ 20Up to 20 Control Center usernames of those who serve as the event's coordinators.coordinatorsADD stringcustomerEventIdstringThe user-specified ID for the event. This ID can be up to 100 characters long. Customer Event ID.descriptionstringThe description of the event. This description can be up to 2000 characters long.enddate-timerequiredAn ISO 8601 timestamp indicating the end date of the event.namestringrequiredlength between 1 and 750The name of the event. This name can be up to 750 characters long.objectsarray of objectsObjects associated with the event. This array can include only unique items.objectsADD objectstartdate-timerequiredAn ISO 8601 timestamp indicating the start date of the event.tagsarray of stringslength ≤ 20Tags for the event. Each tag can be up to 100 characters long. This array can contain up to 20 unique items.tagsADD stringversionintegerrequiredThe version of the event. Use the version of the event sent in the original server's response. See Event Version.HeadersacceptstringenumDefaults to application/jsonGenerated from available response content typesapplication/jsonapplication/problem+jsonAllowed:application/jsonapplication/problem+jsonResponses 200Successful response. 400Bad request. Invalid request. Details may be available in the response body. 403Forbidden. Insufficient permissions to access event or associated objects. 404Not found. The requested event wasn't found. 409Conflict. The event was modified after you retrieved it. Please refetch the event, reconcile possible differences and resubmit the request.Updated 13 days ago