4.events API

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

★ Only Publicly Available SpecProductivityCalendar 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.

Quickstart

Get started with 4.events API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a 4.events event"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with 4.events API 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

Issue and manage discount coupons applicable to specific tickets or events

GET STARTED

Start building with 4.events API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for 4.events API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use 4.events API 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 though Jentic?

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

Credential isolation

4.events bearer tokens are stored encrypted in the Jentic vault. Agents call createEvent, createTicket, and check-in operations through Jentic, which injects the Authorization header at execution — the raw token never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create an event' or 'check in an attendee') and Jentic returns the matching 4.events operation along with its input schema, so the agent calls the right endpoint without reading docs.4.events.

Time to first call

Direct 4.events integration: 2-3 days to model events, ticket dependencies, and check-in flows. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Ticketmaster Discovery API

Ticketmaster's Discovery API exposes large-venue ticketed events with rich event metadata.

Pick Ticketmaster Discovery when you need to surface large-scale ticketed events from a public catalogue; pick 4.events when you are running and managing your own event end to end.

Alternative

Meetup API

Meetup focuses on community events and recurring group meetings rather than ticketed conferences.

Pick Meetup for community-style recurring events; pick 4.events for ticketed conferences with check-in, certificates, and coupons.

Alternative

Sympla API

Sympla is a Brazilian event ticketing platform with similar event/ticket/attendee primitives.

Pick Sympla if your audience is Brazilian and already on Sympla; pick 4.events for hybrid event flows with stronger virtual session and check-in support.

Complementary

Luma API

Use Luma for invite-driven community events alongside 4.events for ticketed conferences.

Use Luma for community invites and 4.events for paid ticketing — bridge attendee data between the two when running a multi-format programme.

FAQs

Specific to using 4.events API 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 at https://app.jentic.com/sign-up.

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. Sign up at https://app.jentic.com/sign-up 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.