> 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/queries/datatypeentities.md).

# DataTypeEntities

Data Type Entities Query

Returns a list of all available entity types that can have custom data types defined for them in the pyck system.

## Arguments

This query takes no arguments.

## Return Type

`[String!]` - A non-null array of string values representing entity names.

## Usage Example

```graphql
query {
  dataTypeEntities
}
```

**Response:**

```json
{
  "data": {
    "dataTypeEntities": [
      "item",
      "customer", 
      "supplier",
      "picking_order",
      "picking_order_item",
      "inbound",
      "inbound_item",
      "item_movement",
      "repository_movement",
      "file",
      "item_set",
      "repository",
      "collection_movement"
    ]
  }
}
```

## Usage with Data Types

```graphql
query {
  # Get all available entity types
  dataTypeEntities
  
  # Then get data types for a specific entity
  dataTypes(
    where: {
      entity: "item"
    }
  ) {
    edges {
      node {
        id
        name
        slug
        entity
        jsonSchema
      }
    }
  }
}
```

## Notes

* This query returns all entity types that support custom data type definitions
* Use this to understand which entities can have custom fields and schemas
* Essential for building dynamic forms and custom field management interfaces
* The returned strings correspond to entity names used in the `entity` field of DataType objects
* These entities represent core business objects in the pyck warehouse management system


---

# 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/queries/datatypeentities.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.