> ## Documentation Index > Fetch the complete documentation index at: https://developer.fabric.inc/llms.txt > Use this file to discover all available pages before exploring further. # Delete Collection > If there is a change in product offerings, one or more collections may become unnecessary. This endpoint is used to delete a collection by ID. ## OpenAPI ````yaml category.openapi delete /collections/{id} openapi: 3.0.0 info: title: Products - Categories API description: >- Categories (also called hierarchies or nodes) form a hierarchical tree structure to organize items and services into intuitive groups. Organizing items this way simplifies item discovery on your e-commerce platform (website or app). **Categories** is the original tree of Product List with nested levels of categories. Each item is placed where it belongs within a category. For example, `Computers` is a parent category with `Laptops` and `Desktops` as children categories, and `MacBook Pro` is an item within `Laptops`. This organization can be represented as Computers -> Laptops -> MacBook Pro. **Collections** serve as alternative organizations of Category system, which is the original, single source for all items and categories. Their main purpose is distribution management by displaying items on your e-commerce platform based on browsing structures you need to achieve various merchandising objectives, such as organizational requirements, multi-regional assortments, multi-channel assortments, and collections. For example, a company that sells, repairs, and supports computers and related items and services will have a Category system with a complete list of SKUs. Because Category system isn't granular enough to be used on Storefront, multiple Collections are created to target specific shopper segment experiences. For laptop consumers, you might have one collection that lists all the laptops and PCs. For large businesses, you will have another collection that lists all commercial laptops, PCs, printers, and servers. Both of the collections will act as filters of the Category, tailored to the purpose of a merchandising strategy. version: 3.0.0 x-audience: external-public contact: email: support@fabric.inc name: Product team license: name: fabric API License url: https://fabric.inc/api-license termsOfService: https://fabric.inc/terms-of-use servers: - url: https://api.fabric.inc/v3 description: Production URL security: - authorization: [] tags: - name: Categories description: >- Categories are organized into a hierarchical tree structure based on common attributes, allowing logical grouping of items. The Categories endpoints enables CRUD operations, such as creating, locating, and managing categories. - name: Collections description: >- As the **Categories** system may not be sufficiently granular to accommodate all Storefront use cases, **Collections** provide an alternative means of organizing products on the Storefront. Collections create a representational categorization of products, and are primarily used by merchants for short-term marketing campaigns. For instance, a collection could be created for a New Year sale that highlights discounted furniture products. - name: Navigation Paths description: >- Paths indicate the navigation of the current category or collection to its root category or collection. These navigation paths are helpful in determining the exact position of a category or collection within the hierarchical tree structure. - name: Bulk action for categories and collections description: These endpoints support creating and updating categories and collections. externalDocs: description: Find out more about Products (previously called PIM) url: https://developer.fabric.inc/docs/products-overview paths: /collections/{id}: delete: tags: - Collections summary: Delete Collection description: >- If there is a change in product offerings, one or more collections may become unnecessary. This endpoint is used to delete a collection by ID. operationId: deleteCollection parameters: - $ref: '#/components/parameters/x-fabric-tenant-id' - $ref: '#/components/parameters/x-fabric-request-id' - $ref: '#/components/parameters/collectionId' responses: '200': headers: x-fabric-request-id: $ref: '#/components/headers/x-fabric-request-id-header' description: OK '400': $ref: '#/components/responses/badRequest' '401': $ref: '#/components/responses/notAuthorized' '403': $ref: '#/components/responses/forbidden' '404': $ref: '#/components/responses/notFoundError' '500': $ref: '#/components/responses/internalServerError' components: parameters: x-fabric-tenant-id: name: x-fabric-tenant-id in: header description: >- A header used by fabric to identify the tenant making the request. You must include tenant id in the authentication header for an API request to access any of fabric’s endpoints. You can retrieve the tenant id , which is also called account id, from [Copilot](/v3/platform/settings/account-details/getting-the-account-id). This header is required. schema: type: string example: 517fa9dfd42d8b00g1o3k312 x-fabric-request-id: name: x-fabric-request-id in: header description: Unique request ID schema: type: string example: 263e731c-45c8-11ed-b878-0242ac120002 required: false collectionId: in: path name: id description: System-generated 24-character collection ID schema: type: string required: true example: 54328bf0b5f328bf0b5f3280 headers: x-fabric-request-id-header: description: Unique request ID schema: type: string example: 263e731c-45c8-11ed-b878-0242ac120002 responses: badRequest: description: Request is invalid or malformed headers: x-fabric-request-id: $ref: '#/components/headers/x-fabric-request-id-header' content: application/json: schema: $ref: '#/components/schemas/genericError' notAuthorized: description: Unauthorized requester headers: x-fabric-request-id: $ref: '#/components/headers/x-fabric-request-id-header' content: application/json: schema: $ref: '#/components/schemas/genericError' example: message: The requester is unauthorized type: UNAUTHORIZED_ERROR forbidden: description: User isn't allowed to perform the action headers: x-fabric-request-id: $ref: '#/components/headers/x-fabric-request-id-header' content: application/json: schema: $ref: '#/components/schemas/genericError' example: type: REQUEST_DENIED message: User doesn't have the required permission notFoundError: description: The entity requested for isn't found headers: x-fabric-request-id: $ref: '#/components/headers/x-fabric-request-id-header' content: application/json: schema: $ref: '#/components/schemas/genericError' example: type: NOT_FOUND message: Resource not found internalServerError: description: Internal server error headers: x-fabric-request-id: $ref: '#/components/headers/x-fabric-request-id-header' content: application/json: schema: $ref: '#/components/schemas/genericError' example: type: SERVER_ERROR message: Internal Server Error schemas: genericError: type: object description: Error details properties: message: type: string description: Error message example: Request was invalid type: type: string description: Error type example: Bad request errors: type: array items: type: object properties: type: type: string description: Error type example: CLIENT_ERROR message: type: string description: Brief error message example: Invalid request securitySchemes: authorization: type: http scheme: bearer bearerFormat: JWT description: S2S access token (JWT) from fabric Identity service (during Login) ````