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.