Map Your Show REST API

Date & Time Parameters

• When providing Date & Time parameters in the API calls, these should be sent in accordance with the Eastern Time Zone.

Exhibitor Data

• Initially call /Exhibitors/Modified with a maximum 30 days date range. MYS account rep or the show can advise on the initial launch date of the exhibitor data so you know what date ranges need to be called to get the complete list. After the initial call the FromDate should be adjusted to the last date/time the function was called to only get changes made since the last call to that function.
• /Exhibitors - in order to get the in depth data of the exhibitor you will loop through the results of /Exhibitors/Modified and call /Exhibitors for each exhid that has a status of Added or Updated. This data will include all booth assignments, product categories assigned, booth contacts etc.
  • IsActive - this is a bit field indicating if that exhibitor is currently active or not. If it is not active it should never appear in the exhibitor list on the mobile app.
  • Booths - some shows have exhibitors that do not have booths assigned. It is up to you to clarify with the show staff if those exhibitors should be shown in the exhibitor list on the mobile app or not

Agenda Data

• Agenda data should be synched between your own data set on your servers and the MYS dataset not directly from the installed mobile app and MYS. This setup will significantly reduce the number of calls needed and allow you to keep an updated data set regardless of when the app is in use.
• /Users - will verify if an agenda exists in MYS for the given email address. Use POST to insert new user and PUT to update existing user.
• /Users/Modified - use this function to get a list of all agendas that have been updated for a given time period, within a maximum 30 days date range. After the initial call for /Users/Modified you will need to change the time range given to only get the list since the last time you called this function.
• /Agendas/Exhibitors - use GET to retrieve list of exhibitors in a users agenda, POST to add an exhibitor to their agenda, PUT to update the hasvisited or notes and DELETE to remove an exhibitor from their agenda.
• /Agendas/Meetings - GET returns the schedule of exhibitor meetings for a user
• /Agendas/Sessions - use GET to retrieve list of sessions in a users agenda, POST to add a session to their agenda and DELETE to remove a session from their agenda.
• /Agendas/Events - use GET to retrieve a list of user specific events, POST to add a user specific event, PUT to update a user specific event and DELETE to remove a user specific event.

Session/Conference Data

• /Sessions/Modified - use this function to get a list of all sessions that have been updated for a given time period, within a maximum 30 days date range. After the initial call for /Sessions/Modified you will need to change the time range given to only get the list since the last time you called this function.
• /Sessions/List - Returns complete session list with high level data only about that session - id, title, description, type, date, start and end time and location. This can include a large data set. Contact the MYS account rep for recommendations on how often to call this data. If MYS is only getting updates once a day there is no need to call this function more often.
• /Sessions - called per session and will return all known data about the session including speakers, handouts, tracks etc.

Response Codes

This is a list of some of the most common response codes you'll get from our REST API. We use standard HTTP Status Codes, a full list of which can be found at http://www.restapitutorial.com/httpstatuscodes.html

You should also get some written text back with any non-200 Status Code explaining the issue.

• 200 - OK
  • All parameters were valid and a successful response is being returned.
• 201 - Created
  • All parameters were valid and your record was created.
• 202 - Accepted
  • All parameters were valid and your requested changed were accepted.
• 400 - Bad Request
  • Invalid parameters were passed (Such as missing a required field, invalid formatting, etc).
• 401 - Unauthorized
  • User not logged in or invalid authorization key/GUID.
• 403 - Forbidden
  • API is refusing to accept your call for a reason other than unauthorized (API call limit reached, used violated some rules, etc).
• 409 - Conflict
  • Your request could not be completed due to a conflict.
• 429 - Too Many Requests
  • You have reached your API call limit.
• 500 - General Error
  • Your request could not be completed due to a general or unknown error. You should contact your MYS Account Manager if the error persists.
• 504 - Gateway Timeout
  • The call you made did not respond in a timely fashion. Please try your call again, or if you're passing in a date range to get a range of information, try a shorter period of time for your calls. You should contact your MYS Account Manager if the error persists.