> ## Documentation Index > Fetch the complete documentation index at: https://docs.clarifeye.ai/llms.txt > Use this file to discover all available pages before exploring further. # Artifacts shown beside an interview > The knowledge-store artifacts the interview's draft chose to show its respondent, read-only, at the latest versions the interviewer's prompt reads (CLA-1931). Readable by the respondent (interview-only access is enough) and by data readers. Only the selected artifacts marked `show_to_respondent`. Empty when none are, when the draft chose none, for interviews sent before the selection existed and for onboarding — none of these show an artifact panel. ## OpenAPI ````yaml /api-reference/openapi-public.yaml get /projects/{project_id}/interviews/{interview_id}/artifacts/ openapi: 3.0.3 info: title: Clarifeye Platform API — Public API description: > Forward-facing, supported REST API for new integrators of the Clarifeye Platform. Covers the curated public surface: authentication, knowledge management (documents), users & teams, signals, and tool execution. New integrations should target these endpoints. ## Authentication All endpoints require authentication. Include the Authorization header in every request using either format: - `Authorization: Token ` - `Authorization: Bearer ` ## Service accounts and API keys Integrations authenticate with an **API key** of a **service account**: - `Authorization: Bearer ` (keys start with `cfk_`) A service account is an ordinary member (role `member`) of one organization that cannot log in. Organization admins create it and mint its keys on the organization's *Service accounts* page, and give it access to knowledge stores with ordinary store permissions. A key is valid on every endpoint and acts as its service account: it reaches exactly the stores, with exactly the rights, the account was given. An account can hold several keys (each with its own name, optional expiry and revocation), so a key can be rotated without changing identity. A refused key answers **403** with one of: `Invalid API key.`, `API key revoked.`, `API key expired.`, `API key disabled.` (the service account is disabled). version: 1.0.0 contact: name: Clarifeye Support servers: - url: https://eu.app.clarifeye.ai/api/v1 description: EU - url: https://us.app.clarifeye.ai/api/v1 description: US security: - BearerAuth: [] - TokenAuth: [] tags: - name: Users description: Manage users within a project - name: Invitations description: Manage project invitations - name: Documents description: Manage documents within a project - name: Signals description: Submit signals about the project's content for domain experts to review - name: Tools description: Execute configured AI tools with custom parameters - name: Interviews description: >- Assign, run and review structured interview conversations, and manage interview drafts and campaigns - name: Artifacts description: > Knowledge-store artifact catalog: list artifacts, create and edit custom artifacts, manage scope membership, read and publish versions, and configure the cohesion guide. - name: Knowledge Changelog description: Chronological log of changes to the knowledge store's artifacts. paths: /projects/{project_id}/interviews/{interview_id}/artifacts/: get: tags: - Interviews summary: Artifacts shown beside an interview description: > The knowledge-store artifacts the interview's draft chose to show its respondent, read-only, at the latest versions the interviewer's prompt reads (CLA-1931). Readable by the respondent (interview-only access is enough) and by data readers. Only the selected artifacts marked `show_to_respondent`. Empty when none are, when the draft chose none, for interviews sent before the selection existed and for onboarding — none of these show an artifact panel. operationId: listInterviewArtifacts parameters: - $ref: '#/components/parameters/ProjectId' - name: interview_id in: path required: true description: UUID of the interview schema: type: string format: uuid responses: '200': description: The artifacts, in catalog order content: application/json: schema: type: array items: allOf: - $ref: '#/components/schemas/ArtifactSummary' - type: object properties: payload: description: >- The artifact content (head version), shaped by its technical_type. '404': description: Not found, or not an interview the caller can open. components: parameters: ProjectId: name: project_id in: path required: true description: UUID of the project schema: type: string format: uuid schemas: ArtifactSummary: type: object properties: id: type: string format: uuid slug: type: string title: type: string semantic_type: $ref: '#/components/schemas/ArtifactSemanticType' technical_type: $ref: '#/components/schemas/ArtifactTechnicalType' in_scope: type: boolean display_order: type: integer group: type: string description: > Catalog group label; empty for predefined artifacts (their section derives from `semantic_type`) and for ungrouped custom ones. "Foundation" and "Other" are reserved for UI-derived sections and cannot be set; the four standard section names ("Project Management", …) are NOT reserved — a custom artifact may use one to file itself alongside the predefined artifacts. definition_short: type: string head_version_number: type: integer nullable: true head_updated_at: type: string format: date-time nullable: true version_count: type: integer can_delete: type: boolean ArtifactSemanticType: type: string description: | What the artifact means in the knowledge store. Predefined types are seeded by the platform; `custom` artifacts are user-created. enum: - brief - project_plan - mental_map - general_knowledge - playbooks - library_description - design_templates - custom ArtifactTechnicalType: type: string description: | Storage/editing format of the artifact's payload — string for `markdown` and `bpmn_xml`, object for `mental_map`, array for `playbook_list` and `design_template_list`. enum: - markdown - mental_map - playbook_list - design_template_list - bpmn_xml securitySchemes: BearerAuth: type: http scheme: bearer description: > Use `Authorization: Bearer `. The token is either a user token / OAuth access token, or a service-account API key (`cfk_...`). A key is valid on every endpoint and acts as its service account, an organization member with per-store permissions. Refused keys answer 403 with `Invalid API key.`, `API key revoked.`, `API key expired.` or `API key disabled.`. TokenAuth: type: apiKey in: header name: Authorization description: 'Use Authorization: Token ' ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.