> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/for-developers/user-data-types/boolean.md).
# boolean
The type `boolean` can be used to store two states, `false` and `true`. The default is `false`.
## API
A boolean looks like this when send and received over the API:
```json
{
"bool": true
}
```
The above example has the value *true* for column `bool`.
## Index
The indexed document contains an entry with `false` or `true`. It is mapped as type [`boolean`](https://www.elastic.co/guide/en/elasticsearch/reference/current/boolean.html).
## Sorting
The ascending order of the sort is `false`, `true`. The sorting is independent of the requested search language.
## Export
The **XML representation** looks like this:
```xml
true
```
This is for a column `bool` and the value `true`. `false` is also always rendered.
The **CSV representation** is `false` or `true`, resp.
The **JSON representation** is a JSON boolean.
{% hint style="info" %}
The storage inside the **fylr** server distinguishes between `null` and `false`, but this is not visible over the API.
{% endhint %}
---
# 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://docs.fylr.io/for-developers/user-data-types/boolean.md?ask=&goal=
```
`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.