m|events API - Before Getting Started

In order to set up new data sources that connect with the API, first contact your account manager to receive the following: 

1. Base URL generally https://api.us.m-anage.com
2. API Username this would likely be m-events@ativsoftware.com
3. API Password provided to you by your account manager
4. EventID typically a 4 digit number e.g. 2601
5. Event Shortcode likely your event abbreviation and the year e.g. abc2026

Once you have received the details, you will be able to set up Import Sources in the Conference app builder. 

Access the menu item in the Conference App Builder where you would like to import data: 

Agenda for session data

Speakers for presenters

Media for abstracts

Setting Up the Initial Data Sources and Running the Initial Import

Speakers

1. Access the Conference App Builder (From our website, choose Organizer Login > EventPilot on the top right)
2. Select your project
3. Navigate to Agenda > Speakers
4. Click Add Import Source (note: you may need to click the carrot to expand the import card before this button is visible) 
5. Enter a logical name for the source to indicate where this import is coming from e.g. M-Events API 
   1. Tip: we recommend including the M-Events event ID in the name. When you clone your project in the future, you'll then easily know if you need to update your import source. 
6. Select M-Events from the Source dropdown
7. Select Next
8. As prompted on the screen, enter:
   1. Base URL
   2. API Username
   3. API Password
   4. EventID
   5. Event Shortcode

9. If you have used import customizations in the past, ask your ATIV Project Manager to add your Customization Code (generally your ORG ID in the App Builder) or Custom Import Parameters

10. Choose Yes or No to Link Co-Speakers (you can always go back and change this setting and try importing)

11. Select Next

12. Mapping
    Complete the field mapping for the table

    1. id > Speaker ID

    2. firstname > First Name

    3. last_with_creds > Last Name

    4. email > Private Emali

    5. bio > Bio

    6. country > Filter 1

    7. institute > organization

    8. profileurl > URL

13. Next to run the import

14. If there are errors in your data, review: Common Conference App Builder Import Data Errors and Import Exclusion Reasons

Sessions

1. Navigate to Agenda > Sessions
2. Click Add Import Source (note: you may need to click the carrot to expand the import card before this button is visible) 
3. Enter a logical name for the source to indicate where this import is coming from e.g. M-Events API 
   1. Tip: we recommend including the M-Events event ID in the name. When you clone your project in the future, you'll then easily know if you need to update your import source.
4. Select M-Events from the Source dropdown
5. Select Next
6. As prompted on the screen, enter:
   1. Base URL
   2. API Username
   3. API Password
   4. EventID
   5. Event Shortcode

7. If you have used import customizations in the past, ask your ATIV Project Manager to add your Customization Code (generally your ORG ID in the App Builder) or Custom Import Parameters

8. If you wish to Display Disclosures in the session detail view, select Yes 

9. If you wish to Link to Co-Speakers in the session detail view, select Yes

10. Select Next

11. Mapping
    Complete the field mapping for the table

    1. id > Session ID

    2. number > Session Number

    3. type > Session Type

    4. title > Session Title

    5. description > Description

    6. room > location

       1. Any commas added in the room or venue name are removed as those symbols are not supported for locations. Learn more in this article: Can I use symbols like slashes, semicolons, etc. for locations (rooms, booths), tracks and metadata? My pin drop or filter is not working? 

    7. date > Date

    8. start > Start Time 

    9. end > End Time

    10. parent > Parent Session

    11. speakers > Speaker ID

    12. If you have in your data: session_groups, presentation_type, presentation_category, you can map those to Filter 1, Filter 2, and Filter 3

    13. Session location: You can choose to import just the room name or a concatenated version of the romance and venue name.

12. Next to run the import

13. If there are errors in your data, review: Common Conference App Builder Import Data Errors and Import Exclusion Reasons

Abstracts (Media)

1. Navigate to Media > Media Data
2. Click Add Import Source (note: you may need to click the carrot to expand the import card before this button is visible) 
3. Enter a logical name for the source to indicate where this import is coming from e.g. M-Events Abstracts 
   1. Tip: we recommend including the M-Events event ID in the name. When you clone your project in the future, you'll then easily know if you need to update your import source.
4. Select M-Events Abstracts from the Source dropdown
5. Select Next
6. As prompted on the screen, enter:
   1. Base URL
   2. API Username
   3. API Password
   4. EventID
   5. Event Shortcode

7. If you have used import customizations in the past, ask your ATIV Project Manager to add your Customization Code (generally your ORG ID in the App Builder) or Custom Import Parameters

8. Select Next

9. Mapping
   Complete the field mapping for the table

   1. mediaid > Media ID

   2. sessionid > Session ID

   3. title > Title

   4. default_subtitle > Subtitle

   5. type > Media Type

   6. description > Description 

   7. default_filter > Filter 1

   8. keywords > Filter 2

   9. topic > Filter 3

   10. sub_topic > Filter 4

   11. embargo > Start

10. Next to run the import

11. If there are errors in your data, review: Common Conference App Builder Import Data Errors and Import Exclusion Reasons

ePoster PDF Links (Media)

1. Navigate to Media > Media Data
2. Click Add Import Source (note: you may need to click the carrot to expand the import card before this button is visible) 
3. Enter a logical name for the source to indicate where this import is coming from e.g. M-Events PDFs 
   1. Tip: we recommend including the M-Events event ID in the name. When you clone your project in the future, you'll then easily know if you need to update your import source.
4. Select M-Events Abstracts from the Source dropdown
5. Select Next
6. As prompted on the screen, enter:
   1. Base URL
   2. API Username
   3. API Password
   4. EventID
   5. Event Shortcode

7. If you have used import customizations in the past, ask your ATIV Project Manager to add your Customization Code (generally your ORG ID in the App Builder) or Custom Import Parameters

8. Fill in the Embargo Date field if your ePosters should not yet be viewed. The format is yyyy-mm-dd. For example 2027-03-15 

9. Default Subtitle for example ePoster

10. Select Next

11. Mapping
    Complete the field mapping for the table

    1. mediaid > Media ID

    2. sessionid > Session ID

    3. title > Title

    4. map subtitle > Subtitle if you entered a subtitle in the previous step. Otherwise map default_subtitle > Subtitle

    5. type > Media Type

       1. select type2 if the page must open in an external browser window

       2. select type3 if the link can only be opened by logged in users

    6. url > URL

    7. default_filter > Filter 1

    8. embargo_date > Start

12. Next to run the import

13. If there are errors in your data, review: Common Conference App Builder Import Data Errors and Import Exclusion Reasons

Filters

If you are importing filter keywords, ensure to open the filter card to: 

• set the filter label
• adjust the filter display order

Incremental Imports after Setup

1. Return to the Conference App Builder, log in, and access your project
2. You have three different import options: 
   1. Import all at once
      Select the Home menu > Import All Data 
   2. Import one data set (e.g. just speakers or just sessions or just media)
      To import all sources for a given table individually, visit that page of the Conference App Builder (e.g. Agenda > Sessions) and choose Import All [Agenda]
   3. Import one source only
      To import just one single source, visit that page of the Conference App Builder (e.g. Agenda > Sessions), expand the import card if necessary, and select the Import button beside a single data source
      
      Note: If you manually import individual sources, ensure to import all related sources (Sessions, Speakers, Media) or you may be seeing orphans errors.
3. If there are errors in your data, review this article: Common Conference App Builder Import Data Errors and Import Exclusion Reasons
4. Select the Publish Menu on the top left and Publish to Proof
5. After reviewing your data update in the proof version on iOS and Android, you may publish to live by selecting Publish Live Data

FAQ

I have made changes in M-Events and imported but I am not seeing the content updated? 

You may need to wait 15-30 minutes before your changes propagate into the API. 

What triggers which sessions / presentations are imported into EventPilot from M-Events? 

The Published field in Planstone must be set to true

What are the M-Events session (parent) and presentation (child) IDs in the EventPilot platform?

For parent sessions the Planstone Id field is "schedid" and for presentations (child) sessions, it is the "pslinkid" field.

How do I remove a session from Eventilot?

Set the Published field in M-Events to false and then reimport your data into EventPilot.