Following the big Public API expansion in v2.48, v2.50 takes the next decisive step: Custom Reports become first-class API citizens, and your bespoke data model — your Custom Variables — rides along with the standard endpoints.
Any report → an endpoint
One tickbox turns a Custom Report into a Public API endpoint.
Four report types
Transactions, Products, Web Forms and Preferences all supported.
Custom variables ride along
Your bespoke Custom Fields now travel with the standard endpoints.
Low-code friendly
A new 'named' format slots neatly into Zapier, Make and friends.
Flip a switch, get an API
The whole flow is deliberately simple. Head to Events HQ > Settings > Reports > Custom Reports, open any report you've already built, and tick 'Enable as Public API endpoint'. That's it. The report is now available via the Public API, returning its live data up to 1,000 rows per page.
Tick the box, and any Custom Report becomes a live Public API endpoint.
For anyone who's ever written an "export this report to CSV, upload to the shared drive, update the dashboard" workflow — this is the end of that story.
Four report types, all supported
v2.50 covers the full Custom Report family, preserving your own column names and the column order you've set up in each report:
Transactions
Full transaction detail
Products
One table per product type
Web Forms
All submission data
Preferences
Attendee preferences
Product reports return one table per product type — Event attendance, Table booking, Exhibition stand, Custom products and Awards nominations — with your Custom Variables included out of the box.
What this really unlocks
The glue between Evessio and everything else.
The data in Custom Reports is often exactly the data your finance team, marketing team and BI team want in their tools. Removing the manual step between "report built" and "data flowing" is the kind of change that saves hours every week and ends a whole category of "can you resend me that spreadsheet?" conversations.
Rich filtering options
Every report endpoint supports flexible filtering out of the box — so you can pull just the slice of data you actually need:
Date filtering, two ways
Transaction-specific filters
The rolling 'last N days' is especially handy for dashboards — set it once, and every refresh returns a rolling window without you needing to touch the dates.
Two response formats
You pick how the data comes back, depending on what consumes it on the other end:
Default
The standard format
The default response format for Custom Report endpoints — ideal when you're building a custom integration in your own code.
New in v2.50
The named format
Simple rows keyed by column name — perfect for low-code tools like Zapier, Make and others that work best with flat key-value structures.
Point Zapier at the endpoint with the named format and your Zap sees each row as a familiar flat record — no custom parsing required.
Custom Variables, everywhere
If you've invested time into configuring Custom Variables (Custom Fields) in Events HQ > Settings > Data fields > Custom fields, you can now get those values straight out via the Public API alongside the data you're already pulling.
Add custom variables to existing endpoints
Pass a flag on the events, transactions, orders and customers endpoints and your custom variable values join the response.
Dedicated custom-variables endpoint
A fresh endpoint that lists every Custom Variable configured for an event — perfect for building dynamic integrations that discover the schema themselves.
Existing integrations keep working
Nothing changes for integrations that already use the Public API — Custom Variables are only added to responses when the integration explicitly asks for them.
The data flow, redrawn
From Evessio to your BI tool, automatically.
Build the Custom Report once in Evessio with the columns and filters you need. Enable the endpoint. Point your BI tool, data warehouse, CRM or spreadsheet at it — and the data flows every time anyone asks for it.
Full documentation inside your Events HQ
Every endpoint — new and existing — is documented in Events HQ > Settings > API > API Docs. Also see the Custom Reports guide, the Custom Fields guide, and the broader Public API article.
Keep going
The Public API started modestly, grew with web forms and products in v2.48, and now takes a confident leap with v2.50. There's plenty more Public API work already queued up — but for a lot of teams, v2.50 unlocks the data pipeline they've been trying to build for ages.
See it in action
Discover what Evessio can do for your events.
Book a demo or speak directly with our team to see how our Public API — and everything else in Evessio's award-winning toolkit — can plug into your existing systems.
