1. Home
  2. Docs
  3. Labor Integration
  4. Update Time Punch Data
  5. Employee Taking another Break

Employee Taking another Break

When employees take multiple breaks, each break needs to be represented by a separate break object in the breaks object array.

For every PUT request made to the endpoint for updating break info, all previous breaks associated with the time punch being updated will need to be specified as well. Not specifying previous breaks causes them to be overwritten and deleted.

Here’s an example request body showing that the employee has gone on a second break, following the break from the previous requests:

Request body

{
	"time_punch": {
		"date": "2020-07-31",
		"clocked_in": "08:00:00",
		"breaks": [
			{
				"in": "12:00:00",
				"out": "12:30:00",
				"paid": false
			},
			{
				"in": "14:00:00",
				"paid": true
			}
                ]
	}
}

As you can see, the first break has been specified, along with the second break. Also, different breaks can have different paid boolean values, based on your paid/unpaid breaks setting logic.

Similarly, when the employee returns from this second break, the request should look as follows:

Request body

{
	"time_punch": {
		"date": "2020-07-31",
		"clocked_in": "08:00:00",
		"breaks": [
			{
				"in": "12:00:00",
				"out": "12:30:00",
				"paid": false
			},
			{
				"in": "14:00:00",
				"out": "14:15:00",
				"paid": true
			}
                ]
	}
}