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

# String

UTF-8 character sequence scalar type

Audience: Programmer

The `String` scalar type represents textual data, represented as UTF-8 character sequences. The String type is most often used by GraphQL to represent free-form human-readable text.

## Format

* UTF-8 encoded text
* No length limit (unless specified by field)
* Supports all Unicode characters
* Empty strings are valid

## Usage

```graphql
type Customer {
  id: ID!
  name: String!
  description: String  # Nullable
  code: String!
}

mutation {
  createCustomer(input: {
    name: "Acme Corporation"
    code: "ACME-001"
    description: "Primary supplier for widgets"
  }) {
    customer {
      id
    }
  }
}
```

## Common String Fields

* Names and titles
* Descriptions and comments
* Codes and SKUs
* URLs and paths
* JSON strings (for Map fields)

## Filtering

String fields often support these filters:

* `field_CONTAINS` - Substring match
* `field_STARTS_WITH` - Prefix match
* `field_ENDS_WITH` - Suffix match
* `field_IN` - Match any of the values
* `field_NOT` - Negation

## See Also

* [Input Types](/graphql-api/inputs.md) - String-based filters
* [Map](/graphql-api/scalars/map.md) - JSON data as strings


---

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