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

# The record types whose forms and custom fields you may configure, with what may be done to each.

> Every record type with a form you arrange is listed, so the model's own columns on it can be moved,
withdrawn and insisted on. `honours_conditions` says whether they can also be frozen or asked only on
a condition: it is false for a record type that is created and corrected only through an operation
of its own, whose form reads neither setting. `accepts_new` says whether a custom field of your own
may be defined against it, which is only where an answer to one can be read back — on a register
that draws them, on an administration list, or on the screen where the work is done. It is false
where an answer of your own could not be read back on any register or list, which includes forms you
can arrange but not yet add to, and record types you already hold fields against but may not add
to.



## OpenAPI

````yaml /api-reference/openapi.json get /custom_field_entities
openapi: 3.0.0
info:
  description: ''
  title: >-
    The only schema PostgREST exposes. Reads are security_invoker views; writes
    are SECURITY DEFINER functions. Rebuilt wholesale on every deploy — it holds
    no data.
  version: 12.2.3
servers:
  - url: https://app.assetinfinity.ai/api
security: []
tags:
  - name: Signing in
  - name: Profile
  - name: Assets
  - name: Asset lifecycle
  - name: Work lifecycle
  - name: Maintenance
  - name: Inventory
  - name: Inventory detail
  - name: Procurement
  - name: Contracts
  - name: Workforce
  - name: Capacity
  - name: Dispatch
  - name: Tools
  - name: Inspections
  - name: Verification
  - name: Reliability
  - name: Parts demand
  - name: Sensors and meters
  - name: Map
  - name: Floor plans
  - name: Labels
  - name: Lost and found
  - name: Root cause analysis
  - name: Reports
  - name: Audit center
  - name: Activity
  - name: Notifications
  - name: Channels
  - name: Search
  - name: Copilot
  - name: Import
  - name: Files
  - name: Sync
  - name: Support
  - name: Admin
  - name: Access
  - name: Lookups
  - name: Read models
  - name: Branding
  - name: Custom fields
  - name: Form studio
  - name: Workflows
  - name: Workflow studio
  - name: Rules
  - name: Statuses and transitions
  - name: Currencies and locales
  - name: Work configuration
  - name: Asset configuration
  - name: Inventory configuration
  - name: Tool configuration
  - name: Workforce configuration
  - name: Vendor and contract configuration
  - name: Document configuration
  - name: Inspection configuration
  - name: Sites, locations and the organisation
  - name: Platform
  - name: Amendments
  - name: Asset clone
  - name: Asset components
  - name: Asset register
  - name: Asset transfer
  - name: Audit feed
  - name: Billing
  - name: Bookings
  - name: Budgets
  - name: Bulk jobs
  - name: Calibration history
  - name: Capex plans
  - name: Conversations
  - name: Costing
  - name: Currency
  - name: Dashboards
  - name: Data exports
  - name: Directory sync
  - name: Document control
  - name: Document folders
  - name: Document tree
  - name: Documents
  - name: Energy
  - name: Extracts
  - name: Features
  - name: Feeds
  - name: Ffe plans
  - name: File exchange
  - name: Filing exceptions
  - name: Finance
  - name: Inbound mail
  - name: Itam
  - name: Itam software
  - name: Itam topology
  - name: Keys
  - name: Knowledge
  - name: Licence
  - name: List views
  - name: Locations
  - name: Mapping
  - name: Mcp
  - name: Mcp oauth
  - name: Mfa
  - name: Numbering
  - name: Permits
  - name: Readers
  - name: Reference
  - name: Reference columns
  - name: Reference entry
  - name: Release
  - name: Scim
  - name: Security streams
  - name: Self verification
  - name: Setup
  - name: Shutdown
  - name: Sso
  - name: Telegram
  - name: Tenant switch
  - name: The caller's own work
  - name: The checklist library
  - name: Today
  - name: Tools on a job, and who has them out
  - name: Trackers
  - name: Tray
  - name: Vendor spend forecast
  - name: Vendors and contracts
  - name: Visitors
  - name: Webhooks
  - name: Work order execution
  - name: Work sequencing
  - name: Workforce detail
externalDocs:
  description: PostgREST Documentation
  url: https://postgrest.org/en/v12/references/api.html
paths:
  /custom_field_entities:
    get:
      tags:
        - Custom fields
      summary: >-
        The record types whose forms and custom fields you may configure, with
        what may be done to each.
      description: >-
        Every record type with a form you arrange is listed, so the model's own
        columns on it can be moved,

        withdrawn and insisted on. `honours_conditions` says whether they can
        also be frozen or asked only on

        a condition: it is false for a record type that is created and corrected
        only through an operation

        of its own, whose form reads neither setting. `accepts_new` says whether
        a custom field of your own

        may be defined against it, which is only where an answer to one can be
        read back — on a register

        that draws them, on an administration list, or on the screen where the
        work is done. It is false

        where an answer of your own could not be read back on any register or
        list, which includes forms you

        can arrange but not yet add to, and record types you already hold fields
        against but may not add

        to.
      parameters:
        - $ref: '#/components/parameters/rowFilter.custom_field_entities.entity'
        - $ref: '#/components/parameters/rowFilter.custom_field_entities.label'
        - $ref: '#/components/parameters/rowFilter.custom_field_entities.schema_name'
        - $ref: '#/components/parameters/rowFilter.custom_field_entities.table_name'
        - $ref: >-
            #/components/parameters/rowFilter.custom_field_entities.is_administered
        - $ref: '#/components/parameters/rowFilter.custom_field_entities.accepts_new'
        - $ref: >-
            #/components/parameters/rowFilter.custom_field_entities.honours_conditions
        - $ref: '#/components/parameters/select'
        - $ref: '#/components/parameters/order'
        - $ref: '#/components/parameters/range'
        - $ref: '#/components/parameters/rangeUnit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/preferCount'
      responses:
        '200':
          content:
            application/json:
              schema:
                items:
                  $ref: '#/components/schemas/custom_field_entities'
                type: array
            application/vnd.pgrst.object+json:
              schema:
                items:
                  $ref: '#/components/schemas/custom_field_entities'
                type: array
            application/vnd.pgrst.object+json;nulls=stripped:
              schema:
                items:
                  $ref: '#/components/schemas/custom_field_entities'
                type: array
            text/csv:
              schema:
                items:
                  $ref: '#/components/schemas/custom_field_entities'
                type: array
          description: OK
        '206':
          description: Partial Content
components:
  parameters:
    rowFilter.custom_field_entities.entity:
      in: query
      name: entity
      required: false
      schema:
        type: string
    rowFilter.custom_field_entities.label:
      in: query
      name: label
      required: false
      schema:
        type: string
    rowFilter.custom_field_entities.schema_name:
      in: query
      name: schema_name
      required: false
      schema:
        type: string
    rowFilter.custom_field_entities.table_name:
      in: query
      name: table_name
      required: false
      schema:
        type: string
    rowFilter.custom_field_entities.is_administered:
      in: query
      name: is_administered
      required: false
      schema:
        type: string
    rowFilter.custom_field_entities.accepts_new:
      in: query
      name: accepts_new
      required: false
      schema:
        type: string
    rowFilter.custom_field_entities.honours_conditions:
      in: query
      name: honours_conditions
      required: false
      schema:
        type: string
    select:
      description: Filtering Columns
      in: query
      name: select
      required: false
      schema:
        type: string
    order:
      description: Ordering
      in: query
      name: order
      required: false
      schema:
        type: string
    range:
      description: Limiting and Pagination
      in: header
      name: Range
      required: false
      schema:
        type: string
    rangeUnit:
      description: Limiting and Pagination
      in: header
      name: Range-Unit
      required: false
      schema:
        default: items
        type: string
    offset:
      description: Limiting and Pagination
      in: query
      name: offset
      required: false
      schema:
        type: string
    limit:
      description: Limiting and Pagination
      in: query
      name: limit
      required: false
      schema:
        type: string
    preferCount:
      description: Preference
      in: header
      name: Prefer
      required: false
      schema:
        enum:
          - count=none
        type: string
  schemas:
    custom_field_entities:
      description: >-
        The record types whose forms and custom fields you may configure, with
        what may be done to each.


        Every record type with a form you arrange is listed, so the model's own
        columns on it can be moved,

        withdrawn and insisted on. `honours_conditions` says whether they can
        also be frozen or asked only on

        a condition: it is false for a record type that is created and corrected
        only through an operation

        of its own, whose form reads neither setting. `accepts_new` says whether
        a custom field of your own

        may be defined against it, which is only where an answer to one can be
        read back — on a register

        that draws them, on an administration list, or on the screen where the
        work is done. It is false

        where an answer of your own could not be read back on any register or
        list, which includes forms you

        can arrange but not yet add to, and record types you already hold fields
        against but may not add

        to.
      properties:
        accepts_new:
          format: boolean
          type: boolean
        entity:
          format: character varying
          maxLength: 80
          type: string
        honours_conditions:
          format: boolean
          type: boolean
        is_administered:
          format: boolean
          type: boolean
        label:
          format: text
          type: string
        schema_name:
          format: character varying
          maxLength: 40
          type: string
        table_name:
          format: character varying
          maxLength: 60
          type: string
      type: object

````

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