← All integrations Integration guide · LINE MINI App

Event booking, inside LINE.

Guests pick a time slot, register with their companions and keep their QR code in LINE. Eventtia runs registration, capacity and check-in behind your MINI App.

Discuss your LINE project See how it connects

Your team or agency builds the MINI App. Eventtia supplies the event engine, the API and the webhooks.

Illustrative booking flow for a fictional event, Atelier Sessions. The guest picks the 15:30 time slot, adds one companion and receives a confirmed entry pass with a QR code.

Illustration with a fictional event. Not a customer's interface.
How it connects

Three systems, one booking.

Your MINI App is what the guest sees. Your backend connects it to Eventtia, where your team sets up events and runs check-in.

Guest experience

Your LINE MINI App

  • Event page and time slots
  • Booking and companion forms
  • Confirmation and QR code
Booking requestBooking and QR code

Your connection

Your backend

  • Links each LINE user to their booking
  • Calls the Eventtia API
  • Receives Eventtia webhooks
API callsResponses and webhooks

Event operations

Eventtia

  • Events, sessions and capacity, set up by your team
  • Registrations, companions and cancellations
  • Check-in with the Eventtia check-in app

When staff scan the QR code at the door, a webhook tells your backend. A follow-up message in LINE is optional, and your team decides.

Who builds what

Your experience, our event engine.

You build what your guests see. Eventtia supplies the event operations underneath.

You build

Your team or agency

  • Design and build the MINI App screens
  • Build the backend that links LINE users to bookings
  • Handle companion invitations and LINE messages
  • Choose how data reaches your CRM: from your backend or from Eventtia

Eventtia supplies

Eventtia

  • Event setup, sessions and capacity
  • Registration, companions and cancellations
  • REST API, webhooks and a staging environment
  • The Eventtia check-in app and technical support
Implementation

From kickoff to the first launch.

  1. Step 01

    Kickoff

    Your team or agency and Eventtia agree on the booking model, the form fields, the CRM path and the traffic you expect at each launch.

  2. Step 02

    Access

    Eventtia opens a staging environment, API credentials and webhooks. If your launches need more than the standard API limit, you agree on it at this step.

  3. Step 03

    Build and test

    Your team or agency builds the screens and the backend on staging, with test events and registrations.

  4. Step 04

    Go live

    Your production backend connects to Eventtia's production environment, and the first event opens to your LINE audience.

For the technical team

API, webhooks and Japanese data.

API building blocks

The parts of the Eventtia REST API a LINE integration uses.

Authentication
A machine-to-machine token, so your backend calls Eventtia without a user session.
Availability
Events, attendee types and form fields, and each session with its total and booked seats and the group limits per attendee type.
Registration
Create the attendee, book a session, update details or cancel. Each companion is a linked attendee and takes one seat.
Webhooks
Event updated; attendee created or updated, with check-in status and QR code; session created, updated or deleted. Set them per event, or once for the whole account through the API.
Launch traffic
The standard limit is 100 API calls per minute. For enterprise projects, Eventtia can raise it for your server addresses. During peaks, requests are queued and processed progressively.
API versions
Versions 3 and 4 are both live. Earlier versions stay active, and each new version adds capabilities.

Full reference: docs.eventtia.com. For the architecture in depth, read Esteban Ochoa's article on headless event registration.

Japanese registration data

Small data rules often block a launch in Japan. The platform already handles them.

  • Mobile carrier emails on domains like docomo.ne.jp, ezweb.ne.jp and i.softbank.jp pass validation.
  • The API returns each event's configured date format, so your MINI App shows dates the same way.
  • Phone numbers are validated by country with Google's libphonenumber.
  • API version 4 returns times in the event's time zone: JST for events in Japan.
FAQ

LINE integration questions.

Can Eventtia run event registration inside a LINE MINI App?

Yes. Your LINE MINI App shows the event, the time slots and the form. Eventtia runs the registration underneath through its REST API and webhooks: capacity, companions, cancellations and check-in.

Is there a ready-made Eventtia app for LINE?

No. The brand's team, or its agency, builds the LINE MINI App screens and a small backend that connects them to Eventtia. Eventtia supplies the event engine, the API, the webhooks and the check-in app, and its technical team works with your developers.

How do guests check in at a LINE event?

The guest shows the QR code from the LINE MINI App. Staff scan it with the Eventtia check-in app, and Eventtia sends an attendee_updated webhook, so your backend knows who came and can send an optional follow-up on LINE.

Do companions count against session capacity?

Yes. Each companion takes one seat in the session, as for any Eventtia registration. Your MINI App can collect each companion's own details later.

What are the Eventtia API limits for a launch?

The standard limit is 100 API calls per minute. For enterprise projects, Eventtia can raise it for your server addresses. During peaks, Eventtia queues incoming requests and processes them progressively.

Does Eventtia handle Japanese registration data?

Yes. Email addresses from Japanese mobile carriers pass validation, the API returns each event's configured date format, phone numbers are validated by country, and API version 4 returns times in the event's local time.

Plan your LINE booking flow.

Tell us about your guest journey, your launch traffic and who builds the MINI App. Bring your technical lead.

Discuss your LINE project All integrations