openapi: 3.1.0
info:
title: Kita Capture Applications Schemas API
version: v1
summary: Document intelligence — extract structured, validated, fraud-checked data from bank statements, payslips, IDs, credit reports and 30+ other document types.
description: 'Kita Capture turns scanned or photographed financial and identity documents into clean
JSON — transactions, metadata, metrics, and fraud signals. Upload a file (multipart or
base64), submit a URL, or batch up to 100 documents, then poll for results or receive an
HMAC-signed webhook.
Authentication uses an organization API key prefixed `kita_prod_` sent as
`Authorization: Bearer <key>`. Errors return `{ "error": ..., "message": ... }`.
Rate limiting is per organization; 429 responses carry a `Retry-After` header.
NOTE: Kita does not publish a machine-readable OpenAPI description. This document was
generated by the API Evangelist enrichment pipeline from Kita''s own published API
documentation (shipped verbatim inside the official `kita-docs-mcp` npm package and
served at https://www.kita.ai/documentation). Only operations, parameters, fields and
status codes that Kita documents are represented here.
'
contact:
name: Kita Support
email: support@kita.ai
url: https://www.kita.ai/documentation
x-source:
- https://www.kita.ai/documentation
- https://unpkg.com/kita-docs-mcp@0.4.0/docs/Documentation.md
x-generated-by: api-evangelist-enrichment-pipeline
x-generated: '2026-07-19'
servers:
- url: https://portal.usekita.com
description: Production (default; override with the KITA_API_URL environment variable)
security:
- BearerAuth: []
tags:
- name: Schemas
description: Custom extraction schemas.
paths:
/api/v1/schemas:
get:
tags:
- Schemas
operationId: listSchemas
summary: List custom extraction schemas
responses:
'200':
description: The schemas.
'401':
$ref: '#/components/responses/Unauthorized'
post:
tags:
- Schemas
operationId: createSchema
summary: Create a custom extraction schema
description: Enterprise organizations can define custom extraction shapes that override the default vocabulary output.
requestBody:
required: true
content:
application/json:
schema:
type: object
responses:
'200':
description: Schema created.
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
/api/v1/schemas/{schemaId}:
parameters:
- name: schemaId
in: path
required: true
schema:
type: string
get:
tags:
- Schemas
operationId: getSchema
summary: Fetch a single schema
responses:
'200':
description: The schema.
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
put:
tags:
- Schemas
operationId: updateSchema
summary: Update a schema
requestBody:
required: true
content:
application/json:
schema:
type: object
responses:
'200':
description: Updated.
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
delete:
tags:
- Schemas
operationId: deleteSchema
summary: Delete a schema
responses:
'200':
description: Deleted.
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
components:
responses:
Forbidden:
description: Upgrade required, or the document type is not enabled for this organization.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
NotFound:
description: Document or batch ID does not exist.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
BadRequest:
description: Bad request — check the request body and parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
example:
error: Bad Request
message: documents array is required and must not be empty
Unauthorized:
description: Invalid or missing API key.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
schemas:
Error:
type: object
properties:
error:
type: string
description: Short error label.
message:
type: string
description: Human-readable description.
securitySchemes:
BearerAuth:
type: http
scheme: bearer
description: 'Organization API key prefixed `kita_prod_`, issued from the Kita dashboard at
https://portal.usekita.com and sent as `Authorization: Bearer <key>`.
'