Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 JSON API help to do a single registration with multiple tickets | Event Espresso - Staging Server
Trying to figure out the format of a JSON POST to create a registration for a single attendee, with multiple “tickets types” for a single event, which would subsequently create multiple ticket printouts, or possibly just create multiple registrations with a single ticket each for a single attendee (multiple ways to accomplish this)
Any assistance or thoughts on what I might be missing? or can anyone point me in the right direction?
I’m Running Version 3.1.32.2.P and the JSON API Version 2.0
In EE 3.1, each attendee has a single price type associated with it. This means that if you are adding X tickets of price type A, and Y tickets of price type B, you will need to do 2 seperate requests to the add attendee method (http://staging.eventespresso.com/wiki/api-addon/#POST.2FPUT_.2Fregistrations), even if you are repeating the attendee information.
This has been redesigned in the upcoming 4.0 release, where attendees, registrations and transactions are all seperated. So a single attendee can be associated with multiple ticket types, multiple events, etc.
Viewing 1 reply thread
The support post ‘JSON API help to do a single registration with multiple tickets’ 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.