canonical: https://jentic.com/apis/nextevent.com/nextevent # NextEvent API Jentic publishes the only available OpenAPI specification for NextEvent API, keeping it validated and agent-ready. The NextEvent API enables event organizers to manage the complete ticketing lifecycle for conferences, concerts, sports events, and festivals. It provides programmatic control over event creation, ticket pricing, order processing, payment authorization and settlement, access code generation, gate management for entry scanning, and promotional discount codes. The API supports multi-tenant deployments with customizable hostnames and includes comprehensive order management with rebooking and cancellation workflows. ## For AI agents Manage event ticketing operations including event creation, pricing, orders, payments, access codes, gate scanning, and discounts. Supports complete ticket lifecycle from sale to entry validation. ## Scope Does not handle venue management, artist booking, marketing campaigns, or attendee CRM - use for ticketing operations and entry validation only. ## Capabilities - Create and configure events with categories and pricing tiers - Process ticket orders with basket management and expiration handling - Authorize and settle payments with cancellation and refund workflows - Generate and track access codes for event entry validation - Configure gates and register devices for ticket scanning - Create discount codes and discount groups for promotional campaigns - Retrieve order tickets and scan logs for entry tracking ## Use cases ### Concert Ticket Sales Event promoters can sell concert tickets through multiple channels using the NextEvent API. The API handles event creation with categories (VIP, General Admission, Standing), dynamic pricing, basket management with automatic expiration, payment authorization, and ticket generation with unique access codes. Order processing supports rebooking for date changes and cancellation workflows with refunds. Integration takes 2-3 days for basic checkout or 4-5 days for custom booking flows with promotional codes. Example prompt: Create an event for a concert with 3 ticket categories (VIP at $150, GA at $75, Standing at $50), process an order for 2 VIP tickets, authorize payment, and generate access codes ### Conference Badge Management Conference organizers use the NextEvent API to manage attendee registration and badge validation. The API supports creating events with speaker, exhibitor, and attendee categories, setting up early-bird and group discount codes, processing bulk orders, and generating access codes linked to badge QR codes. Gate devices log entry scans in real-time, enabling capacity tracking and duplicate entry prevention. Device authentication ensures only authorized scanners can validate badges at each gate. Example prompt: Create a conference event with 3 registration types, set up a 20% early-bird discount code, process 50 attendee registrations, and retrieve scan logs for the main entrance gate ### Festival Multi-Day Pass Sales Festival organizers can sell multi-day passes and single-day tickets using the NextEvent API's flexible pricing and category system. The API handles complex scenarios like family packages (multiple tickets in one order), VIP upgrades through rebooking, refund requests through cancellation workflows, and entry validation across multiple festival gates over multiple days. Base categories and base prices enable consistent pricing across event dates while allowing per-event overrides. Example prompt: Create a 3-day festival with single-day and weekend pass pricing, process an order for a weekend pass, rebook it to upgrade to VIP access, and track entry scans across all 3 festival gates ### AI Agent Event Operations AI agents use the NextEvent API through Jentic to automate event operations tasks like monitoring ticket sales, processing refunds, generating promotional codes, and analyzing entry patterns. Agents search by intent (e.g., 'process a ticket refund') and Jentic returns the matching operation with input schemas. Credentials are stored encrypted in the your Jentic One instance - agents receive scoped tokens, never raw API keys. Direct NextEvent integration requires 3-5 days for auth, webhook setup, and error handling. Through Jentic: under 1 hour. Example prompt: Search for 'process a ticket refund', load the NextEvent cancellation operation schema, and execute a refund request for order ID ord_abc123 ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/events` | Create a new event | | GET | `/events` | List all events | | GET | `/baskets/{orderId}` | Get basket contents for an order | | POST | `/orders/{orderId}/authorize` | Authorize payment for an order | | POST | `/payments/settle` | Settle an authorized payment | | GET | `/orders` | List all orders | | POST | `/access-codes` | Create access codes for tickets | | GET | `/access-codes/{code}/scan-logs` | Get scan logs for an access code | ## Key resources - **Events** — Create events and retrieve event details - **Categories** — Manage event categories and base categories for ticket types - **Pricing** — List prices and manage base prices for ticket categories - **Orders** — Process orders, manage baskets, retrieve tickets, handle rebooking and cancellations - **Payments** — Authorize, settle, and abort payment transactions - **Access Codes** — Create, update, list, and track scan logs for entry access codes - **Gates** — Retrieve gate information for entry points - **Devices** — Manage scanning devices and handle device authentication - **Discounts** — Create discount codes and manage discount groups ## Why Jentic - **Setup:** Wiring the NextEvent API by hand means encoding your username and password as HTTP Basic, resolving your own tenant hostname, and sequencing event, basket, order authorization, payment settlement, and access-code calls yourself. Through Jentic you install once, import the NextEvent API from the API Directory, store the username and password once, and your agent calls it. - **Permission scoping:** The NextEvent API puts the order id and access code in the URL path (`/orders/{orderId}/authorize`, `/access-codes/{code}/scan-logs`), so a rule can pin your agent to one order or code. You choose the operations it may call, so payment settlement is not included unless you add it. - **Credential handling:** Your NextEvent username and password are stored once, encrypted, by your own Jentic One instance and encoded as HTTP Basic at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'process a ticket order' and Jentic returns the matching NextEvent operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe API** — Payment processing infrastructure often paired with NextEvent for handling payment intents and card charges - **Ticketmaster Discovery API** — Large-scale ticketing platform for concerts, sports, and entertainment events - **Square API** — Point-of-sale and commerce platform for in-person and online payments ## FAQ ### Why is there no official OpenAPI spec for NextEvent API? NextEvent does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NextEvent 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 NextEvent API use? The NextEvent API uses HTTP Basic Authentication. Jentic's your Jentic One instance stores your basic auth credentials encrypted in the vault. AI agents receive scoped access tokens - the raw username and password never enter the agent's context. ### Can I process ticket orders and payments with the NextEvent API? Yes. The API provides order management through basket operations (get, clear, remove items, extend expiration) and payment processing through authorize, settle, and abort endpoints. You can retrieve order details, order tickets, and handle rebooking and cancellation workflows with refunds. ### How do I manage access codes and gate scanning with the NextEvent API? Create access codes for ticket holders using the POST /access-codes endpoint, update them with PUT /access-codes, and track entry validations through scan logs at GET `/access-codes/{code}/scan-logs.` Configure gates with GET /gates and `/gates/{gateId}`, and authenticate scanning devices using POST `/devices/login` and POST `/devices/logout.` ### What are the rate limits for the NextEvent API? Rate limits are not specified in the OpenAPI spec. Contact NextEvent support or refer to their developer documentation for current rate limit information. Jentic tracks API usage and will surface rate limit errors if encountered. ### How do I create discount codes with the NextEvent API through Jentic? Search for 'create discount code' in Jentic to find the POST /discount-codes operation. The operation returns the schema showing required fields. Execute the call with your discount parameters (code, discount type, amount, validity period). List existing codes with GET /discount-codes and delete with DELETE `/discount-codes/{id}.` ### Can I rebook or cancel orders with the NextEvent API? Yes. The API supports rebooking through POST `/orders/{orderId}/rebook` for ticket changes (date, category upgrades), and cancellations through a two-step workflow: POST `/orders/{orderId}/cancellation/request` to initiate and POST `/orders/{orderId}/cancellation/settle` to complete the refund. ### Can I limit what my agent is allowed to do with the NextEvent API? Yes. Because you run Jentic One yourself, your own rules decide which NextEvent operations and credentials the agent may use, so you can grant read-only order and scan-log access while withholding write operations like payment settlement at `/payments/settle.` Since the NextEvent API carries the order id and access code in the URL path, such as `/orders/{orderId}/authorize` and `/access-codes/{code}/scan-logs`, you can pin the agent to a single order or access code rather than the whole account. Your Basic auth username and password stay with your Jentic One instance and are never exposed to the agent.