Skip to main content
PATCH
Rename or pin a folder
Moving projects is done with updateProject folder_id. When to use: to rename or pin a folder. Side effects: None. Cost: Free. Idempotency: Idempotency-Key accepted (SDKs send one); retries within 24 h replay the first response. Required scopes: projects:write

Authorizations

Authorization
string
header
required

API key from Settings -> API keys, sent as Authorization: Bearer <key> (SDK environment variable RASK_API_KEY). Bound to one workspace and one acting user. Operations list the scopes they need (OpenAPI 3.1 scopes on a bearer scheme).

Scopes

projects:write

Headers

Idempotency-Key
string

Optional. A unique key per logical request (SDKs send a bare UUIDv4; an RFC 9651 quoted string is accepted and unquoted); reuse it unchanged on retries to replay the first response.

Required string length: 1 - 255
Pattern: ^[\x20-\x7E]+$

Path Parameters

folder_id
string
required

Folder id.

Maximum string length: 64

Body

application/json

Body of updateFolder.

name
string

Folder name.

Required string length: 1 - 255
is_pinned
boolean

Pinned.

Response

OK: Folder.

A project folder.

object
enum<string>
required

Always folder.

Available options:
folder
id
string
required

Folder id.

name
string
required

Folder name.

is_pinned
boolean
required

Pinned in the web app.

project_count
integer<int32>
required

Live projects in the folder.

created_at
string<date-time>
required

Creation time.