# GraphQL
Formie supports accessing [Form](docs:developers/form) and [Submission](docs:developers/submission) objects via GraphQL. Be sure to read about [Craft's GraphQL support](https://craftcms.com/docs/4.x/graphql.html).

:::tip
Have a look at our [headless Formie demo](https://formie-headless.verbb.io/?form=contactForm) to get a feel for what's possible with GraphQL.
:::

## Forms

### Example

:::code
```graphql GraphQL
{
    formieForm (handle: "contactForm") {
        title
        handle

        settings {
            errorMessageHtml
        }
        
        pages {
            label

            rows {
                rowFields {
                    label
                    handle
                    type
                    displayName

                    ... on Field_Name {
                        fields {
                            label
                            enabled
                            required
                        }
                    }

                    ... on Field_Email {
                        placeholder
                    }
                }
            }
        }
    }
}
```

```json JSON Response
{
    "data": {
        "formieForm": {
            "title": "Contact Form",
            "handle": "contactForm",
            "settings": {
                "errorMessageHtml": "Couldn’t save submission due to errors."
            },
            "pages": [
                {
                    "label": "Page 1",
                    "rows": [
                        {
                            "rowFields": [
                                {
                                    "label": "Your Name",
                                    "handle": "yourName",
                                    "type": "verbb\\formie\\fields\\Name",
                                    "displayName": "Name",
                                    "fields": [
                                        {
                                            "label": "Prefix",
                                            "enabled": false,
                                            "required": false
                                        },
                                        {
                                            "label": "First Name",
                                            "enabled": true,
                                            "required": true
                                        },
                                        {
                                            "label": "Middle Name",
                                            "enabled": false,
                                            "required": false
                                        },
                                        {
                                            "label": "Last Name",
                                            "enabled": true,
                                            "required": true
                                        }
                                    ]
                                }
                            ]
                        },
                        {
                            "rowFields": [
                                {
                                    "label": "Email Address",
                                    "handle": "emailAddress",
                                    "type": "verbb\\formie\\fields\\Email",
                                    "displayName": "Email",
                                    "placeholder": "eg. psherman@wallaby.com"
                                }
                            ]
                        },
                        {
                            "rowFields": [
                                {
                                    "label": "Message",
                                    "handle": "message",
                                    "type": "verbb\\formie\\fields\\MultiLineText",
                                    "displayName": "MultiLineText"
                                }
                            ]
                        }
                    ]
                }
            ]
        }
    }
}
```
:::

### The `formieForms` query
This query is used to query for [Form](docs:developers/form) objects. You can also use the singular `formieForm` to fetch a single form.

| Argument | Type | Description
| - | - | -
| `id`| `[QueryArgument]` | Narrows the query results based on the elements’ IDs.
| `uid`| `[String]` | Narrows the query results based on the elements’ UIDs.
| `archived`| `Boolean` | Narrows the query results to only elements that have been archived.
| `trashed`| `Boolean` | Narrows the query results to only elements that have been soft-deleted.
| `unique`| `Boolean` | Determines whether only elements with unique IDs should be returned by the query.
| `title`| `[String]` | Narrows the query results based on the elements’ titles.
| `search`| `String` | Narrows the query results to only elements that match a search query.
| `ref`| `[String]` | Narrows the query results based on a reference string.
| `fixedOrder`| `Boolean` | Causes the query results to be returned in the order specified by the `id` argument.
| `inReverse`| `Boolean` | Causes the query results to be returned in reverse order.
| `dateCreated`| `[String]` | Narrows the query results based on the elements’ creation dates.
| `dateUpdated`| `[String]` | Narrows the query results based on the elements’ last-updated dates.
| `offset`| `Int` | Sets the offset for paginated results.
| `limit`| `Int` | Sets the limit for paginated results.
| `orderBy`| `String` | Sets the field the returned elements should be ordered by.
| `handle`| `[String]` | Narrows the query results based on the form’s handle.


### The `FormInterface` interface
This is the interface implemented by all forms.

| Field | Type | Description
| - | - | -
| `id`| `ID` | The id of the entity.
| `uid`| `String` | The uid of the entity.
| `title`| `String` | The element’s title.
| `enabled`| `Boolean` | Whether the element is enabled or not.
| `archived`| `Boolean` | Whether the element is archived or not.
| `searchScore`| `String` | The element’s search score, if the `search` parameter was used when querying for the element.
| `trashed`| `Boolean` | Whether the element has been soft-deleted or not.
| `dateCreated`| `DateTime` | The date the element was created.
| `dateUpdated`| `DateTime` | The date the element was last updated.
| `handle`| `String` | The form’s handle.
| `pages`| `[PageInterface]` | The form’s pages.
| `rows`| `[RowInterface]` | The form’s rows.
| `formFields`| `[FieldInterface]` | The form’s fields.
| `settings`| `[FormSettingsInterface]` | The form’s settings.
| `configJson`| `String` | The form’s config as JSON.
| `templateHtml`| `String` | The form’s rendered HTML.
| `csrfToken`| `[CsrfTokenInterface]` | A CSRF token (name and value).
| `captchas`| `[CaptchaValueInterface]` | A list of captcha values (name and value) to assist with spam protection.
| `submissionMutationName`| `String` | The form’s GQL mutation name for submissions to use.
| `submissionEndpoint`| `String` | The form’s endpoint for sending submissions to, if using POST requests.

#### The `formFields` query
This query is used to query for [Field](docs:developers/field) objects on a form.

| Argument | Type | Description
| - | - | -
| `includeDisabled`| `Boolean` | Expands the query results to include fields that have a visibility of "disabled". These are omitted by default.

#### The `templateHtml` query
You can also add query arguments to `templateHtml` to narrow your results.

| Argument | Type | Description
| - | - | -
| `options`| `String` | The form template HTML will be rendered with these JSON serialized options.
| `populateFormValues`| `String` | The form field values will be populated with these JSON serialized options.


### The `FormSettingsInterface` interface
This is the interface implemented by all forms.

| Field | Type | Description
| - | - | -
| `displayFormTitle`| `Boolean` | Whether to show the form’s title.
| `displayCurrentPageTitle`| `Boolean` | Whether to show the form’s current page title.
| `displayPageTabs`| `Boolean` | Whether to show the form’s page tabs.
| `displayPageProgress`| `Boolean` | Whether to show the form’s page progress.
| `scrollToTop`| `Boolean` | Whether to the form should scroll to the top of the page when submitted.
| `progressPosition`| `String` | The form’s progress bar position. Either `start` or `end`.
| `defaultLabelPosition`| `String!` | The form’s default label position for fields. This will be a `verbb\formie\positions` class name.
| `defaultInstructionsPosition`| `String!` | The form’s default instructions position for fields. This will be a `verbb\formie\positions` class name.
| `submitMethod`| `String!` | The form’s submit method. Either `page-reload` or `ajax`.
| `submitAction`| `String!` | The form’s submit action. Either `message`, `entry`, `url`, `reload`.
| `submitActionTab`| `String!` | The form’s submit redirect option (if in new tab or same tab). Either `same-tab` or `new-tab`.
| `submitActionFormHide`| `Boolean` | Whether to hide the form’s success message.
| `submitActionMessageHtml`| `String` | The form’s submit success message.
| `submitActionMessageTimeout`| `Integer` | The form’s submit success message timeout in seconds.
| `submitActionMessagePosition`| `String` | The form’s submit message position. Either `top-form` or `bottom-form`.
| `loadingIndicator`| `String!` | The type of loading indicator to use. Either `spinner` or `text`.
| `loadingIndicatorText`| `String!` | The form’s loading indicator text.
| `validationOnSubmit`| `Boolean` | Whether to validate the form’s on submit.
| `validationOnFocus`| `Boolean` | Whether to validate the form’s on focus.
| `errorMessageHtml`| `String` | The form’s submit error message.
| `errorMessagePosition`| `String` | The form’s error message position. Either `null`, `top-form` or `bottom-form`.
| `redirectUrl`| `String!` | The form’s submit action redirect URL, resolved depending on `submitAction` being `entry` or `url`.
| `redirectEntry`| `EntryInterface!` | The form’s submit action entry (for redirection), if `submitAction` is `entry`.
| `integrations`| `[FormIntegrationsInterface]` | The form’s enabled integrations.


### The `FormIntegrationsInterface` interface
This is the interface implemented by all form integrations.

| Field | Type | Description
| - | - | -
| `name`| `String` | The integration’s name.
| `handle`| `String` | The integration’s handle.
| `enabled`| `Boolean` | Whether the integration is enabled.
| `settings`| `String` | The integration’s settings as a JSON string.


### The `PageInterface` interface
This is the interface implemented by all pages.

| Field | Type | Description
| - | - | -
| `id`| `ID` | The id of the entity.
| `uid`| `String` | The uid of the entity.
| `dateCreated`| `DateTime` | The date the element was created.
| `dateUpdated`| `DateTime` | The date the element was last updated.
| `label`| `String` | The label of the page.
| `rows`| `[RowInterface]` | The pages’s rows.
| `pageFields`| `[FieldInterface]` | The pages’s fields.
| `settings`| `[PageSettingsInterface]` | The pages’s settings, including buttons.

#### The `pageFields` query
This query is used to query for [Field](docs:developers/field) objects on a page.

| Argument | Type | Description
| - | - | -
| `includeDisabled`| `Boolean` | Expands the query results to include fields that have a visibility of "disabled". These are omitted by default.


### The `PageSettingsInterface` interface
This is the interface implemented by all pages.

| Field | Type | Description
| - | - | -
| `submitButtonLabel`| `String!` | The page’s submit button label.
| `backButtonLabel`| `String!` | The page’s back button label.
| `showBackButton`| `Boolean` | Whether to show the page’s back button.
| `buttonsPosition`| `String` | The page’s button (back and submit) positions.
| `cssClasses`| `String!` | The page’s button (back and submit) CSS classes.
| `containerAttributes| `[FieldAttribute]!` | The page’s button (back and submit) container attributes.
| `inputAttributes| `[FieldAttribute]!` | The page’s button (back and submit) input attributes.
| `enablePageConditions`| `Boolean` | Whether the page has conditions enabled.
| `pageConditions`| `String` | The page’s conditions as a JSON string.
| `enableNextButtonConditions`| `Boolean` | Whether the page’s next button has conditions enabled, for multi-page forms.
| `nextButtonConditions`| `String` | The page’s conditions for whether to show the next button, for multi-page forms as a JSON string.

### The `RowInterface` interface
This is the interface implemented by all rows.

| Field | Type | Description
| - | - | -
| `id`| `ID` | The id of the entity.
| `uid`| `String` | The uid of the entity.
| `rowFields`| `[FieldInterface]` | The row’s fields.

#### The `rowFields` query
This query is used to query for [Field](docs:developers/field) objects on a row.

| Argument | Type | Description
| - | - | -
| `includeDisabled`| `Boolean` | Expands the query results to include fields that have a visibility of "disabled". These are omitted by default.


### The `FieldInterface` interface
This is the interface implemented by all fields. Note that as settings are specific to fields, you'll need to use [Inline Fragments](https://graphql.org/learn/queries/#inline-fragments).

| Field | Type | Description
| - | - | -
| `id`| `ID` | The id of the entity.
| `uid`| `String` | The uid of the entity.
| `label`| `String` | The field’s label.
| `handle`| `String` | The field’s handle.
| `instructions`| `String` | The field’s instructions.
| `required`| `Boolean` | Whether the field is required or not.
| `type`| `String` | The field’s full class type.
| `displayName`| `String` | The field’s display name (last portion of the class).
| `typeName`| `String` | The field’s full GQL type.
| `inputTypeName`| `String` | The field’s full GQL input type. Useful for mutations.
| `matchField`| `String!` | The field handle for another field that this value should match exactly.
| `placeholder`| `String!` | The field’s placeholder.
| `defaultValue`| `String` | The field’s default value as a string. Some fields have different fields for their default value.
| `prePopulate`| `String!` | The field’s pre-populated value extracted from the query string.
| `errorMessage`| `String!` | The field’s error message.
| `labelPosition`| `String!` | The field’s label position. This will be a `verbb\formie\positions` class name.
| `instructionsPosition`| `String!` | The field’s instructions position. This will be a `verbb\formie\positions` class name.
| `cssClasses`| `String!` | The field’s CSS classes.
| `containerAttributes`| `[FieldAttribute]` | The field’s container attributes.
| `inputAttributes`| `[FieldAttribute]` | The field’s input attributes.
| `includeInEmail`| `Boolean` | Whether the field should be included in email content.
| `enableConditions`| `Boolean` | Whether the field has conditions enabled.
| `conditions`| `String!` | The field’s conditions as a JSON string.
| `enableContentEncryption`| `Boolean` | Whether the field has content encryption enabled.
| `visibility`| `String!` | The field’s visibility.

Once using the necessary [Inline Fragments](https://graphql.org/learn/queries/#inline-fragments) for each field type, you'll have access to the same variables as described on the [Field](docs:developers/field) docs.

#### Agree
| Field | Type | Description
| - | - | -
| `description` | `String!` | The description for the field. This will be shown next to the checkbox.
| `descriptionHtml` | `String` | The HTML description for the field.
| `checkedValue ` | `String!` | The value of this field when it is checked.
| `uncheckedValue` | `String!` | The value of this field when it is unchecked.
| `defaultState` | `Boolean` | Whether the default state should be checked or unchecked.


#### Calculations
| Field | Type | Description
| - | - | -
| `formula` | `String!` | A JSON string including the parsed formula and variables for any fields used in the formula.


#### Categories
| Field | Type | Description
| - | - | -
| `placeholder` | `String!` | The option shown initially, when no option is selected.
| `source` | `String!` | Which source do you want to select categories from?
| `branchLimit` | `String!` | Limit the number of selectable category branches.
| `categories` | `CategoryQuery` | The category query for available categories.
| `displayType` | `String` | What sort of field to show on the front-end for users. Either `dropdown`, `checkboxes` or `radio`.


#### Checkboxes
| Field | Type | Description
| - | - | -
| `options` | `[FieldOption]` | Define the available options for users to select from.
| `layout` | `String` | Select which layout to use for these fields.
| `toggleCheckbox` | `String!` | Whether to add an additional checkbox to toggle all checkboxes in this field by. Either `null`, `top`, `bottom`.
| `toggleCheckboxLabel` | `String!` | The label for the toggle checkbox field.


#### Date/Time
| Field | Type | Description
| - | - | -
| `defaultDate` | `DateTime` | The default date to be used for the field.
| `displayType` | `String` | The display layout for this field. Either `calendar`, `dropdowns` or `inputs`.
| `dateFormat` | `String` | The chosen format for the date.
| `timeFormat` | `String` | The chosen format for the time.
| `useDatePicker` | `Boolean` | Whether this field should use the Flatpickr datepicker.
| `datePickerOptions` | `Boolean` | A collection of options for the Flatpickr datepicker.
| `minDate` | `DateTime` | The minimum allowed date.
| `maxDate` | `DateTime` | The maximum allowed date.
| `availableDaysOfWeek` | `String` | A JSON string of available days of the week enabled.

#### Dropdown
| Field | Type | Description
| - | - | -
| `multiple` | `Boolean` | Whether this field should allow multiple options to be selected.
| `options` | `[FieldOption]` | Define the available options for users to select from.
| `defaultValue` | `String` | Entering a default value will place the value in the field when it loads.


#### Email Address
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The text that will be shown if the field doesn’t have a value.
| `defaultValue` | `String` | Entering a default value will place the value in the field when it loads.
| `validateDomain` | `Boolean` | Whether to validate the domain when the value is saved.
| `blockedDomains` | `[String]!` | A list of domains to block values.
| `uniqueValue` | `Boolean` | Whether to the value of this field should be unique across all submissions for the form.


#### Entries
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The option shown initially, when no option is selected.
| `sources` | `String` | Which sources do you want to select entries from?
| `limit` | `String` | Limit the number of selectable entries.
| `entries` | `EntryQuery` | The entry query for available entries.
| `displayType` | `String` | What sort of field to show on the front-end for users. Either `dropdown`, `checkboxes` or `radio`.


#### File Upload
| Field | Type | Description
| - | - | -
| `uploadLocationSource` | `String` | The volume for files to be uploaded into.
| `uploadLocationSubpath` | `String` | The sub-path for the files to be uploaded into.
| `limitFiles` | `String` | Limit the number of files a user can upload.
| `sizeLimit` | `String` | Limit the size of the files a user can upload.
| `allowedKinds` | `String` | A collection of allowed mime-types the user can upload.


#### Group
See [nested fields](#nested-fields) for how to query the inner fields.


#### Heading
| Field | Type | Description
| - | - | -
| `headingSize` | `String!` | Choose the size for the heading.


#### Hidden
| Field | Type | Description
| - | - | -
| `defaultOption` | `String!` | The selected option for the preset default value chosen.
| `defaultValue` | `String!` | Entering a default value will place the value in the field when it loads. This will be dependent on the value chosen for the `defaultOption`.
| `queryParameter` | `String!` | If `query string` is selected for the `defaultOption`, this will contain the query string parameter to look up.
| `cookieName` | `String!` | If `cookie` is selected for the `defaultOption`, this will contain the cookie name to look up.


#### Html
| Field | Type | Description
| - | - | -
| `htmlContent` | `String!` | Enter HTML content to be rendered for this field.


#### Multi-Line Text
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The text that will be shown if the field doesn’t have a value.
| `defaultValue` | `String` | Entering a default value will place the value in the field when it loads.
| `limit`| `Boolean` | Whether the field should limit content.
| `minType`| `String!` | The field’s minimum text type. Either `characters` or `words`.
| `min`| `Int!` | The field’s minimum number of characters/words to limit, based on `minType`.
| `maxType`| `String!` | The field’s maximum text type. Either `characters` or `words`.
| `max`| `Int!` | The field’s maximum number of characters/words, based on `maxType`.
| `useRichText` | `Boolean` | Whether the front-end of the field should use a Rich Text editor. This is powered by [Pell](https://github.com/jaredreich/pell).
| `richTextButtons` | `[String]!` | An array of available buttons the Rich Text field should use. Consult the [Pell](https://github.com/jaredreich/pell) docs for these options.


#### Name
| Field | Type | Description
| - | - | -
| `useMultipleFields` | `Boolean` | Whether this field should use multiple fields for users to enter their details.


#### Number
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The text that will be shown if the field doesn’t have a value.
| `defaultValue` | `String` | Entering a default value will place the value in the field when it loads.
| `limit` | `Boolean` | Whether to limit the numbers for this field.
| `min` | `Float` | The minimum number that can be entered for this field.
| `max` | `Float` | The maximum number that can be entered for this field.
| `decimals` | `Int!` | Set the number of decimal points to format the field value.


#### Payment
| Field | Type | Description
| - | - | -
| `paymentIntegration` | `String!` | The handle of the [Payment Integration](docs:integrations/payments) chosen.
| `paymentIntegrationType` | `String!` | The class of the [Payment Integration](docs:integrations/payments) chosen.
| `providerSettings` | `String!` | A JSON string of settings for the payment provider to use.


#### Phone
| Field | Type | Description
| - | - | -
| `showCountryCode` | `String` | Whether to show an additional dropdown for selecting the country code.
| `countryLabel` | `String` | The label for the Country sub-field.
| `countryPlaceholder` | `String` | The placeholder for the Country sub-field.
| `countryDefaultValue` | `String` | The default value for the Country sub-field.
| `countryEnabled` | `Boolean` | Whether the Country sub-field is enabled in the control panel.
| `countryOptions` | `[FieldAttribute]` | An array of options available to pick a country from.

#### Products
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The option shown initially, when no option is selected.
| `sources` | `String` | Which sources do you want to select products from?
| `limit` | `Boolean` | Limit the number of selectable products.
| `products` | `ProductQuery` | The product query for available products.
| `displayType` | `String` | What sort of field to show on the front-end for users. Either `dropdown`, `checkboxes` or `radio`.


#### Radio
| Field | Type | Description
| - | - | -
| `options` | `[FieldOption]` | Define the available options for users to select from.
| `layout` | `String` | Select which layout to use for these fields. Either `vertical` or `horizontal`,


#### Recipients
| Field | Type | Description
| - | - | -
| `displayType` | `String` | What sort of field to show on the front-end for users. Either `hidden`, `dropdown`, `checkboxes` or `radio`.
| `options` | `[FieldOption]` | Define the available options for users to select from.


#### Repeater
See [nested fields](#nested-fields) for how to query the inner fields.

| Field | Type | Description
| - | - | -
| `addLabel` | `String!` | The label for the button that adds another instance.
| `minRows` | `Int!` | The minimum required number of instances of this repeater's fields that must be completed.
| `maxRows` | `Int!` | The maximum required number of instances of this repeater's fields that must be completed.


#### Section
| Field | Type | Description
| - | - | -
| `border` | `String!` | Add a border to this section.
| `borderWidth` | `Int!` | Set the border width (in pixels).
| `borderColor` | `String!` | Set the border color.


#### Single-Line Text
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The text that will be shown if the field doesn’t have a value.
| `defaultValue` | `String` | Entering a default value will place the value in the field when it loads.
| `limit`| `Boolean` | Whether to limit the content of this field.
| `minType`| `String!` | The field’s minimum text type. Either `characters` or `words`.
| `min`| `Int!` | The field’s minimum number of characters/words to limit, based on `minType`.
| `maxType`| `String!` | The field’s maximum text type. Either `characters` or `words`.
| `max`| `Int!` | The field’s maximum number of characters/words, based on `maxType`.


#### Table
| Field | Type | Description
| - | - | -
| `columns` | `[TableColumn]!` | Define the columns your table should have.
| `defaults` | `String!` | Define the default values for the field as a JSON string.
| `addRowLabel` | `String` | The label for the button that adds another row.
| `static` | `Boolean` | Whether this field should disallow adding more rows, showing only the default rows.
| `minRows` | `Int!` | The minimum required number of rows in this table that must be completed.
| `maxRows` | `Int!` | The maximum required number of rows in this table that must be completed.


#### Tags
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The option shown initially, when no option is selected.
| `source` | `String` | Which source do you want to select tags from?
| `tags` | `TagQuery` | The tag query for available tags.
| `displayType` | `String` | What sort of field to show on the front-end for users. Either `dropdown`, `checkboxes` or `radio`.


#### Users
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The option shown initially, when no option is selected.
| `sources` | `String` | Which sources do you want to select users from?
| `limit` | `String` | Limit the number of selectable users.
| `users` | `UserQuery` | The user query for available users.
| `displayType` | `String` | What sort of field to show on the front-end for users. Either `dropdown`, `checkboxes` or `radio`.


#### Variants
| Field | Type | Description
| - | - | -
| `placeholder` | `String` | The option shown initially, when no option is selected.
| `source ` | `String` | Which source do you want to select variants from?
| `limit` | `String` | Limit the number of selectable variants.
| `variants` | `VariantQuery` | The variant query for available variants.
| `displayType` | `String` | What sort of field to show on the front-end for users. Either `dropdown`, `checkboxes` or `radio`.


#### Sub-Fields
For sub-fields like Address and multi-Name, you have access to `nestedRows` and `fields`.

```graphql
{
    formieForm (handle: "contactForm") {
        title
        handle
        
        formFields {
            label

            ... on Field_Name {
                nestedRows {
                    fields {
                        label
                    }
                }
            }

            ... on Field_Address {
                fields {
                    label
                }
            }
        }
    }
}
```


#### Nested Fields
For nested fields like Group and Repeater, you have access to `nestedRows` and `fields`.

```graphql
{
    formieForm (handle: "contactForm") {
        title
        handle
        
        formFields {
            label

            ... on Field_Group {
                nestedRows {
                    fields {
                        label
                    }
                }
            }
        }
    }
}
```

### The `FieldAttribute` interface
This interface defines a key-value stored value, where you want the label and value.

| Field | Type | Description
| - | - | -
|`label` | `String` | The label of the attribute.
|`value` | `String` | The value of the attribute.

### The `FieldOption` interface
For option-based fields, a `FieldOption` represents a single option row.

| Field | Type | Description
| - | - | -
|`label` | `String` | The label of the option.
|`value` | `String` | The value of the option.
|`isOptgroup` | `Boolean` | Whether this option has been marked as an `optgroup`.
|`isDefault` | `Boolean` | Whether this option has been marked as a default.

### The `TableColumn` interface
This interface defines the columns for a Table field.

| Field | Type | Description
| - | - | -
|`heading` | `String` | The column heading.
|`handle` | `String` | The column handle.
|`width` | `String` | The column width.
|`type` | `String` | The column type.

### The `CsrfTokenInterface` interface
This is the interface to allow easy retrieval of a CSRF token and value.

| Field | Type | Description
| - | - | -
| `name`| `String` | The CSRF name.
| `value`| `String` | The CSRF token.

### The `CaptchaValueInterface` interface
This is the interface to fetch enabled captchas for the form.

| Field | Type | Description
| - | - | -
| `handle`| `String` | The captcha name.
| `name`| `String` | The captcha name.
| `value`| `String` | The captcha value.


## Submissions

### Example

:::code
```graphql GraphQL
{
    formieSubmissions (form: "contactForm") {
        title

        ... on contactForm_Submission {
            yourName
            emailAddress
            message
        }
    }
}
```

```json JSON Response
{
    "data": {
        "formieSubmissions": [
            {
                "title": "2020-07-24 22:01:59",
                "yourName": "Peter Sherman",
                "emailAddress": "psherman@wallaby.com",
                "message": "Just wanted to say hi!"
            }
        ]
    }
}
```
:::

### The `formieSubmissions` query
This query is used to query for [Submission](docs:developers/submission) objects. You can also use the singular `formieSubmission` to fetch a single submission.

| Argument | Type | Description
| - | - | -
| `id`| `[QueryArgument]` | Narrows the query results based on the elements’ IDs.
| `uid`| `[String]` | Narrows the query results based on the elements’ UIDs.
| `archived`| `Boolean` | Narrows the query results to only elements that have been archived.
| `trashed`| `Boolean` | Narrows the query results to only elements that have been soft-deleted.
| `unique`| `Boolean` | Determines whether only elements with unique IDs should be returned by the query.
| `title`| `[String]` | Narrows the query results based on the elements’ titles.
| `search`| `String` | Narrows the query results to only elements that match a search query.
| `ref`| `[String]` | Narrows the query results based on a reference string.
| `fixedOrder`| `Boolean` | Causes the query results to be returned in the order specified by the `id` argument.
| `inReverse`| `Boolean` | Causes the query results to be returned in reverse order.
| `dateCreated`| `[String]` | Narrows the query results based on the elements’ creation dates.
| `dateUpdated`| `[String]` | Narrows the query results based on the elements’ last-updated dates.
| `offset`| `Int` | Sets the offset for paginated results.
| `limit`| `Int` | Sets the limit for paginated results.
| `orderBy`| `String` | Sets the field the returned elements should be ordered by.
| `form`| `[String]` | Narrows the query results based on the form’s handle.

You can also query based on a field handle, like you would a regular element query in Twig.

:::code
```graphql GraphQL
{
    formieSubmissions (form: "contactForm", emailAddress: "psherman@wallaby.com") {
        title
    }
}
```

#### Nested Fields
An example for querying Repeater and Group field content.

```graphql
{
    formieSubmissions (handle: "contactForm") {
        title
        
        ... on contactForm_Submission {
            groupFieldHandle {
                myFieldHandle
            }

            repeaterFieldHandle {
                rows {
                    myFieldHandle
                }
            }
        }
    }
}
```

## Mutations
Mutations in GraphQL provide a way of modifying data. The actual mutations will vary depending on the schema. There are some common mutations per GraphQL object type as well as type-specific mutations.

Be sure to read the [GraphQL docs](https://craftcms.com/docs/3.x/graphql.html#mutations).

### Submissions

#### Saving a submission

To create or update a submission use the form-specific mutation, which will have the name in the form of `save_<formHandle>_Submission`.

<!-- BEGIN SUBMISSION MUTATION ARGS -->

| Argument | Type | Description
| - | - | -
| `id`| `ID` | Set the element’s ID.
| `uid`| `String` | Set the element’s UID.
| `enabled`| `Boolean` | Whether the element should be enabled.
| `title`| `String` | Set the element’s title.
| `status`| `String` | Set the element’s status as its handle.
| `statusId`| `Int` | Set the element’s statusId.
| `isIncomplete`| `Boolean` | Set the element’s incomplete state.
| `...`|  | More arguments depending on the field layout for the form

<!-- END SUBMISSION MUTATION ARGS -->

The below shows an example request to create a new submission. For this form, we have a single-line text field with the handle `yourName`. In our query variables, we pass the value(s) we want to use in the query.

```graphql
// Query
mutation saveSubmission($yourName:String) {
    save_contactForm_Submission(yourName: $yourName) {
        title
        yourName
    }
}

// Query Variables
{
    "yourName": "Peter Sherman"
}
```

With the resulting output:

```json
{
    "data": {
        "save_contactForm_Submission": {
            "title": "2020-08-18 10:29:06",
            "yourName": "Peter Sherman"
        }
    }
}
```

#### Complex Fields
Some fields, such as Name and Address fields are much more than primitive values. Instead, their content needs to be provided as an object. The Name field is an exception, as it can be set to have multiple fields, or a single field.

For example, you can populate a name and address field using the below:

```graphql
// Query
mutation saveSubmission($yourName:contactForm_yourName_FormieNameInput $yourAddress:contactForm_yourAddress_FormieAddressInput) {
    save_contactForm_Submission(yourName: $yourName, yourAddress: $yourAddress) {
        yourName
        yourAddress
    }
}

// Query Variables
{
    "yourName": {
        "firstName": "Peter",
        "lastName": "Sherman"
    },
    "yourAddress": {
        "address1": "42 Wallaby Way",
        "city": "Sydney",
        "zip": "2000",
        "state": "NSW",
        "country": "Australia"
    }
}
```

You'll notice the `contactForm_yourName_FormieNameInput` type being used. This follows the structure of `{formHandle}_{fieldHandle}_FormieNameInput`. There are also a number of other input types to consider.

#### Address Field
```graphql
// Query
mutation saveSubmission($yourAddress:contactForm_yourAddress_FormieAddressInput) {
    save_contactForm_Submission(yourAddress: $yourAddress) {
        yourAddress
    }
}

// Query Variables
{
    "yourAddress": {
        "address1": "42 Wallaby Way",
        "city": "Sydney",
        "zip": "2000",
        "state": "NSW",
        "country": "Australia"
    }
}
```

#### File Upload Field
When uploading a file, you must provide an array of upload data with a `base64` encoded data, so that Formie can create the asset element. Provide this as `fileData`, and you can also supply an optional `filename` variable to name the asset correctly. If you do not supply this, a filename will be generated for you.

```graphql
// Query
mutation saveSubmission($fileUploadField:[FileUploadInput]) {
    save_contactForm_Submission(fileUploadField: $fileUploadField) {
        title
    }
}

// Query Variables
{
    "fileUploadField": [
        {
            "fileData": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQUA...",
            "filename": "testing.png"
        },
        {
            "fileData": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQUA..."
        }
    ]
}
```

If you have already uploaded your asset through other means, you can provide an `assetId` in the same fashion.

```graphql
// Query
mutation saveSubmission($fileUploadField:[FileUploadInput]) {
    save_contactForm_Submission(fileUploadField: $fileUploadField) {
        title
    }
}

// Query Variables
{
    "fileUploadField": [
        {
            "assetId": 1234
        },
        {
            "assetId": 4562
        }
    ]
}
```

#### Group Field
```graphql
// Query
mutation saveSubmission($groupField:contactForm_groupField_FormieGroupInput) {
    save_contactForm_Submission(groupField: $groupField) {
        groupField {
            firstValue: firstValue
            secondValue: secondValue
        }
    }
}

// Query Variables
{
    "groupField": {
        "firstValue": "This content",
        "secondValue": "is for groups"
    }
}
```

#### Repeater Field
```graphql
// Query
mutation saveSubmission($repeaterField:contactForm_repeaterField_FormieRepeaterInput) {
    save_contactForm_Submission(repeaterField: $repeaterField) {
        repeaterField {
            rows {
                field1: field1
                field2: field2
            }
        }
    }
}

// Query Variables
{
    "repeaterField": {
        "rows": [
            {
                "field1": "First Block - Field 1",
                "field2": "First Block - Field 2"
            },
            {
                "field1": "Second Block - Field 1",
                "field2": "Second Block - Field 2"
            }
        ]
    }
}
```


#### Deleting a submission
To delete a submission use the `deleteSubmission` mutation, which requires the `id` of the submission that must be deleted. It returns a boolean value as the result to indicate whether the operation was successful.

```graphql
// Query to delete a submission with ID of `1110` for a site with an ID of `2`.
mutation deleteSubmission {
    deleteSubmission(id:1110 siteId:2)
}
```

With the resulting output:

```json
{
    "data": {
        "deleteSubmission": true
    }
}
```


#### Validation
If a mutation triggers a validation error, you'll get a response back, similar to the below. Here, the example shows the user didn't provide an email address, for the `emailAddress` field, despite it being required. The `message` will always be a JSON-encoded response of errors.

```json
{
    "errors": [
        {
            "message": "{\"emailAddress\":[\"Email Address cannot be blank.\"]}",
            "extensions": {
                "category": "graphql"
            }
        }
    ],
    "data": {
        "save_contactForm_Submission": null
    }
}
```

#### Captchas
You'll likely want to implement some form of captcha on the front-end for your headless forms. We would recommend either [reCAPTCHA](https://www.google.com/recaptcha/about/) or [hCaptcha](https://www.hcaptcha.com/), as other captchas require a bit more work. Refer to our [Headless Demo](https://github.com/verbb/formie-headless) for more information on the specifics of this, primarily to deal with CORS, and cross-site cookies.

You can add the following to your GQL form query to fetch tokens generated server-side.

```graphql
{
    formieForm (handle: "contactForm") {
        ...

        captchas {
            handle
            name
            value
        }
    }
}
```

Here, you'll need 3 vital bits of information, which is the `handle` of the Captcha integration, the `name` of the session variable used to compare the tokens between client and server, and the `value` of the token.

To authenticate your enabled Captchas correctly, you'll need to include these in your mutation, sent to the server.

```graphql
// Query
mutation saveSubmission($yourName:contactForm_yourName_FormieNameInput $javascriptCaptcha: FormieCaptchaInput) {
    save_contactForm_Submission(yourName: $yourName, javascriptCaptcha: $javascriptCaptcha) {
        title
    }
}

// Query Variables
{
    "yourName": {
        "firstName": "Peter",
        "lastName": "Sherman"
    },
    "javascriptCaptcha": {
        "name": "__JSCHK_8403842",
        "value": "1234"
    }
}
```

Here, we've included an additional parameter that includes the handle, name and value of the captcha in our mutation.

For an example with reCAPTCHA, refer to our [Headless Demo docs](https://github.com/verbb/formie-headless).
