> ## Documentation Index > Fetch the complete documentation index at: https://moengage.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Delete Items > This API deletes existing items in a given catalog. #### Rate Limit * Request limit: You can delete 100 items per minute OR 1000 items per hour. You can delete up to 50 items per request. * Payload size limit: 5 MB only when Content-Length header is provided. ## OpenAPI ````yaml /api/catalog/catalog.yaml post /catalog/{catalog_id}/items/bulk-delete openapi: 3.0.3 info: title: MoEngage Catalog API description: > This API allows for the management of product and item catalogs, including **creation**, **attribute definition**, **item ingestion, updates, deletion**, and **retrieval**. Authentication is handled via **Basic Auth** (using your Workspace ID as username and API Key as password), and all requests additionally require the `MOE-APPKEY` header (Workspace ID). The API has a platform-wide rate limit of **100 requests/minute OR 1000 requests/hour**, with a maximum payload size of **5MB**. x-mint: content: | #example 500 max # version: '1.0' servers: - url: https://api-{dc}.moengage.com/v1 variables: dc: default: '01' description: >- The ‘dc’ in the API Endpoint URL refers to the MoEngage Data Center (DC). MoEngage hosts each customer in a different DC. You can find your DC number and replace the value of ‘dc’ in the URL by referring to the DC and API endpoint mapping [here](/api/introduction#data-centers). Your MoEngage Data Center (DC) can be 01, 02, 03, 04, 05, 06, or 101. security: - basicAuth: [] tags: - name: Catalog description: Operations related to creating and managing catalog schemas (attributes). - name: Items description: >- Operations related to ingesting, updating, and deleting items within a catalog. paths: /catalog/{catalog_id}/items/bulk-delete: post: tags: - Items summary: Delete Items description: | This API deletes existing items in a given catalog. operationId: deleteCatalogItems parameters: - name: MOE-APPKEY in: header description: >- This is the Workspace ID of your MoEngage account that must be passed with the request. You can find it in the MoEngage dashboard at **Settings** > **Account** > **APIs** > **Workspace ID (earlier app id)**. required: true schema: type: string - $ref: '#/components/parameters/CatalogIdPath' requestBody: required: true content: application/json: schema: type: object required: - items properties: items: type: array maxItems: 50 description: An array of item IDs to delete from the catalog. items: type: string example: item_id_123 example: items: - '{{item_ID}}' responses: '202': description: Accepted. The bulk delete request was processed successfully. content: application/json: schema: type: object properties: message: type: object properties: valid: type: object properties: count: type: integer description: The number of items successfully deleted. invalid: type: object properties: count: type: integer description: >- The number of items that were not found and could not be deleted. example: message: valid: count: 0 invalid: count: 10 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '413': $ref: '#/components/responses/PayloadTooLarge' '429': $ref: '#/components/responses/TooManyRequests' components: parameters: CatalogIdPath: name: catalog_id in: path required: true description: The unique identifier for the catalog, obtained during catalog creation. schema: type: string responses: BadRequest: description: >- Bad Request - The request is improperly formatted, or contains missing/invalid parameters. content: application/json: schema: $ref: '#/components/schemas/Error' examples: invalid-datatype: value: error-code: invalid-request message: The data type provided for some of the attributes is invalid. invalid-json: value: error-code: invalid-request message: >- The request body is not a valid JSON. Please provide a valid JSON request body. limit-exceeded: value: error-code: invalid-request message: >- items size should be greater than 0 and less than or equal to 50 Unauthorized: description: >- Unauthorized - The request does not have valid authentication credentials. content: application/json: schema: $ref: '#/components/schemas/Error' example: error-code: request-unauthenticated message: >- Your request is unauthorized. Please verify your credentials and try again. Forbidden: description: Forbidden - The client does not have access rights to the Catalog APIs. content: application/json: schema: $ref: '#/components/schemas/Error' example: error-code: request-denied message: Your account does not have access to the Catalog APIs. NotFound: description: Not Found - The specified resource (catalog) could not be found. content: application/json: schema: $ref: '#/components/schemas/Error' example: error-code: catalog-not-found message: >- We could not find any API based catalog for the provided catalog id. PayloadTooLarge: description: Payload Too Large - The request payload exceeds the 5MB limit. content: application/json: schema: $ref: '#/components/schemas/Error' example: error-code: payload-size-exceeded message: >- Your payload size exceeds the 5MB limit. Please reduce the payload size and try again. TooManyRequests: description: > Too Many Requests - The rate limit for the API has been exceeded. The following headers are returned in case of rate-limit breach: * **x-ratelimit-limit (integer)**: The maximum number of requests that the consumer is permitted to make in a given time window. * **x-ratelimit-remaining (integer)**: The number of requests remaining in the current rate limit window. * **x-ratelimit-reset (integer)**: The time at which the current rate limit window resets in UTC epoch seconds. schemas: Error: type: object properties: error-code: type: string description: A machine-readable error code. message: type: string description: A human-readable description of the error. securitySchemes: basicAuth: type: http scheme: basic description: > Authentication is done via Basic Auth. This requires a base64-encoded string of your credentials in the format 'username:password'. - **Username**: Use your MoEngage workspace ID (also known as the App ID). You can find it in the MoEngage dashboard at **Settings** > **Account** > **APIs** > **Workspace ID (earlier app id)**. - **Password**: Use your API Key, which you can find within the **Campaign report/Business events/Custom templates/Catalog API/Inform Report** tile. For more information on authentication and getting your credentials, refer [here](https://www.moengage.com/docs/api/introduction#getting-your-credentials). ````