# Sympla Events API

> Sympla featured events in Brazil: dates, venues, organizers, ticket prices and availability

- Vendor: `symplaeventsapi` · version 1.0 · category Entertainment · tags sympla api, brazil events api, event tickets api, sympla events api, brazil shows api, ticketing api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/symplaeventsapi
- This document: https://apiclay.com/docs/symplaeventsapi.md
- OpenAPI 3.1: https://apiclay.com/api/symplaeventsapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `symplaeventsapi`
- Updated: 2026-11-18

## About

## Sympla Events API

Public discovery data from Sympla, a Brazilian event ticketing platform: the home-page highlight feed of featured events (name, start and end dates, venue with address and coordinates, city and state, organizer, themes and tags, ticket price range and availability, sold-out flag, event URL), optionally ranked for a city, plus the home page's component feed with sponsored events and event collections.

Data comes from **sympla.com.br** (https://www.sympla.com.br). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/highlights?limit=20&amp;city=sao-paulo-sp`, or `/home?components_limit=13` for collections and sponsored events.

### Routes

#### GET `/highlights` - Highlights
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| limit | query | number | no | Number of events (about 160 are featured). |
| city | query | string | no | City slug such as `sao-paulo-sp` or `porto-alegre-rs`; ranks that city's events first rather than filtering. |

Returns: `results[0].hits` array of events: `event_id`, `name`, `start_date` and `end_date` (Unix), `start_date_formats`, `location` (`name`, `address`, `city`, `state`, `zip_code`, `slug`), `_geoloc`, `organizer` (`id`, `name`, `email`), `theme`, `subtheme`, `tags`, `images`, `tickets` (`min_price`, `max_price`, `available_tickets`, `is_sold_out`), `event_url`; plus `nbHits`.

#### GET `/home` - Home feed
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| components_limit | query | number | no | How many page components to return (13 in all). |
| afterComponentsCount | query | number | no | Offset into the component list, `0` first. |

Returns: `components` array: each has `label`, `uuid`, `response_type` and `response` (sponsored events with `title`, `start_date`, `location`, `link_page`; collections with `label`, `slug`, `description`, images; event cards).

### Caveats

- Responses include organizer names and contact emails and Sympla's own sales signals (`gmv`, `pct_sales`, view counts) exactly as the site's API returns them; handle that personal data under the LGPD and other applicable law.
- City ranking is a preference, not a strict filter.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by sympla.com.br.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /highlights — Highlights
- Gateway: `GET https://api.apiclay.com/v1/api/symplaeventsapi/highlights`
- Public query params: `limit` (number), `city` (string)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /home — Home feed
- Gateway: `GET https://api.apiclay.com/v1/api/symplaeventsapi/home`
- Public query params: `components_limit` (number), `afterComponentsCount` (number)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/symplaeventsapi/highlights" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
