API Reference / Knowledge - Artifacts

Create manual artifact

post https://api.intelig.ai/api/v1/intelig/knowledge/artifacts/manual

Auth: Authorization: ApiKey <key> (an API key sent as Bearer is rejected) or Authorization: Bearer <jwt> for a dashboard session. operationId: createManualArtifact

Creates a knowledge artifact manually (not from a webhook). Allows users to upload meeting notes or transcript text directly with an optional source URL and occurrence date.

Example request

curl -X POST "https://api.intelig.ai/api/v1/intelig/knowledge/artifacts/manual" \
  -H "Authorization: ApiKey $INTELIG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Weekly Engineering Standup",
    "transcriptText": "John: Let's discuss the roadmap...",
    "occurredAt": "2026-01-15T10:00:00Z",
    "sourceUrl": "https://zoom.us/rec/share/abc123"
  }'

Request body

application/json

FieldTypeRequiredDescription
title string no Title of the meeting or artifact (AI will generate if blank) Example: Weekly Engineering Standup
transcriptText string yes Full transcript text, may contain speaker labels Example: John: Let's discuss the roadmap...
occurredAt string (date-time) no When the meeting occurred (defaults to now if omitted) Example: 2026-01-15T10:00:00Z
sourceUrl string no Source URL of the meeting recording or document Example: https://zoom.us/rec/share/abc123

Response 201

application/json · ApiResponseLong

FieldTypeDescription
success boolean
message string
data integer (int64)

Status codes

  • 201 — Manual artifact created successfully
  • 400 — Invalid request body
  • 401 — Organization context not set
  • 403 — Insufficient permissions for Knowledge pillar
  • 429 — —

Every response is wrapped in { success, message, data }. A 4xx means the request is wrong — do not retry it unchanged. A 429 carries Retry-After in seconds.