Define a Kustomer Klass (custom object schema) declaratively via the Apps Platform, distinct from kObject record CRUD
domain: developer.kustomer.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Understand the model: a Klass defines the schema for a custom object type, while individual kObjects are the data records created against that schema
Define a Klass declaratively in your app's JSON definition using the klasses property, specifying a unique alphanumeric/underscore/hyphen name, icon, and color
Define the Klass's attributes under metadata.properties, suffixing each property key by its type (e.g. Num, Str, At, Txt, Bool, Url)
Register/install the app so the Klass schema becomes available on the account
Once the schema exists, create and query kObject records against it using Kustomer's standard record endpoints, which is a separate step from schema definition
Known gotchas
Klass names must be unique per account and are restricted to alphanumeric characters, underscores, and hyphens
Attribute typing is encoded directly in the property key suffix (Num/Str/At/Txt/Bool/Url), not in a separate type field — getting the suffix wrong silently creates a differently-typed property
Schema definition (Klasses) and record CRUD (kObjects) are different layers with different creation paths — defining a Klass does not itself create any data records
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?