> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/scalars/boolean.md).

# Boolean

True or false scalar type

Audience: Programmer

The `Boolean` scalar type represents `true` or `false`.

## Format

* Only two possible values: `true` or `false`
* Not nullable when defined as `Boolean!`
* Case-sensitive (lowercase only)

## Usage

```graphql
type InventoryItem {
  id: ID!
  isActive: Boolean!
  isDeleted: Boolean!
  hasStock: Boolean
}

query {
  inventoryItems(
    where: {
      isActive: true
      isDeleted: false
    }
  ) {
    edges {
      node {
        id
        hasStock
      }
    }
  }
}
```

## Common Boolean Fields

* Status flags (`isActive`, `isDeleted`, `isEnabled`)
* Feature toggles (`hasFeatureX`, `canDoY`)
* Existence checks (`hasChildren`, `isEmpty`)
* Permissions (`canEdit`, `canDelete`)
* State indicators (`isLoading`, `isComplete`)

## Filtering

Boolean fields in where clauses:

```graphql
query {
  items(where: {
    isActive: true
    hasStock: false
    # Negation
    NOT: {
      isDeleted: true
    }
  }) {
    edges {
      node {
        id
      }
    }
  }
}
```

## Best Practices

1. Use clear, positive names when possible (`isActive` vs `isInactive`)
2. Consider nullable booleans for tri-state logic
3. Document the default value
4. Use for binary states only

## See Also

* [Input Types](/graphql-api/inputs.md) - Boolean filters in where clauses
* [Types](/graphql-api/types.md) - Types using boolean fields


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/scalars/boolean.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.