An API key pasted into a script for last year's event, then forgotten, is still a way into your event data. Now every new key gets an expiration date, Studio shows when each key was last used, and keys that sit idle for a year switch themselves off.

What's new

Choose how long a key lives

When you create a key, pick its Expiration date: 7 days, 30 days, 60 days, 90 days (the default), 1 year, or Custom to set an exact date.

See every key's status at a glance

The API Keys list now shows, for each key, when it was created, when it was last used, and when it expires, or that it already has. Spotting a key that hasn't been used in months takes a second.

Unused keys expire on their own

A key that hasn't been used for 12 months expires automatically. Events run on yearly cycles, so a key nobody has called in a year is almost always a forgotten one. This applies to existing keys too, including those created without an expiration date.

A heads-up before anything breaks

You get an email shortly before a key expires, and another once it has: enough time to swap the key in your integration before anything stops syncing. Expired keys stay in the list, marked as expired, but they can't be turned back on. Create a new key and update your integration.

How to create a key

1. In Studio, open API Keys and click Create a new key.
2. Give it a Key name and choose an Expiration date.
3. Click Generate the key, then copy it right away: for security reasons, it's only shown once.

Bring your accepted abstracts, sessions and speakers from MiraSMART straight into Swapcard.

You can now connect MiraSMART (Mira Smart Conferencing) to Swapcard Studio. The integration imports your scientific program: events, the presentations scheduled inside them, and the speakers, poster presenters, organizers and moderators behind them. It keeps all of it in sync without manual exports or CSV uploads.

🔐 Authentication

Connect with three credentials:

• Vendor login and password, issued by MiraSMART
• Project ID, your MiraSMART project (e.g. ABCD1234)

If the credentials are rejected, the connection is flagged right away so you can update them.

📦 What gets synced

Each of the three object types can be turned on or off on its own. All three are off by default.

• Events → Sessions. Each MiraSMART event becomes a Swapcard session, with its title, description, start and end times, room, event type, scientific topics, audience and moderators.
• Presentations → Sessions. Each presentation becomes a session nested under its parent event, so attendees can browse from a symposium or poster block down to the individual talks. It brings its title, abstract, schedule, status, topics and subtopics, author and affiliation blocks, and abstract ID. If a presentation appears in more than one event, it gets a session in each one.
• Speakers & Organizers → People. Speakers, poster presenters, organizers and moderators are imported as people, with their name, email, institution and author types. Each person is automatically linked to their sessions: presenters to their presentation and its parent event, and organizers and moderators to their event.

⚙️ How it works

• Sync order: events, then presentations, then people, so every record can link to the sessions it belongs to.
• Accepted content only: by default, presentations are filtered to Accepted – Talk, Accepted – Talk and Poster and Accepted – Poster. You can change this filter in Studio.
• Field mapping: map MiraSMART fields to any standard or custom Swapcard field. Topics and audiences come as ready-made lists for multiple-choice fields.
• Times: session times are imported as event-local times, exactly as scheduled in MiraSMART.

🔄 Key behaviors

• Moves follow MiraSMART. If a presentation is moved to another event in MiraSMART, it moves in Swapcard too.
• Nothing is deleted. Records removed from MiraSMART are never deleted from Swapcard.
• People wait for their sessions. A person is imported once at least one of their sessions is in Swapcard. Presenters wait for their presentation specifically.
• Email identifies each person, so someone with several roles or presentations becomes one profile linked to all their sessions.
• Incomplete records are skipped and logged. Events or presentations that aren't scheduled yet, or have invalid times, are left out until they're ready.

💡 Pro tips

• Use the "Event or Presentation" field to tell parent sessions and nested presentations apart in filters and session lists.
• Renaming the parent/child labels: the link labels default to Session and Presentations and can be renamed in Studio to match your program's wording.
• Formatted abstracts: the abstract imports as HTML, but italics, superscript and subscript are not kept. Map Abstract Text (Text Only) if you'd prefer a clean plain-text version.
• Speaker roles: roles can be assigned automatically based on author type (e.g. Speaker, Poster Presenter, Organizer, Moderator) and event type. Contact your Swapcard team to set this up.

✅ Why it matters

• No more manual exports. Your program comes straight from MiraSMART.
• A structured program from day one, with presentations nested under their events and speakers already linked.
• Always in sync with your accepted abstracts as the schedule changes.

Changes to a registration now reach your external tools automatically. When someone registers, cancels, gets approved or is declined, Swapcard sends an update through webhooks and Zapier. Each update also shows whether the registrant has paid or still has a balance due.

What's Changing

Until now, registration changes stayed inside Swapcard. If someone cancelled, your CRM didn't know. And there was no way to see who had actually paid without exporting lists by hand.

Now your connected tools, such as HubSpot, stay up to date on their own.

How It Works

• Automatic updates. Your connected tools are notified whenever a registration is confirmed, pending approval, rejected, cancelled or abandoned.
• Payment visibility. Each update shows whether the registrant has paid in full or still owes a balance.
• Ready in Zapier. Registration and payment status can be used in your Zaps to filter, map and sync them to your CRM.
• No setup changes. This works with your existing webhooks and Zaps. Nothing breaks.

💡 Pro tips

• Add a filter to your Zap, for example only cancellations, so that just the updates you need reach your CRM.
• Use payment status to build follow-up lists of registrants with a balance due.

Swapcard's eShow integration now covers exhibitors. Company profiles, booth contacts, and package tier data sync automatically from eShow into your event app — so your exhibitor directory is always accurate without the manual lift.

Setting up your exhibitor directory shouldn't mean juggling two platforms and a spreadsheet. Swapcard's eShow connector has been extended to pull exhibitor data directly from eShow — company profiles, booth contacts, product categories, and package tiers — straight into your event app, automatically.

What's New

Swapcard already synced attendees, sessions, and speakers from eShow. Exhibitors were the missing piece. That gap is now closed.

When the sync runs, the following exhibitor data is mapped into Swapcard:

• Company name & profile — including description, logo, website, and email address.
• Address — street, city, and country, combined into a single location field.
• Booth number — mapped to the exhibitor's location in the event app.
• Product categories — surfaced directly on the exhibitor profile.
• Booth contacts — each contact is created as a Person in the Swapcard event and linked as a team member for their exhibitor. Attendees always know exactly who to speak to on the show floor.

Package Tier Mapping: Elite Exhibitors Get Their Due

The sync doesn't stop at profile data. It also reads each exhibitor's package tier from eShow and uses that to assign them to the correct Swapcard group — automatically.

Two tiers are supported:

• Basic → assigned to the standard exhibitor group.
• Elite→ assigned to a premium group, unlocking a full set of additional permissions in Swapcard:
  • document uploads, press releases, online product showcases, videos
  • Highlighted listing in the exhibitor directory
  • Directory profile header image
  • Premium positioning

No manual group assignment after import. Exhibitors land in the right tier from the first sync.

Why Organizers Will Love It

Exhibitor data is often the last thing to get updated and the first thing attendees complain about. With this sync in place:

• Your exhibitor directory reflects the ground truth in eShow — no re-entry, no version drift between platforms.
• Premium exhibitors are automatically surfaced with the visibility they paid for.
• Booth contacts appear as proper team members on each exhibitor profile, giving attendees a direct line to the right person.
• Organizers save hours that would otherwise go to CSV exports, copy-pasting, and chasing exhibitors for profile updates.

💡 Pro tips

• Make sure booth contact details stay consistent in eShow throughout the event lifecycle — Swapcard uses a combination of email and company ID to uniquely identify each contact. Changes mid-cycle can result in duplicates.
• Confirm your Elite package tier identifier in eShow before the first sync. If it changes, the tier mapping won't fire correctly and Elite exhibitors may land in the wrong group.

Swapcard's webhook system is a powerful tool for real-time integrations — but like any powerful tool, it needed a guardrail. Starting now, each customer account is limited to 20 webhook subscriptions per event. It's a small number that makes a big difference.

What's changing

Previously, there was no ceiling on how many webhook subscriptions could be created per customer. That opened the door to two common problems:

• Accidental overload — A developer iterating quickly on an integration could unknowingly create hundreds of duplicate subscriptions without realizing it, silently degrading performance.
• Automated proliferation — some tools auto-generate webhook subscriptions, and without a limit, those can stack up fast.
• Malicious abuse — In the worst case, a bad actor could flood the system with thousands of subscriptions and impact Swapcard's performance for everyone.

How it works

The fix is simple: 20 webhook subscriptions per event, maximum.

• If a customer already has 20 active subscriptions, any attempt to create a new one will be blocked with a clear error message.
• Existing subscriptions are unaffected — the limit applies to new creations going forward.
• The cap applies across all webhook events and endpoints for that customer account.

Why this matters

This isn't just a defensive measure — it's a reliability investment for every team building on Swapcard's API. Clean integrations perform better, are easier to debug, and don't silently eat up system resources in the background.

💡 Pro tip: If you're regularly hitting or approaching the 20-subscription limit per event, audit your active webhooks for duplicates or stale endpoints. A lean webhook setup is a healthy one.

We're excited to announce our new HubSpot integration — connecting your HubSpot CRM directly into Swapcard Studio to import contacts and companies as attendees and exhibitors, with real-time updates via webhooks & API support.

✅  Simple Authentication

Connect your HubSpot account by providing an access token generated from a private HubSpot Legacy App. Swapcard validates the token on entry and alerts you if anything needs adjusting.

✅  Import Contacts and Companies

The integration reads your HubSpot data using a dedicated Swapcard Event custom object and imports records directly into Swapcard — Contacts become People (Attendees, Speakers) and Companies become Exhibitors. Any HubSpot contact or company field is automatically available for mapping.

✅  Real-Time Sync via Webhooks

Changes in HubSpot — new contacts, updated fields, or new associations — are automatically reflected in Swapcard without manual re-imports, keeping your event data accurate throughout the entire event lifecycle.

✅  Flexible Field Mapping

Map any HubSpot field to standard Swapcard fields or your own custom fields, giving you full control over how your CRM data populates your event app.

💡 Why This Matters

With this integration, you can:

• Save time by eliminating manual CSV exports from HubSpot and uploads into Swapcard.
• Ensure accuracy by syncing your authoritative CRM data directly into your event.
• Stay up to date with real-time webhook sync so your attendee and exhibitor data is always current.

We're excited to announce a new integration that connects OpenWater directly into Swapcard Studio — enabling you to automatically import Sessions, Speakers, and Applicants from your OpenWater program into your event.

✅  Simple Authentication

Connect your OpenWater account by providing three credentials:

• Client Key — your OpenWater domain
• API Key — your OpenWater API secret
• Program ID — the numeric ID of the program to sync

Once entered, Swapcard validates your credentials immediately and alerts you if anything needs adjusting.

✅  Sync Sessions, Speakers & Applicants

The integration supports five object types — each independently toggleable:

• Sessions — scheduled conference slots, imported as Swapcard Sessions
• Applications — accepted submissions assigned to sessions, also imported as Swapcard Sessions
• Documents — speaker file uploads (slides, agendas) auto-imported with Applications
• Speakers — presenters and organizers listed in submissions, imported as Persons linked to their sessions
• Applicants — the OpenWater account holders who submitted proposals, imported as Persons

✅  Flexible Field Mapping & Import Filters

For each object, you can map both standard fields and dynamic fields sourced from your OpenWater form templates — including custom submission fields, round data, and speaker table columns.

Import filters let you control exactly which records come through — filter by session type, category, submission status, or any custom field value.

💡 Why This Matters

With this new integration, you can:

• Save time by eliminating manual exports from OpenWater and CSV uploads into Swapcard.
• Ensure accuracy by keeping your event app in sync with the accepted program directly from the source.
• Go live faster by automatically populating sessions, speakers, and profiles as soon as submissions are accepted and scheduled in OpenWater.

We're excited to share a preview of our upcoming iMIS integration — connecting your iMIS membership data directly into Swapcard Studio to automatically import your event registrants as attendees.

✅  Simple Authentication

Connect your iMIS account by providing:

• Username & Password — your iMIS credentials
• Host — your organisation's iMIS domain
• Instant Query name — the configured query that returns your registrant list

Swapcard validates your credentials on entry and alerts you if anything needs adjusting.

✅  Sync Registrants as Attendees

The integration reads your iMIS Instant Query and imports each registrant record as a Swapcard Person. Standard fields include name, email, company, and registration status — and any additional columns your iMIS administrator adds to the query automatically become available for mapping.

✅  Optional OpenWater Profile Enrichment

If you also use OpenWater, you can provide OpenWater credentials alongside your iMIS setup. Swapcard will automatically enrich each attendee record with their OpenWater profile data — matched by member ID — adding fields like biography, photo, credentials, and more.

✅  Flexible Field Mapping

Map any iMIS query field — or OpenWater profile field — to standard Swapcard fields or your own custom fields, giving you full control over how registrant data populates your event app.

💡 Why This Matters

With this new integration, you can:

• Save time by eliminating manual CSV exports from iMIS and uploads into Swapcard.
• Ensure accuracy by syncing your authoritative membership and registration data directly from iMIS.
• Enrich attendee profiles by combining iMIS registration data with OpenWater speaker profiles in a single automated flow.

We're adding a more flexible way to map attendees into groups within the Cvent integration. Earlier, group mapping was based on Registration Type. Now, you can also use Cvent's Audience Segments — giving you finer-grained control over how attendees are grouped in your Swapcard event.

✅  What's Changing

The existing Registration Type mapping remains fully available. The new Audience Segment option adds an alternative grouping method for events where Registration Type alone is not granular enough.

Audience Segments in Cvent allow organisers to group attendees based on packages, session selections, or other flexible criteria — independently of how they registered. With this update, those segments can drive group assignment directly in Swapcard.

✅  How It Works

When Audience Segment mapping is enabled, the sync will:

• Fetch all Audience Segments defined for the event from Cvent.
• Retrieve the attendees associated with each segment to build the segment-to-attendee mapping.
• Cross-reference with the full attendee list to combine segment membership with profile data in a single import.

Each attendee is then assigned to the corresponding Swapcard group based on their Audience Segment — in addition to, or instead of, their Registration Type.

💡 Why This Matters

With this enhancement, you can:

• Group attendees more accurately using the same segments already defined in Cvent, without duplicating configuration in Swapcard.
• Reduce manual work by eliminating the need to manually assign attendees to additional groups after import.
• Support complex event structures where a single Registration Type spans multiple attendee profiles or access levels.