> ## Documentation Index > Fetch the complete documentation index at: https://developers.redo.com/llms.txt > Use this file to discover all available pages before exploring further. # Delete a bundle > Remove one bundle, identified by the SKU of its parent product. The SKU is looked up in your catalog, so a bundle created in the Redo UI is found too. If your store reuses SKUs across variants, always send `variant_id` so Redo knows which variant's bundle to remove. Use `GET /stores/{storeId}/bundles?parent_sku=` to see which variant each bundle belongs to. `404` means either no product has the SKU or the product has no bundle; `detail` says which. Requires the [`returns_write`](/docs/api-reference/scopes) scope. ## OpenAPI ````yaml /api-schema/openapi.yaml delete /stores/{storeId}/bundles/{parentSku} openapi: 3.1.0 info: contact: email: engineering-admin@getredo.com name: Redo Engineering description: | ## Endpoints Endpoints are authenticated using the Bearer authorization scheme, using the REDO_API_SECRET. ```txt GET /v2.2/resource HTTP/1.1 Authorization: Bearer 77bb7598b7a972475cc7c7e171ec33af Host: api.getredo.com ``` ## Webhooks Webhooks are authenticated using the Bearer authorization scheme, using a secret supplied by the subscriber. ```txt POST /events HTTP/1.1 Authorization: Bearer subscriberauth123 Host: subscriber.example.com ``` Webhook events are delivered in order for each individual subject (e.g. return). If the response is not a 2xx status code, the event will be retried multiple times before discarding it. title: Redo API version: 2.2.1 servers: - url: https://api.getredo.com/v2.2 security: [] tags: - description: >- Group several products under one product shoppers buy, so a returned bundle can be broken back into the products it contains. name: Bundles - name: Checkout Buttons - name: Coverage Info - name: Coverage Products - name: Custom Events - name: Customer Portal - name: Customer Subscriptions - name: Customers - name: Inbound Shipments - name: Inventory Items - name: Inventory Levels - name: Invoices - name: Merchant Admin - name: Orders - name: Products - name: Returns - description: >- Push orders into Redo from a commerce platform Redo does not support directly, so shoppers can return them. name: Returns Custom Integration - name: Storefront - name: Webhooks paths: /stores/{storeId}/bundles/{parentSku}: summary: Bundle parameters: - $ref: '#/components/parameters/store-id.param' - $ref: '#/components/parameters/bundle-parent-sku-path.param' delete: tags: - Bundles summary: Delete a bundle description: > Remove one bundle, identified by the SKU of its parent product. The SKU is looked up in your catalog, so a bundle created in the Redo UI is found too. If your store reuses SKUs across variants, always send `variant_id` so Redo knows which variant's bundle to remove. Use `GET /stores/{storeId}/bundles?parent_sku=` to see which variant each bundle belongs to. `404` means either no product has the SKU or the product has no bundle; `detail` says which. Requires the [`returns_write`](/docs/api-reference/scopes) scope. operationId: Bundle delete parameters: - $ref: '#/components/parameters/bundle-variant-id.param' responses: '200': content: application/json: schema: $ref: '#/components/schemas/bundle-delete-response.schema' example: parent_sku: BUNDLE-STARTER-KIT variant_id: '55518673568035' description: The bundle was removed '400': content: application/problem+json: schema: $ref: '#/components/schemas/bundle-ambiguous-sku-error.schema' description: >- The path SKU is empty, or `variant_id` is not one of the variants carrying the SKU (the response lists the valid `variant_ids`) '404': content: application/problem+json: schema: $ref: '#/components/schemas/error.schema' description: >- No product has this SKU, or the product has no bundle (`com.getredo.api:bundles/not-found`) '409': content: application/problem+json: schema: $ref: '#/components/schemas/bundle-ambiguous-sku-error.schema' example: type: com.getredo.api:bundles/ambiguous-sku title: Parent SKU matches more than one variant detail: >- SKU BUNDLE-STARTER-KIT is on 2 variants. Pass ?variant_id= to choose one. variant_ids: - '55518673568035' - '55518673600803' description: >- The SKU is on more than one variant and no `variant_id` was given; the response lists the `variant_ids` to choose from default: content: application/problem+json: schema: $ref: '#/components/schemas/error.schema' description: Error security: - Bearer: [] components: parameters: store-id.param: description: Store ID in: path name: storeId required: true schema: example: 64e5a8a1af49a89df37e4ee7 type: string bundle-parent-sku-path.param: description: >- SKU of the product that represents the bundle. Case-sensitive and URL-encoded. example: BUNDLE-STARTER-KIT in: path name: parentSku required: true schema: type: string bundle-variant-id.param: description: >- The parent variant. Send it if the SKU may be on more than one variant in your catalog. example: '55518673568035' in: query name: variant_id schema: type: string schemas: bundle-delete-response.schema: description: The bundle that was removed. properties: parent_sku: description: Parent SKU the request named. example: BUNDLE-STARTER-KIT title: Parent SKU type: string variant_id: description: The parent variant whose bundle was removed. example: '55518673568035' title: Variant ID type: string required: - parent_sku - variant_id title: Bundle Delete Response type: object bundle-ambiguous-sku-error.schema: allOf: - $ref: '#/components/schemas/error.schema' description: Problem details plus the variants that carry the SKU. properties: variant_ids: description: Variants that carry the SKU. items: type: string title: Variant IDs type: array required: - variant_ids title: Ambiguous SKU problem details type: object error.schema: description: >- Problem details. See [RFC 7807 Section 3](https://datatracker.ietf.org/doc/html/rfc7807#section-3). properties: detail: description: Human-readable description of the problem. title: Detail type: string instance: description: A URI reference that identifies this problem. format: uri-reference type: string title: description: Human-readable summary of the problem type. title: Title type: string type: default: about:blank description: A URI reference that identifies the problem type. format: uri-reference type: string title: Problem details type: object securitySchemes: Bearer: scheme: bearer type: http ````