> For the complete documentation index, see [llms.txt](https://docs.fieldmotion.com/fieldmotion-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldmotion.com/fieldmotion-api-docs/userclockin/_setclockinnotes.md).

# \_setClockinNotes

Sets the Notes for a Clock-in time within a User Clock-in

### Parameters

#### id

The ID of the User Clock-in which includes the Clock-in time being modified

#### notes

A JSON array with 3 objects:

* "content" - A string with the new notes to be saved to the Clock-in time
* "noteTime" - The time and date when the new notes were saved, as an epoch time format with milliseconds (e.g 1688461858514, being 10:10am on 04-07-2023)
* "createdBy" - The ID of the User who modified the notes of the Clock-in

### Example

```
FM_api('UserClockin_setClockinNotes',[
  'id'=>'30020',
  'notes'=>'[
              {
              "content":"A few minutes late due to Traffic.",
              "noteTime":1688459159389,
              "createdby":92447
              }
            ]'
      ]
);
```

### Results

#### On Success

```
{"ok":1}
```

#### On Failure

If the "id" parameter is missing or has a value less than 1

```
{"error":"missing or invalid parameter: id"}
```

If the "id" parameter does not fit with any existing User Clock-in IDs

```
{"error":"clockin does not exist"}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fieldmotion.com/fieldmotion-api-docs/userclockin/_setclockinnotes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.