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

# NodeDataType

nodeDataType Query

Audience: Programmer

Fetches a management-related object given its ID. This query follows the Relay Global Object Identification Specification and can retrieve any object that implements the NodeDataType interface.

## Arguments

| Name | Type  | Description                                                |
| ---- | ----- | ---------------------------------------------------------- |
| `id` | `ID!` | The unique identifier of the management object to retrieve |

## Return Type

`NodeDataType` - An interface that returns an object implementing the NodeDataType interface. This includes:

* `DataType` - JSON schema definition for entity data validation
* `Company` - Company/organization entity
* `Event` - Custom event definitions
* `User` - System user accounts

## Usage Example

### GraphQL Query

```graphql
query GetManagementObject($id: ID!) {
  nodeDataType(id: $id) {
    id
    ... on DataType {
      name
      slug
      schema
      entity
      enabled
      createdAt
      updatedAt
    }
    ... on Company {
      name
      organizationID
      tenantID
      users {
        id
        username
        email
      }
    }
    ... on Event {
      topic
      name
      description
      payload
      key
      createdAt
    }
    ... on User {
      username
      email
      idpID
      role
      groups {
        id
        name
      }
      company {
        name
      }
    }
  }
}
```

### Query Variables

```json
{
  "id": "RGF0YVR5cGU6MTIz"
}
```

### JavaScript Example

```javascript
const getManagementObject = async (objectId) => {
  const query = `
    query GetManagementObject($id: ID!) {
      nodeDataType(id: $id) {
        id
        __typename
        ... on DataType {
          name
          slug
          schema
          entity
          enabled
        }
        ... on Company {
          name
          organizationID
          tenantID
        }
        ... on User {
          username
          email
          role
        }
        ... on Event {
          topic
          name
          description
        }
      }
    }
  `;

  const response = await fetch('/graphql', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${accessToken}`
    },
    body: JSON.stringify({
      query,
      variables: { id: objectId }
    })
  });

  const { data } = await response.json();
  return data.nodeDataType;
};
```

## Type Detection

Use the `__typename` field to determine which specific type was returned:

```javascript
const object = await getManagementObject(id);
switch (object.__typename) {
  case 'DataType':
    console.log(`DataType: ${object.name} (${object.slug})`);
    break;
  case 'Company':
    console.log(`Company: ${object.name}`);
    break;
  case 'User':
    console.log(`User: ${object.username} (${object.email})`);
    break;
  case 'Event':
    console.log(`Event: ${object.topic} - ${object.name}`);
    break;
}
```

## Related

* [NodeDataType Interface](https://github.com/pyck-ai/docs/blob/main/graphql/interfaces/NodeDataType.md)
* [DataType Type](/graphql-api/types/datatype.md)
* [Company Type](/graphql-api/types/company.md)
* [User Type](/graphql-api/types/user.md)
* [Event Type](/graphql-api/types/event.md)
* [dataTypes Query](/graphql-api/queries/datatypes.md)
* [companies Query](/graphql-api/queries/companies.md)
* [users Query](/graphql-api/queries/users.md)
* [events Query](/graphql-api/queries/events.md)


---

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