---
title: "Update a collection"
method: PUT
path: "/collections/{collection_id}"
tags: ["collections"]
---

# Update a collection

`PUT /collections/{collection_id}`

Updates the matching collection.

## Headers

- `Accept` 'application/json', required

## Request body

- object
  - `data` object, required
    - `attributes` object
      - `name` string — A new name.
      - `slug` string — A new URL-friendly slug. Use only letters, numbers, hyphens, and underscores. NOTE: We recommend **not** to invent your own slug. If it is not unique and valid, the request fails with a `422` error. Default is to automatically assign a slug based on `name` (a name of \"My Collection\" would make a slug of \"my-collection\").
      - `tagline` string — A new tag line.

## Response `200`

The updated collection.

- object
  - `data` object, required
    - `id` string — Unique identifier for the resource instance.
    - `type` 'collections' — The type of the resource.
    - `attributes` object
      - `name` string — A new name.
      - `slug` string — A new URL-friendly slug.
      - `tagline` string — A new tag line.
      - `public` boolean — Set to `true` for hassle-free sharing, allowing search engines to index your brand assets. Otherwise, set to `false` to share only with the users you specify.
      - `stealth` boolean — Set to `true` to remove the collection from appearing in web searches.
      - `is_workspace` boolean — Set to `true` if the collection is a Brandfolder workspace.

## Other responses

- `default` — Generic error payload

---

[API](https://skmtc.net/smartsheet/apis/brandfolder-openapi-reference.md) · [All operations](https://skmtc.net/smartsheet/apis/brandfolder-openapi-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/smartsheet/brandfolder-openapi-reference/revisions/fd95b0a2d2f8/schema)