# Labor - Shifts API

**URL:** <https://developer.squareup.com/forums/t/labor-shifts-api/20243>\
**Category:** Questions\
**Tags:** labor-api\
**Created:** [December 23, 2024, 4:38pm UTC](https://developer.squareup.com/forums/t/labor-shifts-api/20243 "2024-12-23T16:38:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kunallxv](https://avatars.discourse-cdn.com/v4/letter/k/bc79bd/32.png) [@kunallxv](https://developer.squareup.com/forums/u/kunallxv)\
**Post date:** [December 23, 2024, 4:38pm UTC](https://developer.squareup.com/forums/t/labor-shifts-api/20243/1 "2024-12-23T16:38:46Z")

</div>

loses seconds value in getting clock in/out time. Hence time calculations can never be accurate. How can we get this fixed?

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [December 23, 2024, 4:39pm UTC](https://developer.squareup.com/forums/t/labor-shifts-api/20243/2 "2024-12-23T16:39:00Z")

</div>

👋 I’m Square Dev AI, here to help answer your question!  
Based on the information you’ve provided, the following documentation will help answer your question:

> **[Labor API: How It Works](https://developer.squareup.com/docs/labor-api/how-it-works)**
>
> Learn how the Square Labor API lets you build labor hours tracking in your application.

> **[Labor API](https://developer.squareup.com/docs/labor-api/what-it-does)**
>
> Learn about the capabilities of the Square Labor API.

> **Additional Documentation**
>
> [Inventory API: How It Works](https://developer.squareup.com/docs/inventory-api/how-it-works)  
> [Troubleshoot the Labor API](https://developer.squareup.com/docs/labor-api/troubleshooting)  
> [Build with the Labor API](https://developer.squareup.com/docs/labor-api/build-with-labor)

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.  
Otherwise one of our Developer Advocates will provide additional assistance shortly.

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [December 23, 2024, 5:38pm UTC](https://developer.squareup.com/forums/t/labor-shifts-api/20243/3 "2024-12-23T17:38:55Z")

</div>

The Square Labor API currently returns timestamps in ISO 8601 format, which includes date and time up to minutes, but does not include seconds. This is by design and currently there’s no way to get seconds precision for clock in/out times using the Labor API. If you need more precise time tracking, you may need to implement a custom solution within your application.

_This answer was reviewed by @Bryan-Square._