canonical: https://jentic.com/apis/sympla.com.br/sympla-com-br

# Sympla API

The Sympla API provides access to events and attendee data on Sympla, the largest event management platform in Brazil. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list all events, get event by id. Covers 8 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- List all events
- Get event by ID
- Integrate Sympla API into automated workflows
- Query and filter Sympla API records by parameters
- Monitor Sympla API operational status and events

## Use cases

### Developer Tools Operations

Use the Sympla API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including list all events, get event by id, list participants for an event.

Example prompt: Call GET /events to list all events

### Automated Events Management

Automate events operations by combining multiple Sympla API endpoints. Agents can get event by id and then list participants for an event in a single workflow.

Example prompt: Call GET /events/{eventId} to get event by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sympla API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'list all events', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /events | List all events |
| GET | /events/{eventId} | Get event by ID |
| GET | /events/{eventId}/participants | List participants for an event |
| GET | /events/{eventId}/participants/{participantId} | Get a participant by ID |
| GET | /events/{eventId}/orders | List orders for an event |
| GET | /events/{eventId}/orders/{orderId} | Get an order by ID |
| GET | /events/{eventId}/orders/{orderId}/participants | List participants for an order |
| POST | /events/{eventId}/participants/{participantId}/checkIn | Check in a participant |

## Key resources

- **Events** — Operations related to Events
- **Orders** — Operations related to Orders
- **Participants** — Operations related to Participants

## Why Jentic

- **Setup:** Wiring the Sympla API by hand means sending the s_token header to the api.sympla.com.br host and shaping the requests for events, participants, and orders yourself. Through Jentic you install once, import Sympla from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Sympla puts the event id in the URL path (/events/{eventId}), so a rule can pin your agent to one event: it can read that event's participants and orders and nothing else. You choose the operations it may call, so state-changing ones like checking a participant in are not included unless you add them.
- **Credential handling:** Your Sympla token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list events' or 'get an event's participants', and Jentic returns the matching Sympla operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Sympla API use?

The Sympla API uses an API key passed in the `s_token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list all events with the Sympla API?

Yes. Use the GET /events endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Sympla API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list all events through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all events'. Jentic returns the matching Sympla API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sympla API have?

The Sympla API exposes 8 endpoints covering events, orders, participants operations.

### Can I limit what my agent is allowed to do with the Sympla API?

Yes. Because you run Jentic One yourself, your own rules decide which Sympla operations and credentials your agent may use. Since Sympla puts the event id in the URL path such as /events/{eventId}, you can pin the agent to a single event and let it read only that event's participants and orders. You also choose the operations it may call, so a state-changing action like checking a participant in via POST /events/{eventId}/participants/{participantId}/checkIn is excluded unless you add it.