List all knowledge base entries
Beta
Returns a list of all knowledge base entries belonging to a replica. This endpoint allows you to view all your training data in one place, with optional filtering by status or type. You can use this to monitor the overall state of a replica's knowledge base, check which entries are still processing, and identify any that might have encountered errors. The response includes detailed information about each entry including its content, status, and metadata.
Query parameters
-
Filter knowledge base entries by comma separated list of their processing statuses. Use this to find entries in specific states like
NEW
orREADY
.Values are
NEW
,FILE_UPLOADED
,RAW_TEXT
,PROCESSED_TEXT
,VECTOR_CREATED
,READY
, orUNPROCESSABLE
. -
Filter knowledge base entries by their content type. Use this to find specific types of training data like text or file uploads.
Values are
file
,text
,website
, oryoutube
. -
Filter knowledge base entries by their title, filename, or URL.
Minimum length is
3
. -
Filter knowledge base entries that have encountered errors during processing.
Values are
true
orfalse
. -
Page number for pagination. Use this to navigate through large result sets.
Default value is
1
. -
Maximum number of entries to return per page (up to 100). Use this to control result set size. A value of zero can be used to check the total number of items without returning any items.
Minimum value is
0
, maximum value is100
. Default value is24
. -
Sort criteria.
Value is
createdAt
. Default value iscreatedAt
. -
The order of the sort.
Values are
asc
ordesc
. Default value isdesc
.
curl \
--request GET 'https://api.sensay.io/v1/replicas/03db5651-cb61-4bdf-9ef0-89561f7c9c53/knowledge-base' \
--header "X-API-Version: 2025-03-25"
{
"success": true,
"items": [
{
"id": 12345,
"type": "text",
"title": "Company information",
"status": "READY",
"summary": "Basic company details and policies",
"createdAt": "2025-04-15T08:11:00.093761+00:00",
"updatedAt": "2025-04-15T08:11:05.299349+00:00",
"replicaUUID": "03db5651-cb61-4bdf-9ef0-89561f7c9c53"
}
],
"total": 100
}
{
"error": "A text representation of the error",
"success": false,
"request_id": "xyz1::reg1:reg1::ab3c4-1234567890123-0123456789ab",
"fingerprint": "14fceadd84e74ec499afe9b0f7952d6b"
}
{
"error": "A text representation of the error",
"success": false,
"request_id": "xyz1::reg1:reg1::ab3c4-1234567890123-0123456789ab",
"fingerprint": "14fceadd84e74ec499afe9b0f7952d6b"
}
{
"error": "A text representation of the error",
"success": false,
"request_id": "xyz1::reg1:reg1::ab3c4-1234567890123-0123456789ab"
}
{
"error": "A text representation of the error",
"success": false,
"request_id": "xyz1::reg1:reg1::ab3c4-1234567890123-0123456789ab",
"fingerprint": "14fceadd84e74ec499afe9b0f7952d6b"
}
{
"error": "A text representation of the error",
"success": false,
"request_id": "xyz1::reg1:reg1::ab3c4-1234567890123-0123456789ab",
"fingerprint": "14fceadd84e74ec499afe9b0f7952d6b",
"inner_exception": {
"name": "Server overheated",
"cause": "Request too complicated",
"stack": "Error: Server overheated due to an unexpected situation\n at Object.eval (eval at <anonymous>...",
"message": "The server overheated due to an unexpected situation"
}
}