Discussions

When I sent a request to `GET https://api.boomset.com/events/123/guests?load_start=2023-01-10T14%3A33%3A14&page=2&page_size=250` I get back a JSON response that starts: ```json { "count": 535, "next": "https://api.boomset.com/rest/events/123/guests?load_start=2023-01-10T14%3A33%3A14&page=3&page_size=250", "previous": "https://api.boomset.com/rest/events/123/guests?load_start=2023-01-10T14%3A33%3A14&page=1&page_size=250", "results": [ ] } ``` The `next` and `previous` URLs in the response include a `/rest` path fragment, which shouldn't be there. Sending a GET request to either of these URLs returns a 404 Not Found (with an HTML "Oops..." page) Is this a bug in the API?

Here is our sample code $data = array('event_id'=>'121429','data'=>array('id'=>'121429','name'=>'test')); $client = new \GuzzleHttp\Client(); $settings = parse_ini_file($_SERVER["DOCUMENT_ROOT"]."/config.ini"); try { $response = $client->request('PUT', 'https://api.boomset.com/events/'.$data['event_id'], [ 'body' => json_encode($data['body']), 'headers' => [ 'accept' => 'application/json', 'content-type' => 'application/json', 'Authorization' =>'Token '.$settings['authorization'] ] ]); echo $response->getBody(); } catch (Exception $ex) { echo json_encode($response); } We are getting a null response

Using framework 4.6.1 with TLS1.2 I have integrated RestSharp with Zoom, but not with boomset. I've exhausted my online search for code adjustments. Here is where I have left off: System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12; var client = new RestClient("https://api.boomset.com/groups"); var certFile = "C:\\\\iMIS\\Godaddy2022.pfx"; System.Security.Cryptography.X509Certificates.X509Certificate2 certificate = new System.Security.Cryptography.X509Certificates.X509Certificate2(certFile, "password"); client.ClientCertificates = new System.Security.Cryptography.X509Certificates.X509CertificateCollection() { certificate }; client.Proxy = new WebProxy(); var request = new RestRequest(Method.GET); request.AddHeader("Accept", "*/*"); request.AddHeader("Accept-Encoding", "gzip, deflate, br"); request.AddHeader("Connection", "keep-alive"); request.AddHeader("Authorization", "Token 8a22d14aedda9620bcb3d91ab927d5b0"); request.AddHeader("Cache-Control", "no-cache"); request.RequestFormat = DataFormat.Json; IRestResponse response = client.Execute(request);

Event has 2 tracks, and need to know if they attended the 1st or 2nd track for that time slot. The guests know to scan their barcode when entering the session room so that it will print on their continuing education certificate. I've looked at the Session detail and guest detail, but it is not apparent to me where actual session attendance is stored.

We need kiosk badge printing and event checkin functionality. Would you provide us, without saving data on boomset account?

I know that you guys can print badges, can we update the QR codes via your API so that we can use our own QR code and update them directly from registration.

It looks like many pieces of event data can be created via your API. Is it possible to populate sessions via the API also?

We have 2 different posts: sending ticket and sending registration confirmation. Why links are the same, but only with different params? Links: https://www.boomset.com/restapi/reservation/settings/:reservationID/send_ticket https://www.boomset.com/restapi/reservation/settings/:registration_id/send_ticket

I noticed a thread here on support asking about a Zapier integration, to which you said no - but, your website says you have by displaying the Zapier logo on the front page. Has something changed since June 16th? Is this something you are actively working on? Thank you.

Is is feasible for me to use the API to push event data to a Boomset account? Looking at the videos I can see, sites like Eventbrite and Meetup have a direct way to import from the boomset interface. Is it possible for me to accomplish the same action from my own interface by asking for credentials or? Thanks for your patience with my non-technical mind.