Integration

Sympla integration

Sympla is a Brazilian event ticketing platform. As an event producer you can list your events and their presentations (sessions or dates), read orders with buyer, payment totals, invoice details and UTM attribution, list participants (one per ticket) with their ticket, sector, check-in state and custom form answers, look a participant up by ID or ticket number, and check participants in. The API exposes no route to create events, sell tickets or handle payouts; check-in from a raw QR code payload is left out (check in by ticket number instead), as are the older API versions 1.5.0 and 1.5.1. Authentication is a producer token generated in the Sympla account under My Account > Integrations, sent in the s_token header.

Connect Sympla How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Sympla.Built from the 14 Sympla tools below, on the connection you add once.

What you can do with Sympla

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Participant, 5 operations

get_participantGet participantGETReturns one participant of an event by participant ID: name, e-mail, order, ticket number and type, sector, prices, check-in state and custom form answers.
get_participant_by_ticket_numberGet participant by ticket numberGETReturns the participant holding a given ticket number in an event: name, e-mail, order, ticket type, sector, prices, check-in state and custom form answers.
list_event_participantsList event participantsGETLists the participants (one per ticket) of an event, one page at a time (cursor pagination). Filter by participant e-mail, by a ticket update date range and by cancelled tickets; useful to sync attendees into a CRM or to see who already checked in.
list_order_participantsList order participantsGETLists the participants (tickets) bought in one order of an event, one page at a time (cursor pagination), with ticket number, ticket type, sector, prices, check-in state and custom form answers.
list_presentation_participantsList presentation participantsGETLists the participants of one presentation of an event, one page at a time (cursor pagination). Same fields and filters as list_event_participants, restricted to that presentation.

Order, 3 operations

get_orderGet orderGETReturns one order of an event: buyer, status, order, approval and update dates, sale and net totals, discount code, invoice details and UTM attribution.
list_event_ordersList event ordersGETLists the orders (purchases) of one event, one page at a time (cursor pagination): buyer name and e-mail, status, dates, totals, discount code, invoice details and UTM attribution. Filter by order date range, buyer e-mail and cancelled orders.
list_presentation_ordersList presentation ordersGETLists the orders placed for one presentation of an event, one page at a time (cursor pagination). Same fields and filters as list_event_orders, restricted to that presentation.

Check in, 2 operations

create_check_in_by_participant_idCreate check in by participant idPOSTChecks in one participant of an event by participant ID and returns the check-in record (whether it is checked in, its date and its ID).
create_check_in_by_ticket_numberCreate check in by ticket numberPOSTChecks in the participant holding a given ticket number at an event.

Event, 2 operations

get_eventGet eventGETReturns one event of the authenticated producer: name, description, start and end dates, address, host, categories, publication and cancellation flags, image and public URL.
list_eventsList eventsGETLists the authenticated Sympla producer's events, one cursor page at a time. Filter by publication status and start date, sort by start date, end date or name, choose the returned fields. Pass pagination.next_cursor back as cursor for the next page.

Presentation, 2 operations

get_presentationGet presentationGETReturns one presentation (session or date) of an event: start and end dates in local time and UTC, open, enabled, published and private flags, URL and ticket sectors.
list_event_presentationsList event presentationsGETLists the presentations (sessions or dates) of an event, one page at a time (cursor pagination), with start and end dates, publication and privacy flags, URL and ticket sectors.

Use Sympla from Claude Code, Cursor or Codex

Connect Sympla in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Sympla operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Sympla

Create your workspace
Sign up free. Nothing to install.
Connect Sympla once
Add your Sympla connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.