> 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/backend-api/resources/fleet/driver_journal/proposal.md).

# Trip proposal for driver journal

Proposal objects - trips per specified period that could be used for driver journal entry creation.

To get information on how-to work with driver journals refer to our [instructions](/docs/navixy-api/user-api/backend-api/guides/fleet-management/driver-journals.md).

## API actions

API path: `/driver/journal/proposal`.

### list

Gets proposal trips that could be used for driver journal entry creation.\
Proposal objects created by a track's division by driver changes.\
If there was no driver change on the track, then the track will be returned entirely.\
Tracks selected by intersecting their date range with date range from request (`from` and `to` parameters).

#### Parameters

| name        | description                                  | type   |
| ----------- | -------------------------------------------- | ------ |
| from        | Include tracks which end after this date.    | string |
| to          | Include tracks which start before this date. | string |
| tracker\_id | ID of the tracker.                           | int    |

#### Example

cURL

{% code overflow="wrap" %}

```sh
curl -X POST 'https://api.eu.navixy.com/v2/driver/journal/proposal/list' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "a6aa75587e5c59c32d347da438505fc3", "tracker_id": 123456, "from": "2020-10-13 00:00:00", "to": "2020-10-14 00:00:00"}'
```

{% endcode %}

#### Response

```json
{
  "success": true,
  "list": [
    {
      "tracker_id": 1,
      "employee_id": 1,
      "start_date": "2020-10-14 07:03:39",
      "end_date": "2020-10-15 08:05:02",
      "start_location": {
        "lat": 11.111111,
        "lng": 22.222222,
        "address": "Address string"
      },
      "end_location": {
        "lat": 33.333333,
        "lng": 44.444444,
        "address": "Address string"
      },
      "length": 2.1,
      "start_odometer": 50.2,
      "end_odometer": 52.0,
      "overlapped": false
    }
  ]
}
```

* `tracker_id` - int. An ID of the tracker (aka "object\_id"). Tracker must belong to authorized user and not be blocked.
* `employee_id` - nullable int. An ID of employee (driver).
* `start_date` - [date/time](/docs/navixy-api/user-api/backend-api.md#data-types). Start date of a journal entry.
* `end_date` - [date/time](/docs/navixy-api/user-api/backend-api.md#data-types). End date of a journal entry.
* `start_location` - location object. Where entry starts.
* `end_location` - location object. Where entry ends.
* `length` - float. Length of the trip km.
* `start_odometer` - nullable float. Odometer's value at the start.
* `end_odometer` - nullable float. Odometer's value at the end.
* `overlapped` - boolean. `true` if there is already driver journal entry with date range which is intersecting this proposal object's date range.

#### Errors

* [General](/docs/navixy-api/user-api/backend-api/errors.md#error-codes) types only.


---

# 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/backend-api/resources/fleet/driver_journal/proposal.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.