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

# ID

Unique identifier scalar type

Audience: Programmer

The `ID` scalar type represents a unique identifier, often used to refetch an object or as the key for a cache. The ID type is serialized in the same way as a String; however, defining it as an ID signifies that it is not intended to be human-readable.

## Format

* Serialized as String
* Not intended for human consumption
* Must be unique within its type
* Often UUIDs or database primary keys

## Usage

```graphql
type InventoryItem {
  id: ID!
  sku: String!
}

query {
  inventoryItem(id: "550e8400-e29b-41d4-a716-446655440000") {
    sku
  }
}
```

## Best Practices

1. Always treat IDs as opaque strings
2. Never parse or manipulate ID values
3. Use for caching and refetching
4. Consider using UUIDs for distributed systems

## See Also

* [UUID](https://github.com/pyck-ai/docs/blob/main/graphql/scalars/UUID.md) - Specific UUID scalar type
* [Node Interface](/graphql-api/interfaces/node.md) - Interface requiring ID field


---

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