Skip to main content

API keys

Create scoped API keys so your own systems can read and update your show data.

API keys let your own systems, such as a CRM, registration system or website, read and update your show data in Map D. Open API Keys in the organization sidebar to reach the API keys page.

Owners manage every key. Show Managers and Associates manage keys for the shows they work on: they see only keys whose shows are all theirs, and only an Owner can create a key for all shows.

The API keys page with View API documentation, Create key and Manage embed profiles buttons

Create a key

  1. Select Create key

    Under Key name, give the key a name that says what uses it, for example "Partner integration".

  2. Choose which shows

    Select Apply to all shows (Owners only), or choose specific shows under Show access.

  3. Choose what it can do

    In the scope grid, allow Read, Write or Delete for each kind of data: show, exhibitors, sponsors, schedules, speakers, attendees, help center and documents. Grant only what the integration needs. Exhibitors also covers each exhibitor's booth staff, products and services, photos and videos.

  4. Copy the secret

    Map D shows the secret once. Select Copy secret and store it somewhere safe, such as your password manager. It will not be shown again.

Edit or delete a key

Open More actions on a key and select Edit to change its shows or scope. The name cannot be changed. To revoke it, open More actions, select Delete, then Delete key. Anything using it stops working immediately, and this cannot be undone.

For developers

Your integration can use your organization's configured custom domain at the same API paths as the main app. It uses the same keys, permissions and request allowance on either domain. Changing domains does not require a new key. Use the current domain directly; older platform addresses are not interchangeable with it.

Select View API documentation, or share the API guide with your developer. It covers authentication, request signing, and every endpoint.

Attendees and speakers are addressed by the person's id. Somebody who both attends and speaks is one record, with the same id on both endpoints, so your system can keep one row per person. Removing an attendee or a speaker through the API takes them off that list and keeps their details for the show, in case they are still on another one. Removing somebody who is not on the list answers "not found".

Removing booth staff, a product, a photo or a video through the API takes it off the exhibitor's profile everywhere, the same as Remove in Map D. A removed product can be restored by setting it back to active.

Your integration can also list booth inventory and assign exact booths to an exhibitor, including booths on different maps. Exhibitors Read access allows listing booths and their current assignments; Write access allows replacing an exhibitor's assignments. Your developer uses each booth's unique ID, so repeated booth numbers on different maps are kept separate.

A replacement either succeeds in full or changes nothing. A booth tied to the exhibitor's active order cannot be removed this way, and held or unavailable booths cannot be newly assigned. Shared booths stay assigned to their other exhibitors. Assigning a booth does not create an order or take payment. The older booth text field remains a display label; changing it does not assign or release booths.

Your integration can create, update and delete booths and booth types with the corresponding Exhibitors access. These changes update the Map Editor and any published map together. Close the Map Editor before making them. A booth that has assignments or order history cannot be deleted, and a booth type still in use cannot be deleted. Changing a type's dimensions does not resize existing booths.

Removing an exhibitor through the API also removes its booth assignments. Shared booths keep their other exhibitors. If an active booth order prevents removal, the entire request is refused; release or cancel the order through your usual process first. Archived exhibitors can be included in API lists, and lists are paginated. Your integration can also read and update exhibitors' public social links and postal addresses, and find a show's new ID from its previous ID or its link name.

API keys normally allow 120 requests per minute across all their shows. Contact Map D if your integration needs a higher allowance. Changing a key's shows or scope does not increase its allowance.

Still need help?

Contact your Map D account team. Include your show name and, if something looks wrong, a screenshot of the page.

Last updated November 6, 2026