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

# Driver journal

Trips categorised as business or private, so transport use can be split between them.

A driver journal is the record of who drove what and why. Each entry is a trip with a category attached, which is what separates a reimbursable journey from a personal one.

Entries are not created from nothing. [Trip proposals](/docs/navixy-api/user-api/resources/fleet/driver_journal/proposal.md) lists the raw trips the Navixy platform detected over a period, and [Driver journal entry](/docs/navixy-api/user-api/resources/fleet/driver_journal/entry.md) turns a chosen one into a categorised record.

## Operations in this section

#### Driver journal entry

| Endpoint                                                                                                                                 | Method | What it does                  |
| ---------------------------------------------------------------------------------------------------------------------------------------- | ------ | ----------------------------- |
| [`/driver/journal/entry/list`](/docs/navixy-api/user-api/resources/fleet/driver_journal/entry.md#post-driver-journal-entry-list)         | POST   | List driver journal entries   |
| [`/driver/journal/entry/create`](/docs/navixy-api/user-api/resources/fleet/driver_journal/entry.md#post-driver-journal-entry-create)     | POST   | Create driver journal entries |
| [`/driver/journal/entry/update`](/docs/navixy-api/user-api/resources/fleet/driver_journal/entry.md#post-driver-journal-entry-update)     | POST   | Update driver journal entry   |
| [`/driver/journal/entry/delete`](/docs/navixy-api/user-api/resources/fleet/driver_journal/entry.md#post-driver-journal-entry-delete)     | POST   | Delete driver journal entries |
| [`/driver/journal/entry/download`](/docs/navixy-api/user-api/resources/fleet/driver_journal/entry.md#post-driver-journal-entry-download) | POST   | Download driver journal       |

#### Trip proposals

| Endpoint                                                                                                                                  | Method | What it does        |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ------ | ------------------- |
| [`/driver/journal/proposal/list`](/docs/navixy-api/user-api/resources/fleet/driver_journal/proposal.md#post-driver-journal-proposal-list) | POST   | List trip proposals |


---

# 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, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/navixy-api/user-api/resources/fleet/driver_journal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.