Create project

Array of time activity UUIDs that can be used when logging time in this project (e.g., Development, Testing, Management, Research). At least one activity must be specified. Use GET /administration/task-settings/activities to retrieve available activities.

UUID of the project category. Categories classify projects by functional area or project type (e.g., Onboarding, Support, Implementation). Use the GET /projects/categories endpoint to retrieve available categories.

Custom field values as key-value pairs. Keys should match custom field IDs configured in workspace settings. Values must match the field type (string, number, boolean, date, etc.). Use GET /administration/project-settings/custom-fields to retrieve available project custom fields and their configurations.

Project deadline date in ISO 8601 format (e.g., "2024-12-31T23:59:59.000Z"). Optional target completion date for the project.

UUID of the user who is accountable for the project by default. This user will be set as accountable on new tasks created in this project unless overridden. Use the GET /workspace/users endpoint to retrieve available users.

Accepts Markdown or HTML for complex formatting. This content is rendered by the Leadtime rich editor, not by a plain Markdown viewer. For quick/simple text, Markdown is acceptable. For polished user-facing content from an agent or integration, prefer structured HTML because it preserves editor blocks, links, and layout more predictably. Use only the nodes and marks documented below for this field. Supported editor features differ by endpoint and field. Choose formatting for readability, not decoration: use headings for real sections, paragraphs for narrative text, lists or tables for structured facts, blockquotes for quoted context, callouts for important outcomes/risks/notes when supported, and explicit anchors for links. Do not rely on bare URLs or Markdown links when the link must be clickable; use explicit anchors such as <a href="https://example.com" target="_blank" rel="noopener noreferrer nofollow">link text</a>. In HTML you can use: ## Node Types and Marks ### Nodes **paragraph** Type: block Content: inline* (inline only — do not use block tags such as <p> inside; use e.g. <br>, <strong>, <em>, <span>…) Default paragraph. extraPlaceholder is an internal structure for the editor to show a ghost placeholder in empty “template” lines (ProseMirror JSON fragment or null). For normal agent output leave extraPlaceholder as null. Only set it if you are intentionally mirroring a field placeholder the user already has in the open editor; do not set random placeholder data for free-form answers. Atts: - extraPlaceholder: null ```html <p class="paragraph-base" extraplaceholder="null/some-value"></p> ``` **heading** Type: block Content: inline* (inline only — do not use block tags such as <p> inside; use e.g. <br>, <strong>, <em>, <span>…) Atts: - level: 1 ```html <h1 class="heading-base"></h1> ``` **bulletList** Type: block list Content: listItem+ Atts: none ```html <ul class="list-base"><li></li></ul> ``` **hardBreak** Type: inline Atts: none ```html <br> ``` **horizontalRule** Type: block Atts: none ```html <hr class="hr-base"> ``` **orderedList** Type: block list Content: listItem+ Atts: - start: 1 - type: null ```html <ol class="order-list-base" type="null/some-value"><li></li></ol> ``` **listItem** Content: (paragraph|list)* (paragraphs and/or lists, in any order) Atts: none ```html <li></li> ``` **blockquote** Type: block Content: block+ (one or more block child nodes (e.g. paragraph, list, …)) Atts: none ```html <blockquote class="blockquote-base"><p class="paragraph-base"></p></blockquote> ``` ### Marks **link** Atts: - href: null - target: _blank - rel: noopener noreferrer nofollow - class: null - title: null ```html <a target="_blank" rel="noopener noreferrer nofollow" href="">link text example</a> ``` **bold** Atts: none ```html <strong>bold text example</strong> ``` **code** Atts: none ```html <code>code text example</code> ``` **italic** Atts: none ```html <em>italic text example</em> ``` **strike** Atts: none ```html <s>strike text example</s> ``` **underline** Atts: none ```html <u>underline text example</u> ``` The description will be automatically converted from HTML/Markdown to the internal IDoc format. When retrieved later via GET, it will be returned as HTML. Also accepts ProseMirror IDoc JSON (object or string).

Whether organization members (guests) can access this project. Only applicable for external (client) projects. When enabled, members of the linked organization can view and interact with the project and its tasks.

Visual identifier for the project. Must be in the format `:icon_name:` (e.g., `:rocket:`, `:shopping_cart:`, `:mobile_phone:`). This icon is displayed in project lists and throughout the application. You can use standard emoji short names (e.g., `:rocket:` for 🚀, `:shopping_cart:` for 🛒) or custom icon names created in the workspace.

Full name of the project. This is the primary display name used throughout the application.

UUID of the organization (client). Required for external projects - must be set to link the project to a client organization. Must be null for internal projects. Use the GET /organizations endpoint to retrieve available organizations.

UUID of the project phase. Phases represent distinct stages within a project lifecycle (e.g., Planning, Development, Testing). Required for external single projects, optional otherwise. Use the GET /projects/phases endpoint to retrieve available phases.

UUID of the user who is responsible for the project (e.g., project manager, sales manager). Use the GET /workspace/users endpoint to retrieve available users.

UUID of the project status. Statuses represent the current progress stage of a project (e.g., Sales, Implementation, Billing, Done). Use the GET /projects/statuses endpoint to retrieve available statuses.

Array of tag strings for categorizing and filtering projects. Tags can represent topics, teams, or work types. Tags make it easier to filter and organize projects in the project overview.

Array of task type UUIDs that can be used in this project (e.g., Feature, Bug, Management, Server issue). At least one task type must be specified. Use GET /tasks/types or GET /administration/task-settings/types to retrieve available task types.

Array of team UUIDs assigned to the project. All members of these teams will have access to the project. Use the GET /teams endpoint to retrieve available teams.

Project type determines the project structure and workflow. Single projects are one-off initiatives with defined start and finish, usually planned and billed as quoted. Ongoing projects are continuous activities where tasks are handled and billed based on effort.

Array of user UUIDs who are direct project members and have access to this project. These users can see the project, be assigned to project tasks, create or edit tasks, and log time on tasks in the project. Include every employee who should work on, be assigned to, or log time on this project; do not include only managers unless managers are the only people who need project access. At least one user must be assigned. Use the GET /workspace/users endpoint to retrieve available users.

Value group classification indicates how the project contributes to value creation. A - Direct value creation (external customer projects), B - Indirect value creation (internal projects that increase product/service value), C - Not value creating (administrative tasks), D - Waste (unproductive time).