Support

November 23, 2021 at 10:33 am

Hello!

I have a battle-tested set of scripts I use to bulk upload events using the REST API.

Today I went to use those scripts and the first row in the bulk upload replied with this unusual error regarding REST and invalid dates:

The first part is the JSON data, the second is the REST response.

`

{
“TKT_max”: 1,
“TKT_price”: “290”,
“TKT_required”: “true”,
“TKT_order”: 0,
“TKT_qty”: “12”,
“TKT_name”: “All Sessions”,
“TKT_end_date”: “2022-01-04T17:30:00”,
“TKT_start_date”: “2021-23-05T05:00:00”
}
{
“message”: “Invalid parameter(s): TKT_start_date”,
“code”: “rest_invalid_param”,
“data”: {
“status”: 400,
“params”: {
“TKT_start_date”: “Invalid date.”
},
“details”: {
“TKT_start_date”: {
“message”: “Invalid date.”,
“code”: “rest_invalid_date”,
“data”: null
}
}
}
}

`

I noticed one unusual thing in the newly created event (created using REST API) was that it contained the default ticket that gets added when a new Event is created using the UI! That is a new twist and something unexpected. Maybe that is related to this error? Is is possible that the REST code was changed to make it so that it inserts the default ticket? If this is what happened, how can I turn off this behavior? It is unexpected, to say the least. I would expect the API to create an event without any default ticket.

Thank you!
D