4.events API

Name: 4.events API
Brand: 4.events API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer37 EndpointsREST

For 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.

Install Jentic One Beta

Connect the 4.events API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 4.events API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with 4.events API.

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

GET STARTED

Start building with 4.events API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use 4.events API for, with concrete tasks.

★ 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.

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.

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.

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.

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

37 endpoints — jentic publishes the only available openapi specification for 4.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using 4.events API through Jentic.

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.

4.events API

Connect the 4.events API to your agent

Capabilities

Start building with 4.events API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs