Skip to main content
POST
/
api
/
kb
/
assets
Add an asset via URL
curl --request POST \
  --url https://{customer-tenant}.nuwacom.ai/api/kb/assets \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "spaceId": "<string>",
  "mimeType": "<string>",
  "url": "<string>",
  "connectorId": 123,
  "metadata": {},
  "path": [
    "<string>"
  ],
  "fetchAuth": {
    "type": "basic",
    "username": "<string>",
    "password": "<string>"
  },
  "name": "<string>"
}
'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
spaceId
required

Unique ID of the space the asset should be added to.

Required string length: 2 - 6
​
mimeType
string
required

MIME type of the remote asset (e.g., "application/pdf", "text/plain").

​
url
string<uri>
required

Reachable URL that the backend should fetch and ingest (can be signed or public).

​
connectorId
number

Identifier of the connector (e.g., SharePoint, Google Drive) the asset belongs to.

​
metadata
object

JSON metadata string that will be stored alongside the asset (e.g., author, custom tags).

​
path
string[]

Hierarchical path (array of folder names) describing where the asset lives in the connector.

​
fetchAuth
object
​
name
string

Optional display name for the asset. Defaults to the filename if omitted.

Response

Asset created successfully

​
id
string<uuid>
required