# Developer overview (/docs/developers)

Read Bloss data with the Platform API, let AI agents such as Claude read it through MCP, and get alerts with webhooks.

Bloss gives you three ways to get data out. All of them are read-only: nothing in Bloss can be changed through them.

<Cards>
  <Card title="Platform API" href="/docs/developers/platform-api">

    Read your own data as a creator or coach (free), or a brand's data as its
    admin on the Scale plan: creators, videos, analytics, payouts and more.

</Card>
  <Card title="AI agents (MCP)" href="/docs/developers/mcp">

    Connect Claude, ChatGPT, Cursor and other agents, and ask questions about
    your Bloss data in plain language.

</Card>
  <Card title="Webhooks" href="/docs/developers/webhooks">

    Bloss alerts your Discord channel or your own URL when a video crosses a
    view target, a video link goes dead, a creator stops posting, and more.

</Card>
</Cards>

## Which one should I use? [#which-one-should-i-use]

| You want to | Use |
| --- | --- |
| Read your earnings, videos and brands as a creator, or your students as a coach | The [Platform API](/docs/developers/platform-api) with a [personal token](/docs/developers/api-tokens). Free. |
| Read a brand's creators, videos, analytics or pay from your own code | The [Brand API](/docs/developers/platform-api#brand-api), part of the Platform API. Scale plan. |
| Ask an AI agent about your data | The [MCP server](/docs/developers/mcp). Same rules as the Platform API. |
| Be told when something happens in a brand | [Webhooks](/docs/developers/webhooks). |
| Keep an existing campaign integration running | The [Campaign API (v0)](/docs/developers/authentication). It keeps working; new integrations should use the Platform API. |

## Quickstart [#quickstart]

<Steps>
<Step>

### Create a token [#create-a-token]

Go to <UiPath>Account › API tokens</UiPath> and click **Create token**. Tick **Your account: name, email, roles and memberships**, plus whatever else you need, and copy the token. It starts with `blsp_` and is shown only once. See [API tokens](/docs/developers/api-tokens).

<OpenInBloss to="account">Open Account Settings</OpenInBloss>

</Step>
<Step>

### See who you are [#see-who-you-are]

`GET /me` returns your account and every brand you belong to, with the ids the other endpoints take:

```bash
curl https://www.bloss.app/api/v1/me \
  -H "Authorization: Bearer $BLOSS_API_TOKEN"
```

</Step>
<Step>

### Read something [#read-something]

For example, the numbers on your creator Dashboard (views, followers and top videos across every brand) for October. This needs the **Your creator profile, stats, brands, videos, bounties and games** permission:

```bash
curl "https://www.bloss.app/api/v1/creator/stats?from=2026-10-01&to=2026-10-31" \
  -H "Authorization: Bearer $BLOSS_API_TOKEN"
```

Every endpoint is in the [Platform API reference](/docs/developers/platform-api-reference).

</Step>
</Steps>

## What you can build [#what-you-can-build]

- **Client reporting**: show an agency client live reach and spend for their campaign with the [Brand API](/docs/developers/platform-api#brand-api).
- **Budget alerts**: read campaign spend with a `prepayment` and act when `atThreshold` turns `true`.
- **A creator dashboard**: your views, earnings and payouts across every brand in one place.
- **Coaching check-ins**: which students haven't posted this week, and how their views are trending.
- **An AI assistant**: let Claude answer "how did we do this week?" through [MCP](/docs/developers/mcp).

<Callout title="Read-only, and only what you can see">

  The API and MCP server read only what you can already see in Bloss, within
  the permissions you give each token. Nothing can be changed, posted or paid
  through them.

</Callout>