Skip to main content
Soventro

Use the API and manage API keys

Create API keys so your own systems can read events and registrations and create registrations, choose what each key may do, and revoke keys you no longer use.
From the video guide Integrations, with its transcript.

The Soventro API lets your own systems read your events, attendee types and registrations, and create registrations, across your whole organization. It's for your developers or an integration partner. They'll find the full reference, with examples, on the developer page.

Create a key

  1. Choose Integrations in the organization menu.
  2. Under API keys, enter a Name that says what uses the key, for example "Website sync".
  3. Under Permissions, tick what the key may do. The choices are listed below.
  4. Click Create key.
  5. Click Copy and store the key somewhere safe, such as your server's secret settings.

The permissions are:

  • events:read: read events and their attendee types.
  • registrations:read: read registrations, including names, emails and answers.
  • registrations:write: create registrations under the public rules.

The key is shown only once. Soventro keeps only a scrambled copy that can't be turned back into the key. If you lose it, revoke it and create another.

Revoke a key

Click Revoke… next to the key, then Revoke now. It stops working at once and can't be turned back on. Revoked keys stay in the list, marked Revoked, so you can see their history.

Each key shows when it was created and Last used, so you can spot keys nothing uses anymore.

What the API can do

  • List your events, or get one event.
  • List an event's attendee types, with price, capacity, access and approval.
  • List an event's registrations, with person, type, answers and money, or get one registration. Your developer can ask for only those changed since the last sync.
  • Create a registration.

Registrations created through the API follow exactly the same rules as your registration form: dates, invitations, eligibility, approval, capacity, discounts, required questions, and one registration per person per event. A key gets no staff overrides. Paid registrations come back with a one-time link the attendee uses to pay on Soventro's payment page. The API never takes card details.

The API doesn't cancel or edit registrations. Do that in Soventro.

Limits

  • Up to 25 active keys per organization.
  • Each key can make 600 read requests and 120 write requests a minute.
  • Lists return up to 100 records at a time.

Who can manage keys

Only Owners and Admins see Integrations and can create or revoke keys.

Keep keys safe

  • A key works for your whole organization. Give each system its own key, with only the permissions it needs.
  • Keys belong on a server. Never put one in a web page, a mobile app or a shared spreadsheet.
  • If a key may have leaked, revoke it right away and create a new one.
  • If your account is suspended or closed, its keys stop working.

Common questions

Is there a Zapier or Make app? There's no ready-made app. Automation tools that can call a web address with a key, or receive webhooks, can connect to Soventro. See Send events to other systems with webhooks.

Is this the same as the registration API on the Embed & API page? No. That one has no keys and only does what your public registration form does, for building your own form. See Embed registration on your website.

Still need help?

Email the Soventro team and a person will get back to you during business hours (US Eastern).

info@soventro.com