---
title: "Build your connection."
description: "Bring your tools and event data together with the Brella Core API."
sidebar:
  label: Overview
  icon: book-open
  order: 0
---

<div className="brella-home">
  <div className="brella-intro not-prose">
    <p>Read event data, sync registrants, and manage your integrations with precise control over every permission.</p>
    <div className="brella-intro-actions">
      <a className="brella-button" href="/getting-started/authentication">Make your first request <span aria-hidden="true">↗</span></a>
      <a className="brella-text-link" href="/reference">Explore the API</a>
    </div>
  </div>

  <div className="brella-start-grid">
    <Card title="Start building" icon="key" href="/getting-started/authentication" cta="Authentication and access">
      Set up your token, choose your scopes, and make a request to the Core API.
    </Card>
    <Card title="Find your endpoint" icon="braces" href="/reference" cta="Resource reference">
      Explore the fields, filters, and operations available for each resource.
    </Card>
    <Card title="Follow a recipe" icon="code" href="/cookbook" cta="Write cookbook">
      Start from complete curl examples for creating and updating your event data.
    </Card>
  </div>
</div>

## A request starts here

Send your token in the `Brella-API-Access-Token` header. Use the organization and event IDs supplied by your team.

```shell
curl --request GET \
  --url "https://api.brella.io/api/core/organizations/30/events/319986/leads" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: YOUR_TOKEN"
```

<div className="brella-scope-note not-prose">
  <span className="brella-note-icon" aria-hidden="true">i</span>
  <div><strong>Your token defines your access.</strong><p>The same endpoint can return different fields, records, or permissions for different tokens. <a href="/getting-started/token-scopes">Understand token scopes</a>.</p></div>
</div>

## Explore the Core API

<div className="brella-resource-grid">
  <Card title="Registrants" icon="users" href="/reference/registrants">Connect registration data and keep attendee details in sync.</Card>
  <Card title="Meetings" icon="calendar" href="/reference/meetings">Work with meetings, participants, and networking timeslots.</Card>
  <Card title="Sponsors" icon="building" href="/reference/sponsors">Manage sponsor information and associated event resources.</Card>
  <Card title="Content sessions" icon="mic" href="/reference/content-sessions">Access sessions, speakers, tracks, and the event agenda.</Card>
  <Card title="Leads" icon="contact" href="/reference/leads">Read and maintain the leads captured at your event.</Card>
  <Card title="Analytics" icon="chart-no-axes-combined" href="/analytics">Explore event, audience, networking, and revenue metrics.</Card>
</div>

## Keep the essentials close

- [Reading data](/concepts/reading-data) — fields, filters, pagination, and related resources.
- [Responses and errors](/concepts/responses-and-errors) — response formats, status codes, and rate limits.
- [Integration checklist](/getting-started/integration-checklist) — the checks to make before going live.