> 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/field-service/task/schedule/proposal.md).

# Schedule proposals

Schedule proposals are "preview" of what tasks and routes will be created at the specified date range.

## API actions

API base path: `/task/schedule/proposal`.

### list

Get all tasks and routes that will be created by schedule.

#### Parameters

| name     | description                                                                                         | type                                                              |
| -------- | --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| trackers | Optional. IDs of the trackers to which task is assigned.                                            | int array                                                         |
| from     | Show tasks that will be created AFTER this date, e.g. "2014-07-01 00:00:00", should not before now. | [date/time](/docs/navixy-api/user-api/backend-api.md#data-types)  |
| to       | Show tasks will be created BEFORE this date, e.g. "2014-07-01 00:00:00", should not before `from`.  | [date/time](/docs/navixy-api/user-api/backend-api.md#data-types)  |
| filter   | Optional. Filter for task schedule label and description.                                           | string                                                            |
| types    | Optional. Tasks or routes. For example: `["task", "route"]`.                                        | [enum](/docs/navixy-api/user-api/backend-api.md#data-types) array |

* If `trackers`, `filter`, `from` or `to` is not passed or *null* then appropriate condition not used to filter results.

#### Example

cURL

{% code overflow="wrap" %}

```sh
curl -X POST 'https://api.eu.navixy.com/v2/task/schedule/proposal/list' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "from": "2020-11-24 00:00:00", "to": "2020-11-25 00:00:00"}'
```

{% endcode %}

#### Response

```json
{
    "success": true,
    "list": [{
         "id": 111,
         "user_id": 3,
         "tracker_id": 22,
         "location": {
             "lat": 51.283546,
             "lng": 7.301086,
             "address": "Fichtenstrasse 11",
             "radius": 150
         },
         "label": "Deliver parcels",
         "description": "Quickly",
         "creation_date": "2014-01-02 03:04:05",
         "from": "2014-02-03 04:05:06",
         "to": "2014-03-04 05:06:07",
         "external_id": null,
         "status": "assigned",
         "status_change_date": "2014-01-02 03:04:05",
         "max_delay" : 5,
         "min_stay_duration": 0,
         "arrival_date": "2014-01-02 03:04:05",
         "stay_duration": 0,
         "origin": "imported",
         "tags": [1, 2],
         "type": "task",
         "form": <form_object>
    }]
}
```

#### 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/field-service/task/schedule/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.