Resending a massive message now takes you straight to the editor of the newly duplicated message. 📧

Previously, choosing Resend on a massive message could leave you on a broken or unexpected page because the duplicated message's ID wasn't being passed to the editor. You had to go back to the list and hunt for the copy before you could tweak recipients, subject, or content.

Why it matters: resending a campaign is now a single, uninterrupted flow — click resend, land in the editor, adjust, and send. No backtracking, no guessing which copy is the right one, and less risk of editing (or sending) the wrong message. ✅

• Resend now redirects correctly to the edit page of the cloned massive message
• The duplicated message is reliably identified, so no more dead-end redirects
• Faster follow-up sends for reminders, re-invitations, and campaign repeats 🚀

Attempting to delete the last remaining session of an activity now returns a clear, readable validation message instead of failing with a server error. 🎯

Previously, this action triggered a 500 error, leaving organizers with no explanation of what went wrong or why the session couldn't be removed. Now the platform responds with a proper 422 validation response and a human-readable message explaining that an activity must keep at least one session. ✅

Why it matters: organizers no longer hit a dead end when managing sessions — they immediately understand the rule and can adjust their agenda without contacting support or retrying the same failing action. ⏱️

• Deleting the last session of an activity now returns a proper validation error (422) instead of a server error 🚫
• The error message is displayed on the activity itself, so it renders correctly in the interface 💬
• Session management via the API behaves consistently and predictably 🔗

Opening an attendee type that no longer exists — because it was archived, belongs to another event, or the link was outdated — now takes you straight back to the attendee types list with a clear "not found" message instead of showing a server error page. 🎯

Previously, these links crashed the page, leaving you stuck with no explanation and no way forward except hitting the back button. Now the system handles the situation gracefully, so bookmarked or shared links to removed attendee types never interrupt your workflow. ✅

• Editing a missing, archived, or cross-event attendee type now redirects to the index page with a friendly not-found notice
• Viewing groups for a missing attendee type follows the same safe behavior
• Eliminates unexpected 500 errors caused by outdated or invalid attendee type links 🚀

Your event logo now renders reliably on attendee networking agendas. 🖼️ Previously, the logo could fail to load on the networking agenda page, leaving attendees with a broken image instead of your branding.

Why it matters: the networking agenda is one of the most-viewed pages during an event — attendees check it repeatedly to see who they're meeting and when. A broken logo undercuts your brand at exactly the moment attendees are paying closest attention. ✨

• Fixed the logo image on attendee networking agendas so it resolves the correct CDN URL before rendering
• Aligned the networking agenda template with the exhibitor agenda template for consistent, predictable branding across both views
• No configuration needed — existing events pick up the fix automatically 🎉

Searching for companies, contacts, or locations while assigning meeting locations now works reliably, even when names contain apostrophes or other special characters. 🔍

Previously, a company like "O'Brien Consulting" or a contact named "D'Angelo" would break the underlying search query and return a server error instead of results — forcing organizers to guess or scroll manually through long lists.

Why it matters: Business conference organizers assigning meeting locations can now trust search to just work, with no dead ends or error pages in the middle of scheduling. ✅

• Company, contact name, and location filters in the location-assign search now handle apostrophes and special characters correctly
• Eliminated the 500 error that appeared when searching for names with quotes
• Search inputs are now safely bound, making the query more robust and secure 🔒

Updating an exhibitor attendee that no longer exists now shows a clear "not found" message instead of crashing with a server error. 🙌

Previously, if an attendee had been deleted, archived, or belonged to a different event, saving changes from the exhibitor area would hit an unexpected error page — leaving exhibitors stuck with no explanation and no way forward.

Why it matters: exhibitors get an immediate, understandable message and can continue working right away, instead of losing their place and reaching out to support to figure out what went wrong. ✅

• Attendee updates now gracefully handle deleted, archived, or out-of-event records
• Users are redirected with a friendly not-found alert instead of seeing a 500 error
• Fewer dead ends and support tickets during busy event days 🎯

Keyword search inside mail lists now returns results reliably instead of failing with a server error. 🔍

Previously, search terms weren't being passed correctly to the database query, which left the keyword placeholder unresolved in the underlying full-text search and caused the request to fail outright. Any attempt to filter a mail list by keyword ended in a 500 error, forcing you to scroll through contacts manually.

Why it matters: finding the right recipients in large mail lists is often the first step before sending a campaign — this fix removes a hard blocker and saves you from manually combing through thousands of records. 📬

• Mail list keyword search now correctly binds search terms to the query
• No more server errors when filtering contacts by keyword
• Search behavior is covered by additional automated tests to prevent regressions ✅

Editing an attendee record that no longer exists — or that belongs to a different event — now returns a clean, predictable permission response instead of an unexpected server error. 🛠️

Why it matters: Stale browser tabs, bookmarked links, and duplicated event workflows are everyday realities for busy organizers. Instead of hitting a confusing error page, your team now gets a clear signal and can keep working without interrupting registration management. ✅

• Access is now validated before the attendee record is read, preventing crashes on missing or cross-event attendee IDs 🔒
• Attempts to update an attendee that isn't available in the current event context return a proper access-denied response 🚫
• Added automated test coverage to keep this behavior stable in future releases 🧪

We've upgraded the embedded Zoom Web SDK to version 6.2.0, bringing a more stable and modern in-browser meeting experience to every workshop and session streamed through Eventtia. 🎥

Attendees join Zoom sessions directly from the event website, so keeping the SDK current means fewer connection hiccups, better browser compatibility, and access to the latest audio and video improvements Zoom has shipped — all without your attendees ever leaving your event. ✨

• 🚀 Updated the Zoom Web SDK used for workshop streaming to 6.2.0
• 🖥️ Improved compatibility with the latest versions of major browsers
• 🔒 Aligned with Zoom's current supported SDK versions, keeping sessions secure and compliant with Zoom's platform requirements
• 🎧 Better audio/video stability for attendees joining sessions embedded in your event site

No action is required on your side — existing Zoom-enabled workshops automatically benefit from the update. 💚

Every Wompi payment status is now confirmed directly with Wompi rather than trusted from the incoming notification. Eventtia takes only the transaction ID from the notification, then reads the authoritative status from Wompi before updating the payment record.

Why it matters: a forged or tampered notification can no longer mark an order as paid, so your registration and ticket revenue is protected from fraudulent approvals — and the payment statuses you see in Eventtia always match what Wompi actually processed. 🔒

• Payment status is read directly from Wompi as the single source of truth
• Reference, amount and currency reported by Wompi are checked against the stored payment before any update is applied
• Transactions that can't be verified are no longer approved
• No configuration changes required — the safer verification applies automatically to all Wompi payments

Bulk emails with recipient conditions now keep delivering even when one recipient record fails, so a single problematic contact can no longer interrupt an entire send.

Previously, an error on one guest, list member, or exhibitor could abort the whole delivery, leaving part of your audience without the message and no clear indication of what went wrong. Each recipient is now processed independently, so the rest of your campaign goes out as planned. 📬

• Recipient failures are now isolated in the guests, contact list, and exhibitors sends, the same way they already were for attendees
• Corrected an inverted failure counter in the exhibitors send, so delivery reports now show accurate sent and failed totals
• Delivery errors are now recorded so our team can spot and resolve issues faster

Why it matters: Your communications reach the maximum possible audience on the first attempt, and the numbers you see in your delivery summary reflect what actually happened.

Attendee birthdates and event dates now display and save correctly, so the information you see in attendee records matches what was actually submitted.

Date handling issues could previously cause birthdates to be stored or shown incorrectly and event dates to appear in an inconsistent format, which made attendee data harder to trust when filtering, exporting, or reporting.

• Corrected the birthdate field on attendee records so values are captured and displayed as entered
• Standardized event date formatting for consistent presentation across attendee data

Why it matters: Clean, reliable date data means fewer manual corrections, more accurate segmentation by age or event timing, and exports you can hand off with confidence. 📅

We fixed an issue in our reCAPTCHA verification service that could cause validation requests to fail unexpectedly, occasionally blocking legitimate attendees from completing a registration or contact form.

Why it matters: reCAPTCHA is the first line of defense against bot submissions and junk registrations. When verification fails, you either lose real registrations or let spam through — both cost you time cleaning up your attendee list. This fix makes sure the check runs correctly every time, so your forms stay open to real people and closed to bots. 🛡️

• Corrected how verification requests are sent to Google's reCAPTCHA service
• Improved handling of the verification response so form submissions are validated consistently
• No action required on your end — the fix applies automatically to all forms already using reCAPTCHA

PayPal payments in Eventtia now run on PayPal's latest checkout platform, bringing a faster, more modern payment experience to your registration and ticketing flows. 💳

Why it matters: a smoother, more familiar checkout means fewer abandoned registrations and more completed ticket purchases — without you changing a thing in how you configure your event.

What's included in this upgrade:

• A redesigned PayPal checkout experience embedded directly in your event registration flow, so attendees complete payment without losing context.
• Support for additional PayPal payment methods, including Apple Pay and credit/debit card payments, giving attendees the option they already trust.
• Clearer, translated error messages when a payment can't be completed, so attendees know exactly what to do next instead of hitting a dead end.
• More reliable order and transaction tracking behind the scenes, keeping your payment records and Excel exports accurate and consistent.

Existing PayPal configurations continue to work — the upgrade applies automatically to your event's payment settings.

Registrations no longer queue up behind each other when many attendees sign up at the same time. Opening the registration form and submitting it now happen in parallel, so your form stays responsive under load.

Why it matters: registration peaks are exactly when you can least afford slowdowns or errors — the minutes after your announcement email goes out, or the final hours before a deadline. This change protects conversion at the moment it counts most. 🚀

• Activity sign-ups no longer block one another during registration
• Requests that used to time out under heavy load now complete instead of failing
• Reporting data stays accurate, whether an attendee joins an activity or leaves one

No action required — the improvement applies automatically to every event.

Action required if you have integrations reading attendee data. The API v2 attendee endpoints now require a valid user token. Calls made without one will no longer return data.

Attendee information retrieved through the API is now accessible only with a valid user token, closing a gap that could expose participant data to unauthenticated requests.

Why it matters: attendee records contain personal details such as names, emails, and registration data. Enforcing authentication ensures only authorized integrations can read them, helping you stay aligned with your organization's privacy and data-protection commitments. 🔒

For your developers:

• The API v2 attendees list endpoint now requires a valid user token
• The API v2 attendees search-by endpoint now requires a valid user token
• Requests without valid credentials are rejected instead of returning attendee data

If you run scripts or integrations against these endpoints, update them to send a valid user token before this release reaches your events.

Outgoing API v3 webhooks are now signed with an HMAC-SHA256 signature, so your endpoint can cryptographically confirm that each incoming payload came from Eventtia and was not altered in transit.

Why it matters: public webhook endpoints are an easy target for spoofed or replayed requests. With signature verification, your integration can reject anything that doesn't match — protecting your systems from acting on forged event data, and giving your security team a straightforward answer during integration reviews. 🔐

• Each event webhook now has its own secret, available from the webhooks settings screen.
• Every outgoing request is signed with HMAC-SHA256 using that secret.
• Your receiving endpoint can recompute the signature from the raw payload and compare it before processing.
• Keep the secret private — anyone who has it can generate valid signatures.

Where to find it: Event Settings → Webhooks. Full verification details are in the webhook documentation.

Event webhook payloads now include the event's UUID — a permanent, unique identifier you can use to match incoming data against records already stored in your CRM, data warehouse, or internal tools.

Why it matters: without a stable identifier, integrations end up matching on event names or other fields that can change, which leads to duplicates and broken syncs. The UUID removes that guesswork and makes lookups reliable from the first request. 🔗

• Every event webhook now carries a uuid field
• All existing fields are unchanged, so current integrations keep working with no modification
• Repeated deliveries of the same event can be safely detected and ignored

For your developers: see the webhook documentation for the full payload reference.

The Sessions tab now includes pagination, so your sessions are split into clean, navigable pages instead of loading as one endless list.

Why it matters: for events with dozens or hundreds of sessions, the page loads faster and finding the session you need takes seconds instead of a long scroll. 🚀

• Sessions are now displayed in paginated pages within the Sessions tab
• Faster page load times for events with a high volume of sessions
• Easier navigation when reviewing or editing your session agenda
• Removed a stray line that appeared under the Actions button, tidying up the table layout

The email selector in your event's general settings is now a searchable dropdown, so you can type a few characters and jump straight to the address you need instead of scrolling through a long list.

Why it matters: organizers managing accounts with dozens of verified sender addresses no longer waste time hunting for the right one — and picking the wrong sender email by mistake becomes far less likely. ✉️

• Type-to-search filtering on the email field in Event Settings
• Faster selection when many sender addresses are configured
• Clearer, more consistent dropdown experience aligned with other selectors in the platform

Event descriptions in listings and template previews now render as clean plain text instead of exposing raw HTML tags.

Previously, descriptions written with rich text formatting could leak markup such as <p> or into the event item view, making listings look broken and unprofessional to attendees browsing your events. Descriptions are now properly sanitized before display.

• HTML tags no longer appear in event descriptions shown in event cards and lists
• Event template previews render descriptions correctly, matching what attendees will see
• No action required — the fix applies automatically to existing events and templates

Why it matters: your event listings stay polished and trustworthy without organizers having to strip formatting by hand. ✨

Brazilian Portuguese (pt-BR) attendee messages now read naturally, with correct grammar and gender agreement across form labels and validation errors. 🇧🇷

Why it matters: awkward or incorrect wording makes attendees hesitate at the exact moment you need them to complete registration. Accurate, native-sounding error messages tell people precisely what to fix, reducing form abandonment and support requests from your Brazilian audience.

• Corrected the translation of the Country field for attendees.
• Fixed grammatical agreement in the Country and City validation message, which now correctly reads "devem ser preenchidos" for this compound field.
• Adjusted feminine/masculine agreement in attendee field messages so wording matches each field name.
• Updated global pt-BR wording for consistency across the platform.

No action is required on your side — the improved translations apply automatically to any event or registration form displayed in Brazilian Portuguese.

Searching for attendees to add to a session no longer fails when the session isn't restricted to specific attendee types. The attendee list now loads reliably, every time. 🎯

Why it matters: organizers building agendas often create sessions open to all attendee types. Previously, those sessions returned an error instead of a searchable attendee list, forcing you to reconfigure the session just to register someone. Now registration flows continue uninterrupted, saving time during high-pressure, on-site check-in and last-minute agenda changes.

• Fixed the error that appeared when searching attendees for a session with no attendee-type restrictions
• Those sessions now return the full list of eligible attendees

Attendees can now include emoji in their survey responses without the submission failing. Previously, replies containing emoji were rejected outright, which meant lost feedback and confused respondents. 🎉

Why it matters: survey feedback is only useful if it actually reaches you. Emoji are a natural part of how people express sentiment, and blocking them silently cost you responses you never knew were missing.

• Survey answers now accept emoji, symbols, and a wider range of non-Latin scripts
• Website survey replies containing emoji save correctly instead of failing
• Existing survey answers are unaffected — no action needed on your side

You can now create activities that don't display dates or times to attendees — ideal for on-demand content, flexible-schedule activities, or sessions whose timing isn't confirmed yet. 📅

Why it matters: until now, every activity required visible dates, which forced organizers to invent placeholder times or delay publishing their agenda. Now you can open registration as soon as an activity is approved, and reveal the schedule whenever you're ready — no more confusing attendees with dates that are bound to change.

Where to find it: Program → Activities → [your activity] → Settings, then turn off the date display option.

• Date-free activities appear consistently across the attendee agenda, activity listings, and advanced settings
• Public APIs and event feeds respect the setting, so external sites and integrations won't surface hidden dates
• Activities with several sessions and activities with a single session now behave the same way

The Sessions tab now only appears for activities that actually use multiple sessions. If an activity runs just once, the tab — and everything tied to it — stays out of your way.

Why it matters: most activities never need sessions, and showing an empty tab only invited confusion and misconfiguration. Organizers now see a shorter, more relevant setup screen and can publish activities faster with fewer wrong turns. ✨

• The Sessions tab is automatically hidden when the 'Multiple sessions' option is disabled on an activity.
• Session-related screens, such as the session attendees list, are consistently restricted for single-session activities.
• Access rules were tightened so session data is only reachable for activities that genuinely support it.

Custom buttons in the email editor now render with the correct width and stay properly contained within their content box — so what you see in the editor is what your attendees receive in their inbox.

Why it matters: misaligned or stretched call-to-action buttons make campaign emails look unpolished and can hurt click-through rates. This fix removes the need to manually tweak layouts or re-send corrected communications.

• Custom buttons respect their configured width instead of overflowing or collapsing
• Button content stays correctly aligned inside its container across email templates
• Editor preview now matches the final rendered email more closely

Event descriptions in calendar invites (.ics files) no longer display raw HTML tags when opened in Apple Calendar on iPhone, iPad, or Mac. Attendees now see clean, readable event details exactly as you wrote them.

Why it matters: The calendar invite is often the last thing an attendee sees before your event starts. When it arrives full of <p> and tags, key logistics like the venue address, dress code, or join link get buried in markup — and your event looks unpolished before anyone walks in the door. 📱

What changed under the hood:

• Event descriptions are now sanitized before being written into the .ics file, stripping HTML markup while preserving the intended line breaks and paragraph spacing.
• Applies to all attendee calendar invites generated by Eventtia, so no action is required on your side — existing events benefit automatically.
• Rich text formatting entered in the event description editor is converted into plain-text equivalents that every calendar client renders correctly, not just Apple's.

Attendee names are no longer auto-formatted, so they appear in the attendee list and in Excel exports exactly as they were registered.

Automatic capitalization rules were altering names that don't follow standard patterns — surnames with apostrophes (O'Brien), prefixes (McDonald, van der Berg), or intentional lowercase spellings were being rewritten. Removing that formatting layer means every attendee sees their name written correctly on your lists, reports, and any downstream document built from them. ✍️

What changed:

• The attendee index now shows first and last names as originally submitted, with no automatic capitalization applied.
• Excel exports of attendees preserve the same original spelling, keeping your reports consistent with your registration data.
• Names containing apostrophes, mixed casing, or special characters are no longer modified.

No action is required on your side — existing attendee records will simply display their original values from now on.

When you duplicate an event, its pre-event and post-event notifications now carry over with their scheduling intact — no more rebuilding your reminder sequence from scratch on every clone.

Why it matters: teams that run recurring or multi-city events rely on cloning as their starting point. Losing notification timings meant re-entering every reminder by hand, and a missed one meant attendees never got their confirmation or follow-up. This fix removes that manual step and the risk that comes with it. 🔁

• Notification schedule dates are now correctly recalculated when an event is duplicated, staying aligned with the new event's dates
• Pre-event and post-event notifications are included in the clone instead of being dropped
• Added safeguards on the event record to prevent invalid or missing event references from breaking the duplication process

Build against Eventtia without leaving Cursor.

The Eventtia MCP server is now a one-click plugin in Cursor. Install it, connect your account, and your AI agent can work directly against your event data — creating events, managing attendees and attendee types, setting up workshops, sessions and speakers, handling payments, and running check-in.

No SDK to wire up, no API docs to keep open in a second window. Ask for what you need in plain language and the agent calls the right endpoints.

Install: https://cursor.directory/plugins/eventtia

We've upgraded our Stripe integration to deliver a smoother, more dependable payment experience for your attendees. This update brings improved payment processing, better handling of customer sessions, and stronger reliability across the entire checkout flow.

Why it matters: fewer payment errors mean higher conversion rates, less time spent troubleshooting failed transactions, and a more professional checkout experience for your attendees — directly impacting your event revenue.

• Upgraded Stripe integration with the latest API improvements for faster and more secure transactions
• Refined payment intent and setup intent workflows for smoother checkout sessions
• Improved customer session handling to reduce friction during repeat purchases
• Enhanced webhook processing to ensure payment status updates are captured reliably
• Expanded test coverage across payment models and services for greater stability

We've removed the Turnstile verification step from the 2FA login screen (Already used on the user/password screen), streamlining the sign-in experience for users with two-factor authentication enabled.

Why it matters: One less checkpoint means quicker access to your account without compromising security, since 2FA already provides a strong layer of protection. Expect a smoother, more direct login flow every time you verify your identity.

We resolved an issue with CORS (Cross-Origin Resource Sharing) handling that could cause certain requests from external domains, including embedded website builder content, to be blocked or behave unexpectedly.

Why it matters: this fix ensures that integrations, embedded widgets, and third-party origins load reliably without unexpected browser errors, saving time troubleshooting and providing a smoother experience for both organizers and attendees.

Our MCP connector, Eventtia Connect, is now published in Claude's connector directory. Once connected, Claude works directly against your account: look up events and summaries, register, confirm or reject attendees, manage attendee types and custom fields, create workshops and sessions, enroll participants, and review check-ins — all in conversation, without leaving Claude.

Why it matters

• Answers instead of exports. "How many confirmed attendees do we have for the Paris edition, and how many seats are left in the morning workshop?" used to mean logging in, filtering, exporting to CSV and counting. Now it's one question.
• Repetitive admin becomes a single instruction. Confirming a batch of pending registrations, enrolling a group in a session, or resending welcome emails no longer means dozens of individual clicks.
• Your data comes to the platform, not the other way around. Claude can read the spreadsheet a sponsor sent you or the list buried in an email thread and register those attendees directly — no reformatting to match an import template.
• Useful on-site, not just at your desk. Seat availability, check-in counts, and attendee lookups are available from your phone, in seconds, while the event is running.
• No integration project required. Connect once from the directory. No developer time, no custom API work, no new tool for your team to learn.

Add it here: <a href="http://www.claude.ai/directory/connectors/eventtia-mcp">www.claude.ai/directory/connectors/eventtia-mcp</a>

Enabling the password gate on your event website now automatically clears any active visitor session cookies, ensuring the protection takes effect immediately for everyone.

Why it matters: Previously, visitors who had already accessed your site could bypass a newly enabled password gate thanks to their existing session. This fix closes that gap, giving organizers confidence that turning on password protection instantly secures the site for all users — no manual cache clearing or waiting required.

A new Appearance tab is now available in Event Settings, giving organizers a single place to shape the visual identity of their event website.

Instead of juggling scattered style options, you can now define your event's colors, corner styles, and overall theme from one dedicated screen — making it faster to launch an on-brand event experience and easier to keep visuals consistent across every attendee touchpoint.

• New Appearance settings tab for configuring event theme and visual styles
• Corner style selector and refined color controls with smart color math for accessible contrast
• Availability of the Appearance tab is now conditional, so it only appears where relevant

The public API has been extended with new endpoints to expose event website data and theme configuration, unlocking deeper integrations with the new website builder.

Developers can now retrieve an event's website details and its associated theme through API v4, making it possible to build custom front-ends, embed event branding into external tools, or sync appearance settings with third-party platforms — all without manual configuration.

• Updated websites endpoints in API v4 with an enriched serializer
• New event theme endpoint to fetch appearance and branding data programmatically

Workshop selections now automatically reset whenever an attendee's type is changed, ensuring registrations stay consistent with the workshops actually available for that type.

Why it matters: this prevents attendees from unintentionally keeping workshop registrations that no longer apply to their new type, avoiding invalid data, scheduling conflicts, and confusing follow-up communications for both organizers and participants.

We've rolled out a brand-new rich text editor across the platform, giving you a smoother, more modern writing experience wherever you format content in Eventtia.

Why it matters: content creation is at the heart of every event — from sponsor descriptions to workshop details. The new editor loads faster, behaves more consistently across browsers, and reduces the small formatting frustrations that slow you down when building out your event.

• Modernized editing interface with cleaner icons and toolbar
• Improved performance thanks to CDN-delivered assets
• More reliable formatting behavior across sponsors, workshops, and other content areas
• Refined styles for better visual consistency with the rest of the platform
• Translation fixes and QA-driven polish for a smoother day-to-day experience

We've resolved an issue affecting the attendee leads API response, ensuring your team gets accurate and complete lead information every time.

This fix means fewer surprises when pulling lead data through integrations or exports — helping sales and event staff follow up on the right contacts without missing a beat.

The event logo is now included in the public attributes of the event API, making it easier to display branded event information across integrations and external tools.

Why it matters: Teams building custom event pages, embeds, or third-party integrations can now access the event logo directly through the public API without needing additional authenticated calls, saving development time and ensuring consistent branding everywhere your event appears.

Workshop calendar files (.ics) sent to attendees now use the PUBLISH method instead of REQUEST, ensuring events are added smoothly to calendar applications without triggering RSVP prompts or invitation acceptance flows.

Why it matters: Attendees can now save workshop schedules to their calendars with a single click, without confusing 'accept invitation' dialogs. This reduces friction, prevents delivery issues with strict calendar clients, and improves the overall registration experience for your events.

We've extended the expiration time for machine-to-machine (M2M) authentication tokens, giving your integrations more breathing room between token refreshes.

Why it matters: If you rely on API integrations or automated workflows, this change reduces the frequency of token renewals, minimizing interruptions and lowering the risk of failed requests due to expired credentials. Expect fewer authentication hiccups and a more reliable connection between Eventtia and your external systems.

Sponsors and exhibitors can now configure the exact questions they want to ask when capturing leads at your event, turning every scan into a richer, more qualified conversation.

Why it matters: instead of settling for a generic lead form, organizers can tailor the data collected to match each sponsor's qualification criteria, which means better follow-ups, higher ROI for exhibitors, and cleaner data for reporting.

• Create and manage custom lead fields directly from App Settings under the Lead Questions tab
• Support for multiple field types, including dropdown questions with predefined answer options
• Full emoji and multilingual character support in both field labels and captured lead responses
• Lead capture is now scoped to the Leads module, so it only appears where it's actually enabled
• Custom lead data flows through to API v3 responses and Excel exports for seamless downstream use

Available in all supported languages, with a refreshed configuration interface that makes it faster to set up and edit lead questions before your event goes live.

Attendee and Guest phone numbers are now strictly validated against international formatting standards, so invalid entries are caught at registration instead of surfacing later during check-in, SMS notifications, or reporting.

Why it matters: bad phone data is one of the most common causes of failed communications and messy attendee lists. By validating numbers at the source using Google's libphonenumber standard, you get cleaner data, fewer support tickets, and higher deliverability for every SMS and WhatsApp message you send.

• Strict format verification powered by Phonelib (Google libphonenumber) for Attendee and Guest records.
• Clearer, translated validation messages across all supported languages to help registrants correct mistakes quickly.
• Handles edge cases such as blank values and unusual international formats reliably.

The platform now remembers your preferred language through a dedicated cookie, so you no longer need to reset it every time you log in or switch pages.

Why it matters: Multilingual teams and international users save time and avoid friction by having their chosen language persist reliably across the entire platform. Combined with a new language switcher directly in the navbar, changing languages is now a one-click action that stays applied wherever you go.

• New cookie-based language preference that persists across sessions
• Added a language switcher directly in the private navbar for quick access
• Hardened cookie handling with additional security safeguards

You can now upload a dedicated iOS logo for your mobile wallet passes, giving your event a polished, on-brand presence right inside attendees' Apple Wallet.

Why it matters: Wallet passes are one of the first touchpoints attendees see on event day. A recognizable logo builds trust, reinforces your brand, and helps your pass stand out among the dozens of cards users may already have saved. Configure it once in your Mobile Passes settings and every issued pass will reflect your identity.

• New iOS icon upload field available in Mobile Passes settings
• Streamlined to a single optimized size, so setup takes seconds
• Applies automatically to all newly generated Apple Wallet passes

Events with all-free tickets now display correctly in the Google Events feed, ensuring your events appear with the right pricing information across Google's discovery surfaces.

Why it matters: Incorrect ticket price structures could prevent your free events from being properly indexed or displayed on Google, reducing visibility and attendance. This fix ensures accurate representation so potential attendees see the right information the first time.

You can now create, update, and delete checkpoints directly through the Eventtia API in both V3 and V4. This unlocks full automation for check-in workflows, so teams managing large or recurring events no longer need to configure checkpoints manually from the dashboard.

Why it matters: integrating checkpoint management into your existing tools means faster event setup, fewer manual errors, and the ability to sync checkpoints with third-party systems in real time.

• New Create, Update, and Delete endpoints for checkpoints available in API V3 and V4
• Full Swagger/OpenAPI documentation published for both versions to make integration straightforward

https://docs-connect-api-v3.eventtia.com/reference/listcheckpoints