---
title: "Create a Feature and optionally associate with one or more event_schemas"
method: POST
path: "/features"
tags: ["Feature"]
---

# Create a Feature and optionally associate with one or more event_schemas

`POST /features`

Create a Feature optionally associate with one or more event_schemas

## Request body

- CreateFeatureRequest — Create a Feature stand-alone or associate it with schemas
  - `name` string, required — Name of the feature
  - `billableName` string — Billable name of feature. Billable name takes precedence over name to display in invoice.
  - `schemaAssociations` EventSchemasForFeature[], required — Association of a feature with event_schemas
    - `schemaName` string, required
    - `attributeName` string, required

## Response `200`

Response for Create and Get Feature requests

- Feature — Represents a Feature
  - `id` string, required
  - `name` string, required
  - `billableName` string
  - `displayName` string, required — Display name of feature. This is an auto-generated field which contains billableName of feature. If billableName is not provided, name will be used as display name.
  - `schemaAssociations` EventSchemasForFeature[], required — Association of a feature with event_schemas
    - `schemaName` string, required
    - `attributeName` string, required
  - `createdAt` string, date-time, required
  - `updatedAt` string, date-time

## Other responses

- `400` — Error response
- `401` — Error response
- `403` — Error response
- `404` — Error response
- `429` — Error response
- `default` — Error response

---

[API](https://skmtc.net/togaihq/apis/togai-apis.md) · [All operations](https://skmtc.net/togaihq/apis/togai-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/togaihq/togai-apis/revisions/442f5d8f4aa0/schema)