Affinda Document Types API
Manage document type definitions — the model configuration governing how a specific document category (invoice, resume, custom contract) is parsed. Each document type exposes a JSON Schema and optional Pydantic model representation. Document types are configured in the dashboard or natural-language workflow builder and reused across workspaces and collections.
Affinda Document Types API is one of 16 APIs that Affinda publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Document Processing, Document Types, Models, and Configuration. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.
This API exposes 7 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 3.0.0.
Requests are made against a single base URL, https://{region}.affinda.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Affinda Document Types API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (ApiKeyAuth).
By default, every request must be authenticated.
ApiKeyAuth— Basic authentication using an API key, e.g. {Authorization: Bearer aff0bb4fbdf97b7e4111ff6c0015471094155f91}. You can find your API key within the Settings pag…
Paths & Operations 7
Across 4 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are DocumentType (5 properties), DocumentTypeCreate (3 properties), RequestError (2 properties), DocumentTypeUpdate (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Affinda 12
Other APIs Affinda publishes across the network.