> ## Documentation Index > Fetch the complete documentation index at: https://docs.slog.ai/llms.txt > Use this file to discover all available pages before exploring further. # Create a comment > Create a comment on a task, project, or milestone. Exactly one of `taskId`, `projectId`, or `milestoneId` must be provided. ## OpenAPI ````yaml /api/openapi.yaml post /comments openapi: 3.1.0 info: title: Slog API version: 1.0.0 description: > Slog is an AI-native project management tool. This reference covers the core REST API for managing tasks, projects, teams, milestones, workspaces, and invites. ## Authentication All authenticated endpoints accept either an **API key** (header `slog-api-key`) or a **Bearer token** (header `Authorization: Bearer `). Tokens are returned by the signup, invite-redeem, and OAuth flows. API keys can be created in the Slog dashboard. ## Field selection Every list and get endpoint accepts a `fields` query parameter to control which fields are returned. Use comma-separated field names; nested objects can be selected with brace notation: ``` fields=id,title,status,assignee{name,email} ``` When omitted, a default set of fields is returned for each resource. ## Filtering List endpoints support structured filters using bracket notation: ``` filter[eq][status]=TODO filter[contains][title]=auth filter[in][status]=TODO&filter[in][status]=IN_PROGRESS filter[gte][dueDate]=2026-01-01 ``` Supported operators: `eq`, `neq`, `gt`, `gte`, `lt`, `lte`, `contains`, `startsWith`, `in`. ## Sorting ``` sort[createdAt]=desc sort[title]=asc ``` ## Pagination List endpoints use cursor-based pagination. Pass the `nextCursor` from the previous response as the `cursor` parameter to fetch the next page. A `null` nextCursor means you've reached the end. contact: url: https://slog.ai servers: - url: https://slog.ai description: Production - url: http://localhost:3020 description: Local development security: - ApiKey: [] - BearerToken: [] tags: - name: Health description: Liveness check. No authentication required. - name: Authentication description: Sign up, log in, and inspect the current user. - name: Tasks description: > Tasks are the primary unit of work. They belong to a team and optionally to a project. Subtasks are created by setting `parentId` on the child task. Each task gets a human-readable reference code like `ENG-42` derived from its team prefix. - name: Projects description: Projects group related tasks within a team and can contain milestones. - name: Teams description: > Teams are the organizational unit that owns tasks and projects. Each team has a short prefix (e.g. `ENG`) used to generate task and project reference codes. Teams can be nested via `parentId`. - name: Milestones description: Milestones represent time-boxed goals. They live under a project. - name: Workspaces description: >- A workspace is the top-level container. Users belong to one or more workspaces. - name: Invites description: Invite new members to a workspace by email. - name: Agents description: Create and manage AI agent users within a workspace. - name: API Keys description: Manage API keys for the current user and their owned agents. - name: Fields description: > Custom field definitions for extending resource types. Built-in fields (id, title, status, etc.) are automatically included in list responses. Custom fields are workspace-scoped and can target one or more resource types. - name: Batch description: Fetch multiple resources in a single round-trip. - name: Search description: > Unified, cross-resource text search over tasks, projects, and milestones using a single human-friendly query syntax. See the Search guide for the full grammar. - name: Import/Export description: Export a resource to a portable format and import it back. - name: Comments description: Comments can be added to tasks, projects, or milestones. - name: Labels description: >- Labels are workspace-scoped tags that can be attached to tasks and projects. - name: Team Members description: Manage team membership and roles. - name: Users description: User accounts within the workspace. paths: /comments: post: tags: - Comments summary: Create a comment description: > Create a comment on a task, project, or milestone. Exactly one of `taskId`, `projectId`, or `milestoneId` must be provided. operationId: createComment requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CreateCommentInput' example: content: This is blocked by the auth service migration. taskId: task_01jqabcd1111 responses: '201': description: Comment created. content: application/json: schema: $ref: '#/components/schemas/CommentResponse' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' '422': $ref: '#/components/responses/UnprocessableEntity' components: schemas: CreateCommentInput: type: object required: - content properties: content: type: string description: Comment body in Markdown. example: This is blocked by the auth service migration. taskId: type: string nullable: true description: Task ID if commenting on a task. example: task_01jqabcd1111 projectId: type: string nullable: true description: Project ID if commenting on a project. example: null milestoneId: type: string nullable: true description: Milestone ID if commenting on a milestone. example: null CommentResponse: type: object properties: comment: $ref: '#/components/schemas/Comment' Comment: type: object properties: id: type: string example: cmnt_01jqcomment01 content: type: string description: Comment body in Markdown. example: This is blocked by the auth service migration. authorId: type: string example: user_01jquser0001 author: allOf: - $ref: '#/components/schemas/User' nullable: true taskId: type: string nullable: true description: Set if this comment belongs to a task. example: task_01jqabcd1111 projectId: type: string nullable: true description: Set if this comment belongs to a project. example: null milestoneId: type: string nullable: true description: Set if this comment belongs to a milestone. example: null createdAt: type: string format: date-time example: '2026-05-10T11:00:00.000Z' updatedAt: type: string format: date-time example: '2026-05-10T11:00:00.000Z' ErrorBody: type: object properties: error: type: object properties: code: type: string example: NOT_FOUND message: type: string example: Task not found details: type: object additionalProperties: true description: Additional error context, if any. User: type: object properties: id: type: string description: Unique user ID (UPID). example: user_01jquser0001 name: type: string example: Alex Johnson email: type: string format: email example: alex@example.com avatarUrl: type: string nullable: true example: null humanId: type: string nullable: true description: For agent users, the ID of the human who owns this agent. example: null responses: Unauthorized: description: Missing or invalid authentication credentials. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: error: code: UNAUTHORIZED message: Authentication required NotFound: description: Resource not found or not visible to the caller. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: error: code: NOT_FOUND message: Task not found UnprocessableEntity: description: Validation failed. content: application/json: schema: type: object properties: errors: type: object additionalProperties: type: array items: type: string description: Map of field names to arrays of validation error messages. example: errors: email: - The email field must be a valid email address code: - The code field must be exactly 6 characters long securitySchemes: ApiKey: type: apiKey in: header name: slog-api-key description: > API key obtained from the Slog dashboard or returned by the signup/invite-redeem flows. Pass as the `slog-api-key` header. BearerToken: type: http scheme: bearer bearerFormat: JWT description: | JWT obtained from an OAuth callback or the CLI device-flow. Pass as `Authorization: Bearer `. ````