Jade REST API

Sync event, participant, registration, housing, exhibitor, lead, sourcing, support, mobile, appointment, and payment data from your own systems.

The public /v1 API is read-first: most resources support list and detail reads with cursor pagination, ETags, incremental sync, account scoping, and PII redaction. Selected writes are available where the domain service is safely exposed today, including attendance records and exhibitor companies; workflow-heavy writes continue through organizer endpoints, participant flows, or dedicated tools.

Get started

  1. Ask your Jade administrator to issue you an API account.
  2. Note the access scope — which clients and events your token can reach, and whether PII fields are included in responses.
  3. Copy your bearer token the moment it's issued. It's shown once and is unrecoverable.
  4. Call any endpoint with Authorization: Bearer <token>. See the API reference for the full surface.

What's documented here

  • Authentication — bearer tokens, rotation, scope.
  • Pagination & caching — cursors, ETags, incremental sync.
  • PII & scope — what your token can see and what it can't.
  • Writing data — which resources currently accept writes and how scoped writes differ from workflow endpoints.
  • Webhooks — receive a signed POST when data changes (the push side of the integration surface).
  • MCP (AI agents) — let personal-assistant agents register people for events on their behalf, gated by email-OTP verification.
  • API reference — every endpoint, every parameter, generated from the same Zod schemas the server enforces.
  • REST API setup — step-by-step from "ask for an account" to "first authenticated call."
  • Webhook setup — stand up an endpoint, verify signatures, handle retries.
  • External Register POST setup — the anonymous pre-registration endpoint.
  • MCP setup — end-to-end walkthrough for building an AI agent that registers people for events on their behalf.
  • Lead Retrieval SDK — a single activation-code-authenticated GET endpoint for exhibitors to pull a scanned lead's fields and record the capture.

Need help?

Contact your account manager. Include your prefix (the first 8 characters of your token after the jdo_ prefix) so they can identify the integration without your secret.