The dynamic-sentence chunker (chunking strategy) splits the provided text into sentences. Sentences are joined until they reach the maxChunkSize. If overlapSize is provided, adjacent chunks will both have overlapping sentences on the sides.
Bearer token used for authentication. Format: Authorization: Bearer ACCESS_TOKEN.
application/json
"application/json"
Unique identifier for the model.
"gte-small"
The batch of key:value pairs used in the chunking request.
Provides fields and values that specify ranges for tokens.
The dynamic-sentence chunker (chunking strategy) splits the provided text into sentences. Sentences are joined until they reach the maxChunkSize. If overlapSize is provided, adjacent chunks will both have overlapping sentences on the sides.
Example:
S1 S2 S3 -- -- S3 S4 S5 -- -- -- -- S5 S6 S7
This is the default chunker configuration if nothing is passed.
OK
This is the response to the POST chunking request submitted for a specific chunker and modelId.
The universal unique identifier (UUID) returned in the POST request. This UUID is required in the GET request to retrieve results.
"441eb3be-7de6-470a-8141-e416a15c7db1"
The current status of the request. Allowed values are:
SUBMITTED - The POST request was successful and the response has returned the chunkingId and status that is used by the GET request.
ERROR - An error was generated when the GET request was sent.
READY - The results associated with the chunkingId are available and ready to be retrieved.
RETRIEVED - The results associated with the chunkingId are returned successfully when the GET request was sent.
"SUBMITTED"