CRM API

The CRM API is the programmable side of Sessionboard CRM. It has its own reference, MCP tools and release notes, apart from the other Sessionboard products.

Base path

CRM is organization-level, so every operation starts at /v1/organization/{orgId}/crm. The same operations are served under /v1/org/{orgId}/crm, and under /v1/crm with the organization taken from the token. They run on the same regional hosts as the rest of the API: public-api.sessionboard.com in the US and public-api-eu.sessionboard.com in the EU.

What you can do

People

Everyone the organization knows, one row per email, tagged speaker, member, customer, prospect, influencer or attendee: filter by tag chips (any or all) and company, warm opportunities (warm=true), add, change, tag in bulk, delete and export; one person’s companies and signals.

Companies

Companies tagged sponsor or exhibitor: list with tag chips, add, change, delete and export; one company’s people, contracts and pipeline; link and unlink the people who work there.

Contacts

The platform record behind a speaker or a company’s person, which the pipeline and contracts use: search, read, add, change, export.

Tags

List your tags with their counts, create, rename and delete them. Deleting a tag keeps its contacts.

Import

Get the sample file, read a CSV’s columns, preview an import without saving anything, then import, matched by email, 250 rows a call.

Connections

List the CRMs, AMSs and event platforms you can read people from, connect and test them, and discover who they hold before importing: contacts from HubSpot, Salesforce and iMIS, or one event’s speakers from Cvent, Swoogo, Bizzabo, ON24 and Goldcast.

Hand-offs

Where a selection can go (Marketing, Sessions, Learning, Awards) and handing it over as a list, with the link that opens the app or its trial page.

Pipeline

List the stages with their counts; search, filter, sort, page and export the pipeline; add up to 200 contacts at once; move an entry to another stage with a note; read its history; archive it.

Contracts

List, read and export contracts; send one for signature from a published template with Sessionboard e-sign; resend or void it; get its PDF; list templates and add a built-in speaker, sponsor or exhibitor starter.

Discovering people in a connected app only reads: it writes nothing in Sessionboard or in the app, and only counts an event’s attendees. Review the rows it returns, then send the ones you choose to POST …/crm/import with source set to the app and target set to people or companies. An event platform’s attendees are counted by discovery and brought in with POST …/crm/apps/{appId}/attendees, which runs the platform’s own attendee sync into People. A person becomes a contact (the record the pipeline and contracts use) when they’re tagged speaker, linked to a company, or added with POST …/crm/people/add-to-contacts; the person and the contact stay two records, linked. PUT …/crm/apps/{appId}/sync keeps a source in sync nightly, and answers 403 with code: sync_disabled where that isn’t turned on.

Only sending, resending and voiding a contract emails anyone: the signer. Confirm the recipient with a person before you call them. The pipeline and contracts are the Sessionboard platform’s own, so an organization that moves to the platform keeps them. Editing a template’s wording or signer roles is done in Sessionboard’s template editor, not through the API.

Request bodies are camelCase (firstName, companyIds, updateExisting, remoteEventId, contactIds, stageId, templateId); responses are snake_case. Standard fields only: GET …/crm/fields lists them, and custom fields are a Sessionboard platform upgrade.

People and companies are free to store. CRM is free up to 1,000 active contacts (people you emailed, invited, sent a contract or a form, scheduled in a session, or who registered, in the last 365 days, once per email across CRM and Marketing); paid plans above that are yearly. Going over the limit blocks nothing. If a paid plan ends unpaid, writes answer 403 with code: plan_read_only, and everything can still be read.

CRM needs the read:crm and write:crm scopes; see Authentication. AI assistants can do the same work with the CRM MCP tools. Release notes are in the CRM changelog.