Masterconf API

What you can build

• Sync registrations into your CRM

  Walk the registrations of an event and keep your CRM up to date with every new participant.

• Show your events on your site

  List your events with their dates and venues, and publish them on your own website.

• Publish accepted papers

  Read the papers of a call for papers by status, with their authors and themes, and publish your programme.

Your first call in three steps

1. Create a key

   An administrator creates an API key in the console, under Integrations (« Intégrations »). Copy it at once: it is shown only once.

2. Call the API

   Send the key in the Authorization: Bearer mcf_… header. GET/v1/account tells you which organization and which key the request used.

   Request

   curl

   curl -G https://api.masterconf.com/v1/account \
     -H "Authorization: Bearer mcf_your_key"

   JavaScript

   const res = await fetch("https://api.masterconf.com/v1/account", {
     headers: { Authorization: "Bearer mcf_your_key" },
   });
   const data = await res.json();

   Python

   import requests
   
   res = requests.get(
       "https://api.masterconf.com/v1/account",
       headers={"Authorization": "Bearer mcf_your_key"},
   )
   data = res.json()

3. List registrations

   Pick an event and list its registrations with GET/v1/registrations, newest first.

   Request

   curl

   curl -G https://api.masterconf.com/v1/registrations \
     -H "Authorization: Bearer mcf_your_key" \
     --data-urlencode "event=EVT-5a1f0c2e-3b7d-4e91-9c2a-1d6e8f4b7a30"

   JavaScript

   const params = new URLSearchParams({
     "event": "EVT-5a1f0c2e-3b7d-4e91-9c2a-1d6e8f4b7a30",
   });
   
   const res = await fetch(`https://api.masterconf.com/v1/registrations?${params}`, {
     headers: { Authorization: "Bearer mcf_your_key" },
   });
   const data = await res.json();

   Python

   import requests
   
   res = requests.get(
       "https://api.masterconf.com/v1/registrations",
       params={"event": "EVT-5a1f0c2e-3b7d-4e91-9c2a-1d6e8f4b7a30"},
       headers={"Authorization": "Bearer mcf_your_key"},
   )
   data = res.json()

Resources

• Account

  The account the API key belongs to: your organization, and the key of the request with its scopes and its expiry.

• Events

  An event of your organization: a conference, a congress, a trade fair… Its registrations, calls for papers and papers link to it by its id.

• Registrations

  A registration of a participant to an event (an attendee, a reviewer, an exhibitor, a sponsor…), with its ticket and its check-in presence. Its form answers, orders and payments are never part of it.

• Calls for papers

  A call for papers of an event: the window in which authors submit their papers, and the themes they submit them to.

• Papers

  A paper submitted to a call for papers: its title, its summary, its authors (names and affiliations, never an e-mail), its themes and its verified journal references. Its reviews, reviewers and scores are never part of it.

Learn the concepts

• AuthenticationHow API keys work, which scopes they carry, and how they expire and are revoked.
• Handling errorsThe error object, the difference between its type and its code, and which errors to retry.
• PaginationHow lists are paged with a cursor, how to walk them, and how to keep a copy in sync.
• Expanding responsesReplace the id of a linked object with the object itself, and include the fields lists leave out.
• SearchFind registrations with a small query language, and page through the results.
• VersioningWhat can change within v1, what never does, and how to write a client that keeps working.
• Rate limitsHow many requests a key can send, how to read the limit headers, and how to back off.
• Request IDsEvery answer carries an identifier. Log it, and quote it when you contact support.
• Data left outWhat the API never returns, on purpose, and why.