[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create a broadcast tournament

> Create a broadcast for an over-the-board event, to which rounds are added next. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/lichess/create_broadcast

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Create a broadcast for an over-the-board event, to which rounds are added next.

Lichess API: https://cotlet.dev/docs/api/lichess.md

`POST https://cotlet.dev/api/v1/lichess/broadcasts`

Access: write. Confirm: waits for the user's OK before it runs.

Creates the broadcast and returns its ID and URL. Visibility decides who can see it: Public, Unlisted (only from the link) or Private (only invited members). A public one is visible to everyone, so it reaches other people. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Tournament name. |
| `visibility` | string | no | public, unlisted or private. Default public. Public does not list it on the main Broadcasts page. |
| `description` | string | no | Long description in Markdown, shown in the broadcast overview. |
| `show_scores` | boolean | no | Show players' scores from the broadcast games. |
| `show_rating_diffs` | boolean | no | Show estimated rating changes from the broadcast games. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/lichess/broadcasts \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Riverside Chess Club Championship 2026","visibility":"private","description":"Six rounds, one game per round, Saturdays at 10:00.","show_scores":false,"show_rating_diffs":false}'
```

**Python**

```python
result = client.call("lichess", "create_broadcast", {"name":"Riverside Chess Club Championship 2026","visibility":"private","description":"Six rounds, one game per round, Saturdays at 10:00.","show_scores":False,"show_rating_diffs":False})
```

**Node.js**

```js
const result = await cotlet.call('lichess', 'create_broadcast', {"name":"Riverside Chess Club Championship 2026","visibility":"private","description":"Six rounds, one game per round, Saturdays at 10:00.","show_scores":false,"show_rating_diffs":false});
```

**CLI**

```bash
cotlet call lichess create_broadcast --data '{"name":"Riverside Chess Club Championship 2026","visibility":"private","description":"Six rounds, one game per round, Saturdays at 10:00.","show_scores":false,"show_rating_diffs":false}'
```

## Example response

```json
{
  "broadcast_id": "Zp4tNc6h",
  "name": "Riverside Chess Club Championship 2026",
  "visibility": "private",
  "url": "https://lichess.org/broadcast/riverside-chess-club-championship-2026/Zp4tNc6h",
  "rounds": []
}
```

Previous: [Import a PGN into a study](https://cotlet.dev/docs/api/lichess/import_pgn_to_study.md)
Next: [Create a broadcast round](https://cotlet.dev/docs/api/lichess/create_broadcast_round.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.