---
title: "Create a schema"
method: POST
path: "/v1/schemas"
tags: ["Schemas"]
---

# Create a schema

`POST /v1/schemas`

## Request

- Base URL: `https://api.talonic.com`
- URL: `https://api.talonic.com/v1/schemas`
- Auth: HTTP bearer

Create a reusable extraction schema. Provide a `name` and optionally a
JSON Schema `definition` with `properties` describing the fields to extract.

## Request body

- SchemaCreateRequest
  - `name` string, required: Schema name.
  - `description` string, nullable: Optional description.
  - `definition` object: JSON Schema definition. If provided, `properties` describes the fields. Each property key is the field name; the value is an object with `type`, optional `title`, and optional `description`.
    - `properties` object
    - `required` string[]
  - `fields` object[]: Flat fields array (alternative to `definition.properties`). Each element has at minimum a `field_name`; other attributes are optional.
    - `field_name` string, required
    - `display_name` string
    - `data_type` string: Field type hint. Accepted values: string, number, integer, boolean, date, array, object. Defaults to string. Extracted values are returned as the specified type when possible.
    - `description` string
    - `is_required` boolean

## Response `201`

Schema created.

- SchemaResponse
  - `id` string, uuid, required
  - `short_id` string: Short form of `id` (`SCH-` + the first 8 hex characters, uppercased). Accepted wherever `{id}` is.
  - `spec_id` string, uuid, nullable: The Spec that authors this schema, or `null` when the schema was created directly (via `POST /v1/schemas` or the legacy editor). This is the id in the Spec editor URL (`/specs/{spec_id}`) and is a DIFFERENT id from the schema `id` above — a Spec is materialized onto a schema, it is not the same record. Use this to cross between the two.
  - `spec_version` integer, nullable: The Spec's published head version — the number shown in the Spec editor. `null` when `spec_id` is `null`, or when the Spec has never been published. Not the same counter as `version` below.
  - `spec_materialized_version` integer, nullable: The Spec version whose configuration is live on this schema — what a run of it actually executes. Normally equal to `spec_version`; it lags when a publish was refused by the acknowledgement gate or a stale activation no-opped. `null` when `spec_id` is `null`.
  - `name` string, required
  - `description` string, nullable
  - `definition` object, required: JSON Schema definition of the extraction target.
    - `type` string
    - `properties` object
    - `required` string[]
  - `field_count` integer
  - `version` integer: Legacy schema-version counter, advanced by the version endpoints (`/v1/schemas/{id}/versions`). A Spec-authored schema never advances it — read `spec_version` for those.
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `links` object
    - `self` string
    - `extractions` string
    - `dashboard` string, uri

## Other responses

- `400`: The request is invalid.
- `401`: Missing or invalid API key.
- `403`: The API key does not have the required scope.
- `429`: Daily rate limit exceeded.

---

[API](https://skmtc.dev/talonic/apis/talonic-api.md) · [All operations](https://skmtc.dev/talonic/apis/talonic-api/llms.txt) · [OpenAPI document](https://skmtc.dev/talonic/apis/talonic-api/revisions/678fe5f8c9c3?raw)