How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Weaviate tokenize API

The tokenize API from Weaviate — 1 operation(s) for tokenize.

Weaviate tokenize API is one of 22 APIs that Weaviate publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tokenize. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 1 operation across 1 path, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.38.0-dev.

Requests are made against a single base URL, http://localhost:8080.

1 operations 1 paths 5 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.38.0-dev
Server
http://localhost:8080
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Weaviate tokenize API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API key authentication
  • BearerAuth — OIDC/JWT bearer authentication

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

tokenize 1
POST
/tokenize
Weaviate Tokenize Text
tokenize body → 200400401403422500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are TokenizeRequest (5 properties), TextAnalyzerConfig (3 properties), StopwordConfig (3 properties), TokenizeResponse (2 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
An error response returned by Weaviate endpoints.
1 property
TokenizeRequest
object
Request body for the generic tokenize endpoint.
5 properties 2 required
StopwordConfig
object
Fine-grained control over stopword list usage.
3 properties
TextAnalyzerConfig
object
Text analysis options for a property. These settings are immutable after the property is created. Applies only to text and text[] data types that use an invert…
3 properties
TokenizeResponse
object
Response from the tokenize endpoints. Returns indexed text and text used at query time
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weaviate-tokenize-api-openapi.yml Raw ↑

Other APIs Weaviate publishes across the network.

Weaviate authz API
Weaviate backups API
Weaviate batch API
Weaviate classifications API
Weaviate cluster API
Weaviate discovery API
Weaviate distributedTasks API
Weaviate export API
Weaviate graphql API
Weaviate mcp API
Weaviate meta API
Weaviate namespaces API
Where this information came from

This is an independent, third-party profile of Weaviate tokenize API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.