Documentation Index
Fetch the complete documentation index at: https://docs.qflowhub.io/llms.txt
Use this file to discover all available pages before exploring further.
OAuth 2.0 access token issued by https://identity.qflowhub.io/core. Include as Authorization: Bearer <token>. See the Authentication guide for the token flow.
Your APIM subscription key. Sent in the welcome email when your account is enabled. Required on every request alongside the bearer token.
The ID of the event to return guests for
OK
The ID of the guest (This should be a GUID)
The first / given name of the guest
The middle of other names for the guest
The last name / surname of the guest
The email address of the guest
How many plus ones the guest has
How many of the plus ones admitted
Additional information for the guest
The barcode data for the guest
Tags groups of guests by common information (comma separated)
The user who created this guest
The time the guest was admitted
The time the guest was blocked
The reason the guest was blocked
The ID of the event this guest belongs to
The time the guest can be admitted from
The time the guest can be admitted up to
If true, all plus ones are checked in along with the guest
The time the guest was checked out / discharged
The guest's image (optional)
The image should ideally be under 50kb
The image should be portrait - 600px x 400px
The image should be base64 encoded
The custom ID by which you can identify the guest if you choose not to use ID
Optional. The GUID of a stored comms template to send to this guest after creation. Leave null/empty to skip sending. The template must belong to your client and the same event. Setting this field triggers an asynchronous email send; the result is reported via webhook (comms.sent / comms.failed).
Optional. Opaque string echoed back in the comms webhook payload. Use this to correlate the webhook event with your own records (e.g. an order id) without having to store Qflow guids on your side.