Eventonomy

Check-in Scanner Pro

Pro feature. Available in Eventonomy Pro.

Pro - The Check-in Scanner block requires Eventonomy Pro.

The eventonomy/checkin block gives door volunteers a fast way to verify attendee tokens and mark them as checked in. The volunteer enters the attendee's check-in token, clicks Check in, and the block posts to the Pro check-in REST endpoint and shows the result immediately.

What You Will Learn

  • How the check-in flow works
  • Where to place the block
  • Block settings and what each one controls
  • How attendees get their tokens

How the Check-in Flow Works

  1. Attendee receives a token when their RSVP or order is confirmed. The token appears in their confirmation email and can be printed or shown on a mobile screen.
  2. Door volunteer opens the check-in page - any page or the single-event page where the Check-in block is placed.
  3. Volunteer enters the token in the text field and clicks Check in.
  4. The block posts the token to POST /eventonomy/v1/checkin (Pro REST endpoint).
  5. Result appears in the result area: success (attendee name, event) or an error (invalid token, already checked in).

Note: The current implementation supports manual token entry only. QR code scanning requires a third-party camera-to-input bridge or a future Pro release that integrates a camera scanner. Many purpose-built QR scanner apps can write their scan output into the focused text field on the page.

Where to Place the Block

Option 1 - Single-event page

Add the Check-in block directly to the event's single-event page template. The block reads the eventId attribute you set to filter check-ins to that event only.

Option 2 - Dedicated check-in page

Create a new page (e.g. /check-in/) and add the block there. This lets volunteers check in attendees for any event from a single page, especially useful for venues that run multiple events.

To add the block:

  1. Open the page in the Block Editor.
  2. Click + and search for Eventonomy Check-in.
  3. Insert the block and configure its settings.

Block Settings

Setting Default Description
Event ID 0 The ID of the event to check attendees in to. Leave 0 to accept tokens from any event (multi-event pages).
Show stats On Show a summary line below the result area.
Allow manual entry On Show the token input field and the Check in button. Turn off if you are using a hardware reader that calls the REST endpoint directly.

Access Control

Only logged-in users see the check-in interface. Visitors who are not logged in see a "Sign in to check attendees in" notice instead of the scanner.

The REST check-in endpoint requires the evnm_manage_rsvps capability (granted to event managers and administrators by default).

What's Next?

Configure paid ticket checkout with a payment gateway.

Payment Gateways →