# Fuel Sensor Quality Index

## Resource

Resource path: `/trackers/$tracker_id/sensors/$sensor_id/quality`.

### GET

Returns the fuel sensor quality index calculated from sensor readings within a specified datetime period.

#### Parameters

| name        | description                                                                      | type     |
| ----------- | -------------------------------------------------------------------------------- | -------- |
| tracker\_id | ID of the tracker which has the sensor.                                          | integer  |
| sensor\_id  | ID of the sensor to analyze.                                                     | integer  |
| interval    | Sensor readings' datetime interval which will be analyzed. Last week by default. | interval |

#### Examples

{% code overflow="wrap" %}

```shell
curl -X GET '{{ extra.eco_fleet_api_example_url }}/trackers/123/sensors/321/quality?interval=P7D/2020-12-31T00:00Z' \
    -H 'Authorization: NVX 22eac1c27af4be7b9d04da2ce1af111b'
```

{% endcode %}

#### Response

```json
{
  "smoothness": 8.29
}
```

* `smoothness` - a smoothness score of the sensor readings. Higher values indicate reduced noise in sensor readings, while lower values suggest increased noise.

**Types**

| Name  | Description                    | JSON type | Restrictions    |
| ----- | ------------------------------ | --------- | --------------- |
| Score | An abstract measurement score. | number    | >=1.0 && <=10.0 |

#### Errors

* `errors/entity/not-found` - Entity not found. Thrown if sensor or calibration table is missing.
* `errors/external-api/navixy` - Error accessing Navixy API. See `detail` field and consult [Backend API documentation](/docs/navixy-api/user-api/backend-api/errors.md).
* `errors/sensors/quality/not-enough-readings` - Not enough sensor readings in given interval. Try using interval with enough vehicle usage or changing readings' sending frequency and waiting for data accumulation.


---

# Agent Instructions: 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://navixy.com/docs/navixy-api/user-api/eco-fleet-api/resources/trackers/sensors/quality.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.