# Ability to know timestamp when Line Item was added to the Order

**URL:** <https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657>\
**Category:** Feature Requests\
**Tags:** orders-api\
**Created:** [September 12, 2023, 8:32am UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657 "2023-09-12T08:32:00Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kirill.g](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kirill.g](https://developer.squareup.com/forums/u/kirill.g)\
**Post date:** [September 12, 2023, 8:32am UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/1 "2023-09-12T08:32:00Z")

</div>

We’re at Glimpse are active consumers of SearchOrders endpoint in Orders API. At the moment we’re using CreatedAt property of an Order, but it’s not accurate for large Orders.

It would help us a lot if we can get that information via API.

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [September 12, 2023, 5:12pm UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/2 "2023-09-12T17:12:42Z")

</div>

When you say its not alway accurate for large orders what do you mean by that? Do you have any examples? 🙂

---

<div class="post-metadata">

**Author:** ![kirill.g](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kirill.g](https://developer.squareup.com/forums/u/kirill.g)\
**Post date:** [September 13, 2023, 10:39am UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/3 "2023-09-13T10:39:35Z")

</div>

So we’re joining items from tickets to events from the video feed. For instance group of people entered restaurant at 18:15, ordered beer at 18:20, then drinks at 19:00, then pizza at 19:30 and then closed the order at 20:00. Using API we have only two dates: 18:15 and 20:00. But actual actions that we’re interested in happen at 18:20, 19:00 & 19:30.  
In this case we won’t be able to accurately join events from video to POS data.

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [September 13, 2023, 4:24pm UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/4 "2023-09-13T16:24:14Z")

</div>

If these are orders that are taken with the POS then you’ll only be able to get the two `created_at` and `updated_at` timestamps when the order is paid for at this time. If the order is created and updated with the API you can subscribe to [order.updated webhooks](https://developer.squareup.com/reference/square/orders-api/webhooks) to be notified of any change to the order. 🙂

---

<div class="post-metadata">

**Author:** ![kirill.g](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kirill.g](https://developer.squareup.com/forums/u/kirill.g)\
**Post date:** [September 14, 2023, 11:04am UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/5 "2023-09-14T11:04:22Z")

</div>

Thanks Brian!  
We’ve used webhooks since integrated and previously they haven’t been regular (I mean only `order.updated`) to my observations.  
Right now body of an event does not allow me to map it to corresponding line item:

```auto
        "order_updated": {
            "created_at": "2023-09-11T23:26:26.405Z",
            "location_id": "XXX",
            "order_id": "YYY",
            "state": "DRAFT",
            "updated_at": "2023-09-11T23:34:10.601Z",
            "version": 18
        }

```

Of course I can implement basic heuristics to map all stored web hook events to each line of an order. Or query your API each time we receive web hook. But it will increase load to your API 1000x times as right now we’re doing it on a daily basis.  
I find it overcomplicated for both sides, that’s why I’m asking for this feature 🙂

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [September 14, 2023, 5:19pm UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/6 "2023-09-14T17:19:42Z")

</div>

We’re constantly working to improve our features based on feedback like this, so I’ll be sure to share your request to the API product team. 🙂

---

<div class="post-metadata">

**Author:** ![kirill.g](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kirill.g](https://developer.squareup.com/forums/u/kirill.g)\
**Post date:** [August 30, 2024, 3:44pm UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/7 "2024-08-30T15:44:21Z")

</div>

Hey there, any update on this? I’ve checked events and recent API reference, still missing this. One of our customers using Square forced to move to another POS provider as they desperately needed this feature ☹

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [August 30, 2024, 3:59pm UTC](https://developer.squareup.com/forums/t/ability-to-know-timestamp-when-line-item-was-added-to-the-order/10657/8 "2024-08-30T15:59:32Z")

</div>

At this time the ability to get the order by version which would give you all the times the order was updated is currently unavailable. 🙂
