> ## Documentation Index > Fetch the complete documentation index at: https://developers.conveyour.com/llms.txt > Use this file to discover all available pages before exploring further. # Update a field > Updates an existing field. Changing a field's `name` after contacts have data stored under it is not recommended — existing contact data will no longer map to the new identifier. **A missing record does not return 404.** This handler reports the failure without a status code, and the error envelope defaults to HTTP `200` — you get `200` with `status: "failed"`. Branch on `status`, not on the HTTP code. ## OpenAPI ````yaml /api-reference/specs/fields.json put /api/fields/{id} openapi: 3.1.0 info: title: ConveYour API — Fields description: Create and manage custom contact fields for your org. version: 1.0.0 servers: - url: https://{subdomain}.conveyour.com description: Your organization's ConveYour instance variables: subdomain: default: acme description: >- Your organization's slug — the subdomain you sign in on. Replace `acme` with yours: if you sign in at `bigco.conveyour.com`, enter `bigco`. security: - conveyourToken: [] tags: - name: Fields description: Create and manage custom contact fields for your org. paths: /api/fields/{id}: put: tags: - Fields summary: Update a field description: >- Updates an existing field. Changing a field's `name` after contacts have data stored under it is not recommended — existing contact data will no longer map to the new identifier. **A missing record does not return 404.** This handler reports the failure without a status code, and the error envelope defaults to HTTP `200` — you get `200` with `status: "failed"`. Branch on `status`, not on the HTTP code. operationId: updateAField parameters: - name: id in: path required: true description: The id identifier. schema: type: string - $ref: '#/components/parameters/teams' requestBody: required: false content: application/json: schema: type: object properties: label: description: Updated human-readable label. type: string values: description: For `list` fields — updated array of allowed option values. type: array items: type: string responses: '200': description: Success. content: application/json: schema: allOf: - $ref: '#/components/schemas/Envelope' - type: object properties: data: $ref: '#/components/schemas/FieldRecord' example: status: ok message: Field updated data: id: FIELD_ID name: badge_number label: Employee Badge Number type: string '403': $ref: '#/components/responses/ForbiddenToken' components: parameters: teams: name: teams[] in: query description: >- Team scope for the request, as one or more team ObjectIds. The brackets are required: PHP keeps only the last value for a repeated plain key, so `teams=A&teams=B` silently resolves to B alone. On requests with a JSON body you may send `teams` (no brackets) in the body instead. **Values that are not valid ObjectIds are silently ignored** — a mistyped team ID behaves as if no team was sent. See the [teams section of the API conventions guide](/guides/api-conventions#team-scoping). style: form explode: true schema: type: array items: type: string example: - 64a1b2c3d4e5f6a7b8c9d0ff schemas: Envelope: type: object description: The common response envelope shared by all ConveYour endpoints. properties: status: type: string enum: - ok - failed description: '`ok` on success, `failed` on error.' message: type: string description: Human-readable description of the result. data: description: >- The response payload — an object or an array depending on the endpoint. FieldRecord: type: object description: >- A field record. Update returns this directly, so it does NOT carry the computed flags (`values`, `owned`, `field_editable`, `field_enabled`, `field_deletable`, `editable_type`, `form_hidden`) that the read endpoints add. properties: id: type: integer description: Field ID. name: type: string description: Machine name; the key this field appears under in a contact record. label: type: string description: Display label. type: type: string description: Field type, e.g. text, select, id_number, related_contacts. order: type: integer description: Display order within the bucket. section: type: string description: Section name. Null is returned as an empty string. active: type: boolean description: Whether the field is active. active_profile: type: boolean description: Whether it shows on the contact profile. editable: type: boolean description: Stored editable flag from the record. visible: type: boolean description: Whether the field is visible. parent_id: type: - integer - 'null' description: Parent field ID for sub-fields; null otherwise. iskey: type: boolean description: Whether the field is a key field. rep_visible: type: boolean description: Whether it is visible in rep views. default_value: type: string description: Default value. suffix: type: string description: Display suffix. is_event: type: boolean description: Whether the field records an event. is_property: type: boolean description: Whether the field is a property. values_enabled: type: boolean description: Whether the allowed-value list is enforced. format: type: string description: Display format. filters: type: array description: Contact filters. Present only when type is related_contacts. custom_object_id: type: string description: Present only when type is related_custom_object. custom_object_field: type: string description: Present only when type is related_custom_object. custom_object_field_map: type: object description: Present only when type is related_custom_object. responses: ForbiddenToken: description: >- The token is missing, expired, or not permitted for this HTTP method. **This endpoint enforces no named permission**, so a 403 here never carries a `permission` field. content: application/json: example: status: failed message: Token is either expired or does not have the correct permissions data: [] securitySchemes: conveyourToken: type: apiKey in: header name: x-conveyour-token description: >- Your API key token. Contacts endpoints require a **Server-only — Full API** key — see [Authentication](/quickstart). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.