<!-- Generated from the canonical Teloring documentation source. Do not edit this file. -->

Canonical page: https://docs.teloring.com/api/list-conversation-attributes
Last modified: 2026-08-20T20:52:05.000Z

# Get the conversation-attribute schema

import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
import ParamsDetails from "@theme/ParamsDetails";
import RequestSchema from "@theme/RequestSchema";
import StatusCodes from "@theme/StatusCodes";
import OperationTabs from "@theme/OperationTabs";
import TabItem from "@theme/TabItem";
import Heading from "@theme/Heading";
import Translate from "@docusaurus/Translate";

<Heading
  as={"h1"}
  className={"openapi__heading"}
  children={"Get the conversation-attribute schema"}
>
</Heading>

<MethodEndpoint
  method={"get"}
  path={"/conversation-attributes"}
  context={"endpoint"}
>
  
</MethodEndpoint>



The account's conversation-attribute schema: the custom fields a conversation can
carry.

`api_id` is the key you use when writing values at
`PATCH /v1/conversations/{id}/custom-attributes`, and `type` decides what a value
may be — the write endpoint enforces it.

Read-only on purpose. This is a *schema*, and reshaping it from a machine
credential would silently invalidate values on conversations that already carry
them.

**Scope:** `conversation_attributes`

<ParamsDetails>
  
</ParamsDetails>

<RequestSchema
  {...require("./list-conversation-attributes.RequestSchema.json")}
>
  
</RequestSchema>

<StatusCodes
  {...require("./list-conversation-attributes.StatusCodes.json")}
>
  
</StatusCodes>
