HEXLE API
Rest-API
1.15.0
CRM Expansion, Time Tracking, and Ticket Polish 17.05.2026Customer addresses can now be edited after the fact, including setting the primary address.
Customers can now have projects assigned to them, with management handled through a dedicated interface.
Ticket types now use reusable, company-wide title/value print fields instead of free text, letting tickets display these fully configurable fields in place of a simple extra note.
The LZE module now supports creating, editing, and deleting services.
Course categories can now be freely created, edited, and arranged in a custom order.
Invoices now correctly pull the seller's name, address, VAT ID, and tax number from the finance settings.
The customer module has been extended with contacts, corporate customers, projects, bank accounts, and other master data.
Customer projects and course password updates now use their own distinct permissions instead of colliding IDs.
The dashboard header now shows a profile icon with name, email, and username instead of just a logout button.
Courses can now be secured with an access password that visitors must enter on the public course page.
Registration now checks new usernames against an expanded blocklist to help prevent abuse.
New user accounts now start in light mode by default instead of dark mode.
The service time tracking module now lets you create and edit time entries and add comments to them.
The "PREVIEW" watermark on ticket PDFs is now tiled and rotated cleanly instead of rendering incorrectly as before.
Activity reports with their entries can now be created, generated as a PDF, and emailed directly to customers.
Creating a new Stripe configuration now leads straight into choosing the desired payment methods.
Access rights for the service time tracking module are now evaluated correctly.
The permission check now covers the "finance" area, and existing customers without a valid status were automatically backfilled to active.
Customer creation during checkout is now protected against race conditions and duplicate requests, so no more faulty customer records get created.
Outgoing emails from test and staging environments now display a clear environment notice in the header so they aren't mistaken for production mail.
Beyond bookings, entire course dates now get automatic reminder and follow-up emails, sent reliably without duplicates or missed dispatches.
After a system outage, follow-up emails for bookings and course dates are now delivered up to 7 days retroactively instead of just 24 hours.
Automated tests for core customer, contact, and company features now safeguard the stability of future changes.
First and last name are now captured separately and correctly during checkout instead of being guessed from a single name field.
Contacts can now only be assigned addresses belonging to their own company, preventing cross-company access to other companies' addresses.
Deleted customer records can no longer be edited or linked to new addresses, bank details, or entries.
Buyers can now personalize their own tickets via a personal link, including versioned QR codes and a registration deadline.
Permission checks for print fields now correctly use the company-scoped permission system instead of global roles.
Time tracking now supports defining and tracking goals with participants, progress, recurrence, streaks, and notifications.
Changes to customer notes are now tracked in a retrievable history for full traceability.
A new audit system logs changes to records and exposes them through a history API.
Server errors during ticket and Store orders no longer trigger misleading "unauthorized" messages.
Tickets can now be sold at scale through a dedicated REST endpoint, not just via the dashboard.
Time entries can now be flagged as billable or non-billable.
A dedicated demo environment is now available for every product, including Ticket, Bookings, Core, LZE, and Dashboard.
New companies and organizations can now be created directly from the dashboard.
Locked or unpaid tickets are now correctly rejected at scanning instead of being let through.
Customer notes and their history now display the first and last name of the person who made the edit.
Customers can now be looked up directly through a linked contact.
Employees can now be managed as standalone people per company and optionally linked to a user account.
Customer salutation is now maintained as a fixed selection instead of free text.
A new notification system with web push notifications and configurable preferences is now available.
Controller names were unified internally without changing any functionality.
Activity entries can now be marked as billable or non-billable.
The obsolete unique index on the legacy customer number has been removed.
Checkout now displays more informative error messages when something goes wrong.
The PDF activity log now correctly shows the total duration instead of leaving it blank.
Outdated management pages for addresses, payment providers, and tax rates have been removed from the backend dashboard.
Paying for door-sale tickets is now available as its own payment option at checkout instead of a separate toggle.
Ticket shops can now be extended with additional custom content blocks.
A company's financial settings now have their own API endpoints instead of being managed only through the company details page.
The outdated bulk sale feature in the backend dashboard has been removed.
You can now configure per ticket shop which ticket information is shown on a successful scan.
A ticket shop's terms and conditions text is now included in the public shop response as well.
Existing data from the legacy system can now be imported via migration.