Skip to main content

Connector Data

Connector data represents the knowledge base documents attached to an assessment - the data sources candidates can search during the task. Documents can be marked as signal (useful) or left as noise (distractors) to test candidate discernment.

List Available Connectors

Returns the available connector manifests for a given assessment (based on its connector configuration).
assessmentId
string
required
The assessment to list connectors for
Each item is the assessment’s stored ConnectorConfig. Note id is the connector’s own identifier; the type field is what holds the connector kind (e.g. "enterprise_search"). source is "builtin" for the packaged fakes or "mcp" for a real MCP server; MCP entries also carry mcpServerUrl/mcpTransport.

List Connector Data


Get Connector Data Item

Returns the full connector data record including file contents.

Create Connector Data

connectorType
string
required
Connector type (e.g. enterprise_search, company_wiki, market_data, crm_data)
name
string
required
Display name for the data source
description
string
Description of the data source
dataFiles
array
Array of file objects with title, content, and optional metadata. (A legacy name key is still read as a fallback, but title is canonical.)
isSignal
boolean
default:"false"
Whether this is a signal document (useful for the task)

Upload Connector Data File

Document upload into connectors is currently disabled (CONNECTOR_DOC_UPLOAD_ENABLED = false). Every call returns 403 { "error": { "code": "forbidden", "message": "Document upload into connectors is temporarily disabled." } }. Use POST /api/assessments/:id/connector-data with inline dataFiles instead. The behavior below describes the endpoint when re-enabled.
Upload a real document (.docx, .pptx, .xlsx, .csv, or .pdf) into a connector. The file is dual-stored: the real bytes go to the private documents Storage bucket, and its extracted plain text is saved to data_files[].content for search. Two targeting modes:
  • Pass connectorId to append the file to an existing connector’s file list.
  • Omit connectorId and pass connectorType (+ optional connectorName) to create a new connector row with this as its first file.
Request: multipart/form-data
file
file
required
The file to upload (.docx, .pptx, .xlsx, .csv, .pdf)
connectorId
string
Existing connector row id to append this file to
connectorType
string
Connector type for a new connector row (required if connectorId is not given)
connectorName
string
Display name for a new connector row (defaults to the filename)
isSignal
string
"true" or "false"

Delete File From Connector

Removes a single file from a connector’s file list (and its real file in Storage, if any). If this was the connector’s last file, the whole connector row is deleted too.

Rename / Toggle Signal on a File

Renames a single file and/or flips its signal/noise flag in place, inside a connector’s file list (a connector row can hold several real files — this addresses one of them without touching the rest).
title
string
New file title
isSignal
boolean
Updated signal flag for this file

Update Connector Data

name
string
Updated name
description
string
Updated description
isSignal
boolean
Updated signal flag

Delete Connector Data