---
title: "Create a new collection"
url: https://docs.gleap.ai/en/reference/rest-api/create-helpcenter-collection
method: POST
path: "/helpcenter/collections"
api: "API Reference"
tag: "Help center collections"
operationId: "CreateHelpcenterCollection"
updatedAt: "2026-11-01T18:40:15.677Z"
language: en
---

# Create a new collection

`POST https://api.gleap.io/v3/helpcenter/collections`

Create a new help center collection. `project`, `docId` and `lexorank` are assigned by the server and ignored if sent. When `parent` is set, `baseAudienceFilter` is inherited from the parent collection (any value sent is overwritten) and an unknown `parent` returns 404.

## Authorization

- `Authorization` (header, required): `Bearer <token>`

## Headers

- `project` (string, required)

## Request body (`application/json`, required)

- `title` (any)
- `description` (any)
- `iconUrl` (string)
- `project` (string)
- `lexorank` (string)
- `docId` (number<double>)
- `parent` (string | null)
- `externalId` (string)
- `targetAudience` (string): Who can read the collection. New collections default to `all`; an update that leaves it out keeps the current audience.
- `baseAudienceFilter` (any)
- `extendedAudienceFilter` (any)
- `site` (string): Create only: the help center site of a new top-level collection (a site id, or `default`). A sub-collection always gets its parent's site; updates ignore it (PUT /helpcenter/sites/{id}/collections moves).

## Example request

```bash
curl --request POST \
  --url https://api.gleap.io/v3/helpcenter/collections \
  --header 'Authorization: Bearer <token>' \
  --header 'project: <project>' \
  --header 'Content-Type: application/json' \
  --data '{
  "iconUrl": "<iconUrl>",
  "project": "<project>",
  "lexorank": "<lexorank>",
  "docId": 0
}'
```

## Responses

### 200 (`application/json`)

Ok