> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fuseai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Programmatic access to Fuse: prospect search, lists, enrichment data, exports, and outbound campaigns.

The Fuse API lets you drive the full Fuse workflow from your own systems: find prospects, organize them into lists, attach your own data with custom columns, export enriched results, and launch email and LinkedIn campaigns.

Everything the API returns is plain JSON over HTTPS, authenticated with an API key you create in the Fuse app. If you have used APIs like Stripe or Anthropic, the shape will feel familiar: predictable resource-oriented paths, standard status codes, one error envelope everywhere, and rate-limit headers on every response.

## Base URL

```text theme={null}
https://api.tryfuse.ai/api/v1
```

All endpoint paths in this documentation are relative to this base URL. The API is served only over HTTPS.

## A 30-second tour

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Make your first request and build a list from a live prospect search in about five minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Create an API key and learn both accepted forms of the Authorization header.
  </Card>

  <Card title="Guides" icon="map" href="/guides/build-a-list-from-search">
    Task-oriented walkthroughs: search, lists, custom columns, exports, and campaigns.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference">
    Every endpoint with schemas, examples, and an interactive playground.
  </Card>
</CardGroup>

## What you can build

| Surface             | What it does                                                                                          | Where to start                                               |
| ------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| **Prospect search** | Query Fuse's people database with structured filters (title, seniority, industry, location, and more) | [Run a people search](/api-reference)                        |
| **Lists**           | Create lists, add or upload contacts, page through rows with enrichment data                          | [Build a list from search](/guides/build-a-list-from-search) |
| **Custom columns**  | Attach your own typed data (strings, numbers, dates, booleans, URLs) to contacts in a list            | [Custom columns](/guides/custom-columns)                     |
| **Exports**         | Asynchronously export any list to CSV and download it from a presigned URL                            | [Export a list](/guides/export-a-list)                       |
| **Campaigns**       | Create manual or AI-generated outbound campaigns, edit steps, and approve them to start sending       | [Campaigns end to end](/guides/campaigns)                    |

## Conventions used throughout

* **IDs** are opaque strings (`"68a1f20b9c41d20014b3e901"`). Never parse or construct them.
* **Timestamps** are ISO 8601 in UTC (`"2026-07-27T10:00:00.000Z"`).
* **Success responses** are keyed by the entity they carry — `{ "list": ... }`, `{ "campaign": ... }`, `{ "user": ... }`. Paginated collections use `{ "data": [...], "pagination": ... }` ([pagination](/concepts/pagination)).
* **Errors** always use one envelope with a stable machine-readable `code` ([errors](/concepts/errors)).
* **Asynchronous work** (exports, saving search results, campaign initialization) returns `202 Accepted` with an id you poll. Nothing long-running blocks a request.

## Need help?

Write to [support@fuseai.com](mailto:support@fuseai.com) and include the `request_id` from any error response — it lets us trace the exact request in our logs.