[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 collection

> Create a collection or a sub-collection. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/bluedot/create_collection

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 collection or a sub-collection.

Bluedot API: https://cotlet.dev/docs/api/bluedot.md

`POST https://cotlet.dev/api/v1/bluedot/collections`

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

Does what the + next to Collections does. The default access decides who in the workspace sees the collection, so it reaches other people. There is no tool to delete a collection, because Bluedot deletes every recording inside it. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Collection title. |
| `workspace_id` | string | no | Workspace ID from list_workspaces. Leave out to use your current workspace. |
| `parent_collection_id` | string | no | Create it inside this collection. A sub-collection takes the access of its parent. |
| `everyone_access` | string | no | Default access for Everyone at Bluedot: full_access, can_upload, can_view or no_access. Leave out to keep Bluedot's default. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/bluedot/collections \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workspace_id":"w_90c1d7","title":"Acme","everyone_access":"can_view"}'
```

**Python**

```python
result = client.call("bluedot", "create_collection", {"workspace_id":"w_90c1d7","title":"Acme","everyone_access":"can_view"})
```

**Node.js**

```js
const result = await cotlet.call('bluedot', 'create_collection', {"workspace_id":"w_90c1d7","title":"Acme","everyone_access":"can_view"});
```

**CLI**

```bash
cotlet call bluedot create_collection --data '{"workspace_id":"w_90c1d7","title":"Acme","everyone_access":"can_view"}'
```

## Example response

```json
{
  "collection_id": "c_a02e51f9",
  "title": "Acme",
  "parent_collection_id": null,
  "everyone_access": "can_view"
}
```

Previous: [Move meeting to collection](https://cotlet.dev/docs/api/bluedot/move_meeting_to_collection.md)
Next: [Create notes template](https://cotlet.dev/docs/api/bluedot/create_template.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.