25 lines
1.0 KiB
Markdown
25 lines
1.0 KiB
Markdown
---
|
|
title: Input objects
|
|
intro: Input objects can be described as "composable objects" because they include a set of input fields that define the object.
|
|
redirect_from:
|
|
- /v4/input_object
|
|
- /v4/reference/input_object
|
|
versions:
|
|
fpt: '*'
|
|
ghec: '*'
|
|
ghes: '*'
|
|
topics:
|
|
- API
|
|
autogenerated: graphql
|
|
---
|
|
|
|
## About input objects
|
|
|
|
[Input objects](https://spec.graphql.org/June2018/#sec-Input-Objects) can be described as "composable objects" because they include a set of input fields that define the object.
|
|
|
|
For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/graphql/reference/objects) **may** have input objects, whereas [mutations](/graphql/reference/mutations) **require** input objects.
|
|
|
|
For more information, see [AUTOTITLE](/graphql/guides/forming-calls-with-graphql#about-mutations).
|
|
|
|
<!-- Content after this section is automatically generated -->
|