canonical: https://jentic.com/apis/4.events/4events

# 4.events API

Jentic publishes the only available OpenAPI specification for 4.events API, keeping it validated and agent-ready. The 4.events API powers the 4.events platform for managing physical, online, and hybrid events. The 37 endpoints cover events, ticket types, ticket forms, discount coupons, activities, certificates, attendees, virtual event sessions, and check-in workflows. Authentication uses HTTP bearer tokens. The API is organised around an event ID (eid) and dependent ticket, attendee, or activity IDs.

## For AI agents

Create and manage events, ticket types, attendees, activities, virtual sessions, and check-in flows on the 4.events platform via OAuth-style bearer auth.

## Scope

Does not handle payment processing, video streaming infrastructure, or marketing email delivery - use for event, ticket, attendee, activity, certificate, and check-in management on 4.events only.

## Capabilities

- Create, update, delete, and retrieve events for physical, virtual, and hybrid formats
- Manage ticket types per event - create, list, update, delete, and add or remove CPF (Brazilian tax ID) restrictions
- Build and update ticket forms that capture custom attendee data at registration
- Issue and manage discount coupons applicable to specific tickets or events
- Define event activities (sessions, workshops, talks) and link them to attendees
- Generate and manage attendance certificates for completed events
- Run check-in flows for in-person and hybrid events using ticket and attendee identifiers

## Use cases

### End-to-End Event Setup

Stand up a new conference end-to-end on 4.events through the API. POST /events/new creates the event, POST /tickets/{eid}/new adds ticket tiers, POST /ticket-form/{eid}/new builds the registration form with custom questions, and POST /coupons/... issues early-bird coupons. The whole flow lives in code, so events can be cloned across editions.

Example prompt: Create an event 'DevConf 2026' starting on 2026-09-15, add three ticket tiers (Early Bird, Standard, VIP), build a registration form with name/email/company fields, and issue an EARLY20 coupon valid against the Early Bird tier.

### Attendee Check-In At Venue

Run check-in at the venue from a tablet or mobile app by calling the check-in endpoints. Look up the ticket via /tickets/{eid}/find/{tid}, then post the check-in to mark attendance. Real-time check-in counts feed dashboards so organisers can see room load as the event runs.

Example prompt: On scan of a QR with ticket ID T-9876 for event EID 1234, look up the ticket, mark the attendee checked-in, and increment the activity attendance counter.

### Discount Coupon Campaigns

Run promo campaigns by issuing time-bound discount coupons against specific ticket types. The coupon endpoints let you create, list, update, and revoke codes. Pair this with the events list endpoint to script seasonal or audience-specific promos across the entire 4.events portfolio.

Example prompt: For event EID 1234, create a coupon code SUMMER15 worth 15% off the Standard ticket tier, valid until 2026-08-31.

### Agent-Driven Event Operations

Let an AI agent run routine event admin - duplicate last year's event, update capacities, issue certificates after sessions complete - through Jentic. The agent searches for the operation by intent, supplies the event ID and payload, and executes; bearer tokens stay isolated in Jentic's vault.

Example prompt: Through Jentic, search 'create a 4.events event', load the schema, clone last year's event with this year's dates, and issue all attendees a certificate after the event ends.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /events/new | Create a new event |
| GET | /events/list | List events |
| POST | /tickets/{eid}/new | Add a ticket type to an event |
| POST | /ticket-form/{eid}/new | Create a ticket registration form |
| GET | /tickets/{eid}/find/{tid} | Find a ticket by ID for check-in |

## Key resources

- **Events** — Create, list, update, delete, and retrieve events
- **Tickets** — Manage ticket types per event including CPF tax-ID restrictions
- **TicketForms** — Build and update ticket registration forms
- **DiscountCoupons** — Issue and manage discount coupons
- **Activities** — Define event sessions, workshops, and talks
- **Certificates** — Generate and manage attendance certificates
- **Attendees** — Manage attendee records linked to tickets
- **VirtualEvents** — Configure virtual sessions and links
- **Checkin** — Run check-in flows for in-person and hybrid events

## Why Jentic

- **Setup:** Wiring the 4.events API by hand means managing its bearer token, targeting the api.4.events host, and shaping event, ticket, and check-in payloads yourself. Through Jentic you install once, import the 4.events API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** 4.events puts the event id in the URL path (/tickets/{eid}/..., /ticket-form/{eid}/new), so a rule can pin your agent to one event: it can add tickets and forms for that event and nothing else. You choose the operations it may call, so creating new events is not included unless you add it.
- **Credential handling:** Your 4.events bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an event' or 'find a ticket for an attendee', and Jentic returns the matching 4.events operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Ticketmaster Discovery API** — Ticketmaster's Discovery API exposes large-venue ticketed events with rich event metadata.
- **Meetup API** — Meetup focuses on community events and recurring group meetings rather than ticketed conferences.
- **Sympla API** — Sympla is a Brazilian event ticketing platform with similar event/ticket/attendee primitives.
- **Luma API** — Use Luma for invite-driven community events alongside 4.events for ticketed conferences.

## FAQ

### Why is there no official OpenAPI spec for 4.events API?

4.events publishes HTML reference docs at docs.4.events but no OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 4.events API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the 4.events API use?

It uses HTTP bearer token authentication; every request carries Authorization: Bearer {token}. Through Jentic, the bearer token is stored encrypted in the vault and injected at execution, so agents never handle the raw token.

### Can I run check-in for an event through the 4.events API?

Yes. The Checkin tag covers find-by-ticket and check-in operations; a typical flow calls GET /tickets/{eid}/find/{tid} on QR scan, then posts the check-in for the attendee. This is suitable for tablet apps at the venue.

### How do I add a ticket type with a CPF restriction?

Create the ticket via POST /tickets/{eid}/new, then add the CPF restriction with POST /tickets/{eid}/{tid}/cpf/add. Remove it later with POST /tickets/{eid}/{tid}/cpf/del. CPF support is specific to events that target Brazilian audiences.

### How do I create an event with 4.events through Jentic?

Run pip install jentic, then search 'create a 4.events event', load the POST /events/new operation, supply name, dates, and format, and execute. Run it through Jentic One, the self-hosted execution layer to receive an agent API key for execution.

### Can I issue attendance certificates through the API?

Yes. The Certificates endpoints let you generate and manage participation certificates for attendees once the event or activity is complete. Combine this with the Attendees and Activities resources to issue certificates only to attendees who actually checked in.

### Can I limit what my agent is allowed to do with the 4.events API?

Yes. Because you run Jentic One yourself, your own rules decide which 4.events operations and credentials the agent can use. 4.events puts the event id in the URL path (/tickets/{eid}/new, /ticket-form/{eid}/new), so you can pin the agent to a single event and let it add ticket types and registration forms for that event and nothing else. You choose the operations it may call, so higher-risk actions like POST /events/new to create new events stay excluded unless you add them.