---
title: "Quickstart: your first API call | distribution.tech"
description: "Create an API key, read how well the network reaches your audience with one curl call, then start a campaign and quote its plan."
canonical: https://distribution.tech/docs/quickstart
generator: md-live-route
generated: 2026-10-19T11:02:38.755Z
---

# Quickstart: your first API call | distribution.tech
-   [Getting started](https://distribution.tech/docs)
-   [API reference](https://distribution.tech/docs/api)
-   [MCP and agents](https://distribution.tech/docs/agents)
-   [Changelog](https://distribution.tech/docs/changelog)

Docs

-   Get started ›

    -   [Docs home](https://distribution.tech/docs)
    -   [Run a campaign with your agent](https://distribution.tech/docs/agents)
    -   [OpenAPI document](https://distribution.tech/openapi.json)
    -   [Changelog](https://distribution.tech/changelog)

-   Quickstart ›

    -   [Quickstart: your first API call](https://distribution.tech/docs/quickstart)


1.  [distribution](https://distribution.tech/)
2.  / [Docs](https://distribution.tech/docs)
3.  / [Getting started](https://distribution.tech/docs)
4.  / Quickstart: your first API call

Quickstart

# Quickstart: your first API call

Create an API key, read how well the network reaches your audience with one curl call, then start a campaign and quote its plan.

Last updated October 19, 2026

Copy page as markdown [View .md](https://distribution.tech/docs/quickstart.md)

## 1\. Create a key

Sign in to your workspace at [app.distribution.tech](https://app.distribution.tech) and open **Developers**. Create a key and pick its scopes: `inventory:read` for step 2, `campaigns:write` for step 3 and `campaigns:read` for step 4. Copy the key when it is shown; it is shown once.

A key that writes (`campaigns:write` or `plans:approve`) also needs a mandate: the most a plan may total, a monthly cap, the channels, whether it may sign, an expiry, and the brand terms a person accepted for it. See [Authentication](https://distribution.tech/docs/api/authentication) and [Scopes](https://distribution.tech/docs/api/scopes).

## 2\. Read your network coverage

```bash
curl https://app.distribution.tech/api/v1/inventory \
  -H "Authorization: Bearer $DISTRIBUTION_API_KEY"
```

The answer lists each channel on sale with how many approved creators reach your audience, how many are bookable now, and how strong coverage is. The full response is on [GET /inventory](https://distribution.tech/docs/api/get-inventory).

## 3\. Start a campaign

```bash
curl https://app.distribution.tech/api/v1/campaigns \
  -X POST \
  -H "Authorization: Bearer $DISTRIBUTION_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: first-launch-2026-10-19" \
  -d '{
    "goal": "launch",
    "product": "Your product in one line",
    "moment": "Version 2 goes live on November 12",
    "window_start": "2026-11-10",
    "window_end": "2026-11-20",
    "budget_usd": 2000
  }'
```

This needs `campaigns:write`. `goal` is one of `launch`, `funding`, `feature` or `program`, and `budget_usd` is the most to spend, held to your key's mandate. The answer carries `campaign_id` and `plan`, a priced plan whose `plan.plan_id` is the PLAN\_ID for step 4, or `plan` is null with a `plan_note` when nothing on sale fits yet. A retry with the same `Idempotency-Key` returns the first answer and never starts a second campaign. Every field is on [POST /campaigns](https://distribution.tech/docs/api/post-campaigns).

## 4\. Quote the plan

```bash
curl https://app.distribution.tech/api/v1/plans/PLAN_ID/quote \
  -H "Authorization: Bearer $DISTRIBUTION_API_KEY"
```

This needs `campaigns:read`. The quote is the plan as it would be signed: each creator, format, date and all-in price, the total, and whether your key's mandate allows signing it now. Approving it ([POST /plans/{id}/approve](https://distribution.tech/docs/api/post-plans-id-approve)) needs `plans:approve` and returns the payment link.

## Next

-   Run the whole flow from an agent over MCP: [Run a campaign with your agent](https://distribution.tech/docs/agents).
-   Every error and what to do about it: [Errors](https://distribution.tech/docs/api/errors).
-   What changed in each release: [API release notes](https://distribution.tech/docs/changelog/api).

A key comes from Developers once your brand is approved. [Connect an agent](https://distribution.tech/distribution#access) to ask for access, then follow [the agent guide](https://distribution.tech/docs/agents).

On this page

-   [1\. Create a key](#1-create-a-key)
-   [2\. Read your network coverage](#2-read-your-network-coverage)
-   [3\. Start a campaign](#3-start-a-campaign)
-   [4\. Quote the plan](#4-quote-the-plan)
-   [Next](#next)

[![distribution.tech](https://distribution.tech/brand/wordmark-light.svg)![distribution.tech](https://distribution.tech/brand/wordmark.svg)](https://distribution.tech/)

Your agent buys your distribution.

Distribution we run for

-   ClickUp
-   Gushwork
-   Tab

Platform

-   [How it works](https://distribution.tech/how-it-works)
-   [Network](https://distribution.tech/network)
-   [Workspace](https://app.distribution.tech/login)
-   [For your agents](https://distribution.tech/distribution)

Solutions

-   [Product launch](https://distribution.tech/solutions/product-launch)
-   [Funding announcement](https://distribution.tech/solutions/funding-announcement)
-   [Feature release](https://distribution.tech/solutions/feature-release)
-   [For brands](https://distribution.tech/for-brands)
-   [For creators](https://distribution.tech/for-creators)

Resources

-   [Blog](https://distribution.tech/blog)
-   [Launch playbook](https://distribution.tech/playbook)
-   [X creator rates](https://distribution.tech/rates/x-creators)

Company

-   [Customers](https://distribution.tech/customers)
-   [Pricing](https://distribution.tech/pricing)
-   [Changelog](https://distribution.tech/changelog)
-   [Build a distribution plan](https://app.distribution.tech/login)
-   [Join the creator network](https://distribution.tech/for-creators#apply)
-   [Log in](https://app.distribution.tech/login)

Legal

-   [Privacy](https://distribution.tech/privacy)
-   [Terms](https://distribution.tech/terms)

© 2026 distribution.tech [Contact: team@distribution.tech](mailto:team@distribution.tech)Cookie settings

Light Dark System