curl --silent --show-error --fail-with-body --request POST \
--url 'https://response.stateset.com/api/v1/knowledge/search' \
--header "Authorization: Bearer $RESPONSECX_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"question": "string",
"top_k": 5
}'
{
"object": "list",
"data": [
{}
],
"has_more": true,
"next_cursor": "string"
}
Semantic search over the knowledge base
Matches
POST
/
api
/
v1
/
knowledge
/
search
curl --silent --show-error --fail-with-body --request POST \
--url 'https://response.stateset.com/api/v1/knowledge/search' \
--header "Authorization: Bearer $RESPONSECX_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"question": "string",
"top_k": 5
}'
{
"object": "list",
"data": [
{}
],
"has_more": true,
"next_cursor": "string"
}
Request body
object
string
required
Maximum length:
10000.integer
Default:
5. Minimum: 1. Maximum: 100.Response
object
string
Allowed values:
'list'.object[]
boolean
string
Keyset cursor for the next page — present only on cursor-capable lists with more rows.
Status codes
| Code | Meaning |
|---|---|
200 | Matches |
400 | Invalid request. issues names the offending field(s). |
401 | Missing, invalid, or expired API key. |
403 | The key lacks a required scope. |
429 | Rate limit exceeded. |
Access
| Required scope | knowledge:read |
| Rate limit | 10 requests per minute |
Using this contract
Read the source OpenAPI document for declared schemas and alternatives. This page also includes documented corrections from the spec overlays. Example IDs and values are illustrative; replace them with records from your workspace.curl --silent --show-error --fail-with-body --request POST \
--url 'https://response.stateset.com/api/v1/knowledge/search' \
--header "Authorization: Bearer $RESPONSECX_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"question": "string",
"top_k": 5
}'
{
"object": "list",
"data": [
{}
],
"has_more": true,
"next_cursor": "string"
}
Last modified on September 21, 2026