> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Update Contact Custom Attributes > Update one or more custom attribute values for a specific contact. ## OpenAPI ````yaml PATCH /v1/contacts/{id}/custom-attributes openapi: 3.0.0 info: title: Conduit API version: 1.0.0 description: Public API for Conduit. servers: - url: https://api.conduit.ai description: Production security: [] tags: - name: meta description: Discovery and API metadata endpoints. - name: agents description: >- V2 chat agent configuration, including instructions, skills, triggers, and automation behavior. - name: contacts description: >- Contact profile and contact-scoped related resources such as tickets and calls. - name: workspaces description: Workspaces accessible to the current API token. - name: escalations description: >- Chat escalations that require operator review, including message, proposed response, and disposition context when available. - name: conversations description: >- Canonical message threads. Use these endpoints to list threads, inspect conversation state, read transcripts, and send replies. - name: conversation-tags description: >- Conversation labels, root topics, and subtopics used for classification and topic analytics. - name: tickets description: >- Operational queue items tied to conversations, including ticket-scoped transcripts and replies. - name: calls description: Phone call records, transcripts, summaries, and recordings when available. - name: reservations description: >- PMS reservations synced from the workspace's integrations (Hostaway, Guesty, Airbnb, etc.), including guest identity, payment status, and stay dates. - name: appointments description: >- Scheduled appointments (bookings) backed by the Conduit booking service. Exposes allocation context and the upstream booking-service `external_id`. - name: helpdesk_tickets description: >- Helpdesk tickets mirrored from external helpdesk integrations (Zendesk, Pylon, Plain), including requester identity and upstream metadata. - name: kb description: >- Knowledge base search and node management. Nodes represent knowledge base entries (files or directories), chunks are the indexed retrieval units used by search. - name: skills description: >- Workspace agent skills that can be attached to V2 chat agents. Sidebar/global-assistant skills are intentionally excluded. - name: custom_tools description: >- Custom code tools: user-authored Python/JavaScript functions executed in a sandbox when an agent calls them. Includes a runtimes endpoint describing the entrypoint signature, return shape, and available dependencies per language. - name: inbox_types description: >- Workspace inbox types. Each id is stable and usable as a message trigger's `inboxTypeId` and as the `inbox_type_id` filter on list conversations. paths: /v1/contacts/{id}/custom-attributes: patch: tags: - custom_attributes summary: Patch custom attributes for a contact description: >- Upserts one or more custom attribute values for a contact. Requires a token with write access. operationId: patchContactCustomAttributes parameters: - schema: type: string description: Contact id. example: ph77c0dy0mgdpzmqz6tesry8w184002s required: true name: id in: path - schema: type: string description: >- Optional workspace override. If omitted, Conduit resolves the contact's workspace automatically. example: j57demo8f8x7c9v0n2q4r6t8y1u3i5o required: false name: workspace_id in: query requestBody: required: true content: application/json: schema: type: object properties: attributes: type: array items: type: object properties: id: type: string value: anyOf: - type: string - type: number - type: boolean - nullable: true - type: array items: anyOf: - type: string - type: number - nullable: true required: - id - value minItems: 1 required: - attributes description: >- Request body for upserting custom attribute values on a contact. Date attributes accept YYYY-MM-DD strings. example: attributes: - id: attr_123 value: vip - id: attr_456 value: null responses: '200': description: Updated contact custom attributes content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string workspace_id: type: string name: type: string type: type: string options: type: array nullable: true items: type: object properties: value: type: string color: type: string required: - value - color order: type: number nullable: true section_id: type: string nullable: true section_name: type: string nullable: true value: anyOf: - type: string - type: number - type: boolean - nullable: true - type: array items: anyOf: - type: string - type: number - nullable: true required: - id - workspace_id - name - type - options - order - section_id - section_name - value required: - data description: Custom attributes for a contact. example: data: - id: attr_123 workspace_id: j57demo8f8x7c9v0n2q4r6t8y1u3i5o name: VIP Status type: Select options: - value: standard color: gray - value: vip color: green order: 1 section_id: section_123 section_name: Contact Info value: vip - id: attr_456 workspace_id: j57demo8f8x7c9v0n2q4r6t8y1u3i5o name: Move-in Date type: Date options: null order: 2 section_id: section_123 section_name: Contact Info value: null '400': description: Invalid request content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '404': description: Not found content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Token description: >- Conduit API token. Use `Authorization: Bearer `. Read/write endpoints require a token with write access. ````