# Deprecation of invoiceitem.updated event

To improve product clarity and reduce redundant notifications, we are planning to remove the invoiceitem.updated [event](https://stripe.com/docs/api/events) by November 15, 2023, or earlier depending on the specifics of your integration. The [Update Invoice Item API](https://stripe.com/docs/api/invoiceitems/update) will remain unchanged and available.
If you previously have had an integration reliant on invoiceitem.updated, you should receive an email notifying you of the deprecation and will need to update your integration before the date referenced to avoid any disruptions.
Typically, we send invoiceitem.updated events when one of the following things occur:
* A user manually updates an invoice item using the [Update Invoice Item API](https://stripe.com/docs/api/invoiceitems/update), in which case we suggest relying on the API response.
* An invoice item is attached to an invoice. In this scenario, you can listen for invoice.created, invoice.finalized, and invoice.updated, which are already sent at the same time. Each event includes a lines field that lists the line items on the invoice, with a limit of 10 total. You can then use the [Retrieve Invoice Line Items API](https://stripe.com/docs/api/invoices/invoice_lines) to directly retrieve all invoice line items if you need them. This should have all of the information you need, but if you rely on a field that is not present, you can then get the [invoice item ID from the line item object](https://stripe.com/docs/api/invoices/line_item#invoice_line_item_object-invoice_item) and use it to directly [retrieve the full invoice item](https://stripe.com/docs/api/invoiceitems/retrieve).
**To avoid disruptions to integrations you own, you will need to update any webhooks and integration code that are reliant on** **`invoiceitem.updated`\*\*\*\*, to rely on one of the above alternative flows.**