Support

Home Forums Event Espresso Premium Wrong tickets_left Value in API

Wrong tickets_left Value in API

Posted: April 10, 2013 at 1:16 pm

Viewing 7 reply threads


Adam Harris

April 10, 2013 at 1:16 pm

I have an event set up with Multi Event Registration Plugin and I’m using the Version 2.0.1.B. Each time is set to allow 3 registrants.

But when I look at the API I see this:
"Datetimes": [
{
"id": 197,
"is_primary": true,
"event_start": "2013-04-14 15:30:00",
"event_end": "2013-04-14 16:00:00",
"registration_start": "2013-03-29 12:01:00",
"registration_end": "2013-04-10 23:59:00",
"limit": 18,
"tickets_left": 6
},
{
"id": 196,
"is_primary": true,
"event_start": "2013-04-14 15:00:00",
"event_end": "2013-04-14 15:30:00",
"registration_start": "2013-03-29 12:01:00",
"registration_end": "2013-04-10 23:59:00",
"limit": 18,
"tickets_left": 6
},
I should see that the limit is 3 and tickets left should be 0, 1, 2, or 3. (In this case, 0, because these time slots are filled. Is there anything I could be doing wrong? or is this a bug?


Josh

  • Support Staff

April 11, 2013 at 10:31 am

Hi Adam,

I’ll ping the developer to API to check on this. It might be good to know what the overall attendee limit is set to for the event you’re referring to.


Michael Nelson

  • Support Staff

April 11, 2013 at 10:47 am

Hi Adam. Given the part of the API output you’ve posted, it looks like you’ve actually just added another time for the event, not another occurrence of the event. (And it actually appears you set the limit to 18, distributed between 6 times.)
I believe you clicked ‘Add Additional Time’ to the event, instead of ‘Is this a recurring event?’ (see screenshot)
If you add recurrences of the event, I think that will give you the behaviour you’re wanting: different instances of the event each with their own ticket limit (eg, each event has a limit of 3 attendees for 6 different times), not one single event with a shared ticket limit (eg, there is a limit of 18 attendees distributed amongst the 6 different times).
Does that help?


Adam Harris

April 11, 2013 at 11:22 am

the overall attendee limit is 18


Adam Harris

April 11, 2013 at 11:42 am

I have  just added another time for the event, which is what I want. When I add additional times, there is a place to put Qty for that time. So I put 3 in all six time slots because there are 3 interview slots at each time. Is there a way with the API to see how many slots are still available at each time?


Adam Harris

April 15, 2013 at 7:41 am

Michael,

You’re correct. That’s what I did. I clicked “Add Additional Time”, but when I did that there is a Qty for each time slot. Does this not mean the number of tickets per time slot? Here is a screenshot to show what I did and that I put 3 in the Qty for each time slot.


Adam Harris

April 26, 2013 at 3:06 pm

Any update on this? Am I wrong in my assumption that the tickets_left value for each time slot should be the same as the Qty from each time slot, or at least the number of tickets that remain for that slot?


Michael Nelson

  • Support Staff

April 29, 2013 at 2:59 pm

Hi Adam, sorry I wasn’t getting notified of your follow-up posts.
I investigated further and found it’s a bug. Tickets left should be equal to the ‘Qty’ field on the time MINUS tickets sold at that time.
I’ve just updated the beta version and will be releasing the fix soon.

Viewing 7 reply threads

The support post ‘Wrong tickets_left Value in API’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso