> ## Documentation Index
> Fetch the complete documentation index at: https://developers.conveyour.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete a folder

> Deletes a bookmark folder.

Delete a bookmark folder

**Groups are called `bookmarks` in the API.** The UI calls these Groups, but the model and every route use `bookmarks`. The name describes what the record actually is: a saved contact filter query — `filters` is a required field, and the saved query is what defines the segment, whether dynamic or static. "Bookmark" was the original word for saving that query; the UI later settled on "Group" for the same thing. Endpoint paths stay `/api/bookmarks` — only the naming in these docs follows the UI.

**A missing record does not return 404.** This handler reports the failure without a status code, and the error envelope defaults to HTTP `200` — you get `200` with `status: "failed"`. Branch on `status`, not on the HTTP code.



## OpenAPI

````yaml /api-reference/specs/bookmarks-groups.json delete /api/bookmarks/folders/{id}
openapi: 3.1.0
info:
  title: ConveYour API — Groups (Bookmarks)
  description: Create and manage contact groups (bookmarks) and bookmark folders.
  version: 1.0.0
servers:
  - url: https://{subdomain}.conveyour.com
    description: Your organization's ConveYour instance
    variables:
      subdomain:
        default: acme
        description: >-
          Your organization's slug — the subdomain you sign in on. Replace
          `acme` with yours: if you sign in at `bigco.conveyour.com`, enter
          `bigco`.
security:
  - conveyourToken: []
tags:
  - name: Groups (Bookmarks)
    description: Create and manage contact groups (bookmarks) and bookmark folders.
paths:
  /api/bookmarks/folders/{id}:
    delete:
      tags:
        - Groups (Bookmarks)
      summary: Delete a folder
      description: >-
        Deletes a bookmark folder.


        Delete a bookmark folder


        **Groups are called `bookmarks` in the API.** The UI calls these Groups,
        but the model and every route use `bookmarks`. The name describes what
        the record actually is: a saved contact filter query — `filters` is a
        required field, and the saved query is what defines the segment, whether
        dynamic or static. "Bookmark" was the original word for saving that
        query; the UI later settled on "Group" for the same thing. Endpoint
        paths stay `/api/bookmarks` — only the naming in these docs follows the
        UI.


        **A missing record does not return 404.** This handler reports the
        failure without a status code, and the error envelope defaults to HTTP
        `200` — you get `200` with `status: "failed"`. Branch on `status`, not
        on the HTTP code.
      operationId: deleteABookmarkFolder
      parameters:
        - name: id
          in: path
          required: true
          description: The id identifier.
          schema:
            type: string
        - $ref: '#/components/parameters/teams'
      responses:
        '200':
          description: Success.
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/Envelope'
                  - type: object
                    properties:
                      data:
                        $ref: '#/components/schemas/NoData'
              example:
                status: ok
                message: success
                data: []
        '403':
          $ref: '#/components/responses/ForbiddenToken'
components:
  parameters:
    teams:
      name: teams[]
      in: query
      description: >-
        Team scope for the request, as one or more team ObjectIds. The brackets
        are required: PHP keeps only the last value for a repeated plain key, so
        `teams=A&teams=B` silently resolves to B alone. On requests with a JSON
        body you may send `teams` (no brackets) in the body instead.


        **Values that are not valid ObjectIds are silently ignored** — a
        mistyped team ID behaves as if no team was sent. See the [teams section
        of the API conventions guide](/guides/api-conventions#team-scoping).
      style: form
      explode: true
      schema:
        type: array
        items:
          type: string
      example:
        - 64a1b2c3d4e5f6a7b8c9d0ff
  schemas:
    Envelope:
      type: object
      description: The common response envelope shared by all ConveYour endpoints.
      properties:
        status:
          type: string
          enum:
            - ok
            - failed
          description: '`ok` on success, `failed` on error.'
        message:
          type: string
          description: Human-readable description of the result.
        data:
          description: >-
            The response payload — an object or an array depending on the
            endpoint.
    NoData:
      type: array
      items: {}
      maxItems: 0
      description: No payload — `data` is an empty array.
  responses:
    ForbiddenToken:
      description: >-
        The token is missing, expired, or not permitted for this HTTP method.
        **This endpoint enforces no named permission**, so a 403 here never
        carries a `permission` field.
      content:
        application/json:
          example:
            status: failed
            message: Token is either expired or does not have the correct permissions
            data: []
  securitySchemes:
    conveyourToken:
      type: apiKey
      in: header
      name: x-conveyour-token
      description: >-
        Your API key token. Contacts endpoints require a **Server-only — Full
        API** key — see [Authentication](/quickstart).

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.