---
title: "CDA | Global Fields"
description: "<p>A <a href=\"/docs/developers/global-field\">Global</a> field is a reusable field (or group of fields) that you can define once and reuse across multiple content types within your stack. This eliminates the need to recreate the same set of fields multiple times, saving effort and ensuring consistency.</p><p>You can pass the <strong>branch header</strong> in API requests to fetch or manage modules within specific branches of the stack. Additionally, setting the include_branch query parameter to true includes the _branch key in the response, specifying the unique ID of the branch where the module resides.</p><p><strong>Additional Resource</strong>: You can create dynamic and flexible Global Fields by nesting Global fields within a <a href=\"/docs/developers/global-field/global-fields-as-blocks-within-modular-blocks\">Modular Block,</a><a href=\"/docs/developers/global-field/about-global-field/\">Global</a><strong>, </strong>or a <a href=\"/docs/developers/global-field/group-fields-within-global-fields\">Group</a> fields.</p>"
url: "https://www.contentstack.com/docs/developers/apis/content-delivery-api/global-fields"
product: "Contentstack"
doc_type: "guide"
audience:
  - developers
  - admins
version: "current"
last_updated: "2026-06-02"
---

# CDA | Global Fields

A [Global](/docs/developers/global-field) field is a reusable field (or group of fields) that you can define once and reuse across multiple content types within your stack. This eliminates the need to recreate the same set of fields multiple times, saving effort and ensuring consistency.

You can pass the **branch header** in API requests to fetch or manage modules within specific branches of the stack. Additionally, setting the include\_branch query parameter to true includes the \_branch key in the response, specifying the unique ID of the branch where the module resides.

**Additional Resource**: You can create dynamic and flexible Global Fields by nesting Global fields within a [Modular Block,](/docs/developers/global-field/global-fields-as-blocks-within-modular-blocks)[Global](/docs/developers/global-field/about-global-field/)**,** or a [Group](/docs/developers/global-field/group-fields-within-global-fields) fields.

## All Global Fields

### Get all global fields

**GET** `/global_fields`

The Get all global fields request returns comprehensive information of all the global fields available in a particular stack in your organization. If you have nested global fields, it appears in the response.

**Note**:

*   Information about Global fields can be retrieved by all users, regardless of their role or access level.
*   If your Global field contains [nested Global fields](/docs/developers/global-field/about-global-field#nested-global-fields), they will appear as part of the schema in the API response.

#### Query Parameters

- **include_global_field_schema** (optional)
  Set this parameter to 'true' to include in response the schema of the Global field.
- **include_branch** (optional)
  Set this to 'true' to include the '\_branch' top-level key in the response. This key states the unique ID of the branch where the Global field resides.

#### Headers

- **api_key** (required)
  Enter the API key of your stack.
  Default: `your_api_key`
- **access_token** (required)
  Enter the environment-specific delivery token of your stack. Refer to the [Authentication](#authentication) section for more details.
  Default: `your_delivery_token`
- **branch** (optional)
  Enter your branch unique ID.
  Default: `main`

#### Sample Response

```json
{
    "global_fields": [
        {
            "created_at": "2019-09-06T11:30:02.108Z",
            "updated_at": "2019-09-06T11:30:02.108Z",
            "title": "Servlet",
            "uid": "servlet",
            "_version": 1,
            "inbuilt_class": false,
            "schema": [
                {
                    "display_name": "Name",
                    "uid": "name",
                    "data_type": "text",
                    "multiple": false,
                    "mandatory": false,
                    "unique": false,
                    "non_localizable": false
                },
                {
                    "data_type": "text",
                    "display_name": "Rich text editor",
                    "uid": "description",
                    "field_metadata": {
                        "allow_rich_text": true,
                        "description": "",
                        "multiline": false,
                        "rich_text_type": "advanced",
                        "options": [],
                        "version": 3
                    },
                    "multiple": false,
                    "mandatory": false,
                    "unique": false,
                    "non_localizable": false
                }
            ],
            "last_activity": {},
            "maintain_revisions": true,
            "description": ""
        }
    ]
}
```

## Single Global Field

### Get a single global field

**GET** `/global_fields/{global_field_uid}`

The Get a single global field request allows you to fetch comprehensive details of a specific global field.

When executing the API call, in the 'URL Parameters' section, provide the unique ID of your global field.

**Note**:

*   Information about Global fields can be retrieved by all users, regardless of their role or access level.
*   If your Global field contains [nested Global fields](/docs/developers/global-field/about-global-field#nested-global-fields), they will appear as part of the schema in the API response.

#### URL Parameters

- **global_field_uid** (required)
  Enter the unique ID of the global field that you wish to update. The UID is generated based on the title of the global field. The unique ID of a global field is unique across a stack.

#### Query Parameters

- **include_global_field_schema** (optional)
  Set this parameter to 'true' to include in response the schema of the Global field.
- **include_branch** (optional)
  Set this to 'true' to include the '\_branch' top-level key in the response. This key states the unique ID of the branch where the Global field resides.

#### Headers

- **api_key** (required)
  Enter the API key of your stack.
  Default: `your_api_key`
- **access_token** (required)
  Enter the environment-specific delivery token of your stack. Refer to the [Authentication](#authentication) section for more details.
  Default: `your_delivery_token`
- **branch** (optional)
  Enter your branch unique ID.
  Default: `main`

#### Sample Response

```json
{
    "global_field": {
        "created_at": "2019-09-06T11:30:02.108Z",
        "updated_at": "2019-09-06T11:30:02.108Z",
        "title": "Servlet",
        "uid": "servlet",
        "_version": 1,
        "inbuilt_class": false,
        "schema": [
            {
                "display_name": "Name",
                "uid": "name",
                "data_type": "text",
                "multiple": false,
                "mandatory": false,
                "unique": false,
                "non_localizable": false
            },
            {
                "data_type": "text",
                "display_name": "Rich text editor",
                "uid": "description",
                "field_metadata": {
                    "allow_rich_text": true,
                    "description": "",
                    "multiline": false,
                    "rich_text_type": "advanced",
                    "options": [],
                    "version": 3
                },
                "multiple": false,
                "mandatory": false,
                "unique": false,
                "non_localizable": false
            }
        ],
        "last_activity": {},
        "maintain_revisions": true,
        "description": ""
    }
}
```