> ## Documentation Index
> Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add a custom field to a project template

> Makes a project or task custom field part of a project template, as adding it in the app's field dialog does: every project created from the template afterwards has it (a task's field in its task table), with no value until one is written. A field already in the template's task fields stays a task field there, and one in its project fields a project field. Projects already made from the template are unchanged. A template synced from another tool, or one the app cannot read, is a 409. An added field is shown in the app, internal for sharing unless the project's settings already share it. A removed one is recorded as removed, even when it was not there, so a value written later through the API does not show it until someone adds it back. A project or template another request is changing is a 409: try again. Adding a field that is there changes nothing. For one project, use PUT /v1/objects/project/records/{project_id}/fields/{field_key}.



## OpenAPI

````yaml /api/statisfy-api.openapi.json put /v1/project_templates/{template_id}/fields/{field_key}
openapi: 3.1.0
info:
  description: >-
    The agent-first Statisfy API. Authenticate with an API key (`Authorization:
    Bearer stfy_live_…`), then call `GET /v1/meta/capabilities` to discover
    every operation and its schemas.
  title: Statisfy API
  version: 1.0.0
servers:
  - url: https://api.statisfy.com
    description: Production
security: []
paths:
  /v1/project_templates/{template_id}/fields/{field_key}:
    put:
      tags:
        - projects
      summary: Add a custom field to a project template
      description: >-
        Makes a project or task custom field part of a project template, as
        adding it in the app's field dialog does: every project created from the
        template afterwards has it (a task's field in its task table), with no
        value until one is written. A field already in the template's task
        fields stays a task field there, and one in its project fields a project
        field. Projects already made from the template are unchanged. A template
        synced from another tool, or one the app cannot read, is a 409. An added
        field is shown in the app, internal for sharing unless the project's
        settings already share it. A removed one is recorded as removed, even
        when it was not there, so a value written later through the API does not
        show it until someone adds it back. A project or template another
        request is changing is a 409: try again. Adding a field that is there
        changes nothing. For one project, use PUT
        /v1/objects/project/records/{project_id}/fields/{field_key}.
      operationId: projects_add_template_field
      parameters:
        - in: path
          name: template_id
          required: true
          schema:
            type: string
        - description: >-
            The field's key (such as `arr__c_`), not its label (`Arr`). To find
            it: make_get_call with path `/v1/fields` and query `{"object":
            "project"}` lists each field's key beside its label; use the key
            whose label the person said. Call it directly; no need to look the
            operation up first
          in: path
          name: field_key
          required: true
          schema:
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TemplateField'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    TemplateField:
      properties:
        field:
          title: Field
          type: string
        object:
          anyOf:
            - enum:
                - project
                - task
              type: string
            - type: 'null'
          description: >-
            project: projects created from the template show the field; task:
            their task tables do. null only for a remove that found the field on
            neither, when it is attached both to projects and to tasks
          title: Object
        on_template:
          description: Whether the field is on the template after the call
          title: On Template
          type: boolean
        template:
          title: Template
          type: string
      required:
        - template
        - field
        - object
        - on_template
      title: TemplateField
      type: object
  securitySchemes:
    HTTPBearer:
      scheme: bearer
      type: http
      description: >-
        An API key, sent as `Authorization: Bearer stfy_live_…`. See
        [Authentication](/rest-api/authentication) for how to get one and which
        scopes it needs.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.