> For the complete documentation index, see [llms.txt](https://docs.internetobject.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.internetobject.org/schema-definition-language/advanced-schema-concepts/union-types.md).

# Union Types (anyOf)

Members that accept more than one type, via anyOf.

When a field must accept values of **more than one type**, use the `anyOf` constraint on the `any` type (see [Any](/schema-definition-language/data-types/any.md)). A value is valid if it matches **any one** of the listed alternatives.

```ruby
id: { any, anyOf: [string, int] }
---
~ 42      # ✓ matches int
~ abc     # ✓ matches string
```

A value matching none of the alternatives is rejected:

```ruby
flag: { any, anyOf: [bool, int] }
---
~ T       # ✓
~ hello   # ✗ matches neither
```

## Constrained and structured alternatives

Each alternative may be a full MemberDef (with constraints) or an object shape, not just a bare type name:

```ruby
value: { any, anyOf: [ { int, multipleOf: 5 }, { int, multipleOf: 3 } ] }
---
~ 10      # ✓ multiple of 5
~ 9       # ✓ multiple of 3
```

## Guidance

* Order alternatives from most specific to least specific.
* Prefer `anyOf` over a bare `any` when the set of acceptable types is known — it keeps validation meaningful.

## See Also

* [Any](/schema-definition-language/data-types/any.md) · [MemberDef](/schema-definition-language/advanced-schema-concepts/memberdef.md)
* [Schema References](/definitions/schema-references.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.internetobject.org/schema-definition-language/advanced-schema-concepts/union-types.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.