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

# dataTypeBySlug

Returns the latest non-deleted DataType version for the given slug within the caller's tenant, or null if no version exists.

Audience: Programmer

Returns the latest non-deleted DataType version for the given slug within the caller's tenant, or null if no version exists. Convenience wrapper for the relay query `dataTypes(where: {slug}, orderBy: {field: VERSION, direction: DESC}, first: 1)`.

**Served by:** [management](https://docs.pyck.cloud/graphql-api/services/management.md)

## Arguments

| Name   | Type    | Default | Description |
| ------ | ------- | ------- | ----------- |
| `slug` | String! |         |             |

## Returns

[DataType](https://docs.pyck.cloud/graphql-api/types/datatype.md)

## Example

Returns the latest non-deleted DataType version for the given slug within the caller's tenant, or null if no version exists.

```graphql
query GetDataTypeBySlug($slug: String!) {
  dataTypeBySlug(slug: $slug) {
    createdAt
    createdBy
    default
    deletedAt
    deletedBy
    description
    entity
    frontendSchema
    id
    jsonSchema
    name
    slug
    tenantID
    updatedAt
    updatedBy
    version
  }
}
```

**Variables**

```json
{
  "slug": "<data type slug, e.g. customer>"
}
```


---

# 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/datatypebyslug.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.
