Overview
The following steps will walk you through how to troubleshoot 3rd party Kiosk Integrations.
Checking Standard Configuration
Verify the Kiosk API user is active in ACME Backoffice and has the proper permissions
Confirm the event is available for sale in the Events List
Ensure the event and ticket types are available for sale at the Kiosk sale channel
Republish the Event Template to ensure there are events available
Review ACME API Status
Confirm Proper ACME API Activity
Please note that many of the APIs used in each module (B2B, B2C, POS, Kiosk) are shared so generally, you would have an API outage on all sales channels, not just one.
Check the online ticketing portal to see if it is working properly
Check B2B and POS to ensure tickets can be sold
Check connectivity from Kiosks to ACME APIs
Eliminate Network Issues
The following command prompt will eliminate network issues and ensure that the workstation is connected to ACME. It will confirm that the connections and endpoints are active and returning responses as expected.
curl -w "%{time_total}\n" "https://api.acmeticketing.com/v1/b2b/health"
curl -w "%{time_total}\n" "https://api.acmeticketing.com/v1/b2c/health"
curl "https://api.acmeticketing.com/v2/b2b/event/instances?startTime=2019-05-01T12:14:31&endTime=2019-05-02T00:00:00&saleChannel=Kiosk" | python -m json.tool
curl "https://api.acmeticketing.com/v2/b2b/checkout/kios -H "Content-Type:Application/JSON”
The first two commands will return Ok with a number and the last two commands will return a message that says “session required.” These responses will let you know that your network is able to connect to our APIs and our APIs are responding.
If the Kiosk is configured correctly and the API is responding properly, there is an issue with the Kiosk code.