BACK TO CONNECTORS

This page is intended to give a high-level technical overview of the PHP Connector v4. To prevent malicious actors from compromising the security of our customer's high-profile sales and registrations, we host our in-depth Connector v4 documentation in private repositories.

If you need more detailed integration documentation than this page offers, connect with one of our technical experts who can understand your use case and determine the optimal setup for your tech stack.

The following diagram shows the Queue-it logic with a server-side Connector.

1. User requests a page.
2. The validation method sees that user has no Queue-it session cookie and no Queue-it token and sends him to the correct waiting room with a valid token based on the configuration.
3. User waits in the queue.
4. User is navigated back to your website, now with a valid token.
5. The validation method validates the token and creates a Queue-it session cookie.
6. The user browses to a new page and the Queue-it session cookie will let him proceed without queuing again.

To integrate using the Queue-it PHP Connector v4, you will need:

• An active Queue-it account
• Queue-it admin available (Someone available with Queue-it GO platform access and familiarity with GO account configuration settings.)
• GitHub Repository Access  (The Queue-it PHP V4 Connector GitHub repository is not available for public access. You need to request access to the repository through your Queue-it representative)
• PHP v7.4 or greater

Complete these steps in order for best results:

1. Install Queue-it PHP Connector
2. Embed Queue-it code in to the application routing logic

Waiting rooms and their protection scope are created and configured in the GO Queue-it Platform and server-side (KnownUser) configuration information must be propagated to the application environment for real-time access by the Queue-it Connector. When an integration configuration is saved (published) in the GO Platform, the server-side configuration settings are packaged into a server-side JSON file and positioned on the Queue-it server, ready for secure downloading.