# Leads API

Source: https://swapcard.dev/leads-api/about-the-api


Give exhibitors their leads where they work: in their CRM, marketing tools or a custom badge-scanning app.

:::note[Built for exhibitors]
The Leads API uses an **exhibitor** API key, created in the Exhibitor Center, not the organizer key used by the Content API. See [Exhibitor authentication](/exhibitors/authentication).
:::

## What you can do

| Use case | Start with |
| --- | --- |
| Find the booths a user can act for | [List your booths](/content-api/examples/my-exhibitors) |
| Capture leads from your own scanning app | [Scan badges](/content-api/examples/scan-badges) |
| Sync collected leads to a CRM | [Export leads](/content-api/examples/leads) |
| Build either end to end | [Integration guide](graphql-leads-api-how-to-integrate.md) |

## Endpoint

The Leads API is a GraphQL API with a single endpoint. Every query and mutation is a `POST` to:

```sh
https://developer.swapcard.com/exhibitor/graphql
```

## Get started

- **Get a key:** follow [Exhibitor authentication](/exhibitors/authentication).
- **Explore the schema:** run live queries in the [API Explorer](graphql-leads-api-explorer.mdx).
- **New to GraphQL?** Read [Learn GraphQL](/guides/graphql-learning).

## Limits and versioning

- Requests are rate limited. See [Rate limits](graphql-leads-api-limitations.md).
- Schema changes are announced in the [Changelog](graphql-leads-api-changelog.md) and follow the [versioning and deprecation policy](/deprecation-policy).
