Skip to main content
PUT
/
v1
/
external
/
teams
/
me
/
folders
/
{folderId}
/
move
curl --request PUT \
  --url https://api.tiro.ooo/v1/external/teams/me/folders/{folderId}/move \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "newParentId": "98765",
  "sharingTypeUpdateStrategy": "KEEP_EXISTING"
}
'
{
  "id": "12345",
  "title": "Weekly Team Meetings",
  "description": "Notes from our weekly sync",
  "color": "#4A90D9",
  "sharingType": "ALL_MEMBER_VIEWER",
  "isTeamFolder": true,
  "createdAt": "2025-01-15T10:30:00Z",
  "updatedAt": "2025-01-20T12:00:00Z"
}

Authorizations

​
Authorization
string
header
required

API key in format {id}.{secret}

Path Parameters

​
folderId
string
required

Folder ID to move

Body

application/json

Request body for moving a folder to a new parent

​
newParentId
string | null

Target parent folder ID. Set to null to move to root level.

Example:

"98765"

​
sharingTypeUpdateStrategy
enum<string>
default:KEEP_EXISTING

Strategy for updating sharing permissions after the move. Defaults to KEEP_EXISTING.

  • Use KEEP_EXISTING to maintain the folder's current sharing permissions
  • Use INHERIT_FROM_PARENT to adopt the new parent's sharing permissions
Available options:
KEEP_EXISTING,
INHERIT_FROM_PARENT
Example:

"KEEP_EXISTING"

Response

Folder moved successfully

Detailed folder information including metadata

​
id
string
required

Unique identifier for the folder

Example:

"12345"

​
title
string
required

Folder title (max 50 characters)

Example:

"Weekly Team Meetings"

​
description
string
required

Folder description

Example:

"Notes from our weekly team sync meetings"

​
color
string
required

Folder color in hex format

Example:

"#4A90D9"

​
isTeamFolder
boolean
required

Whether this is a team folder

Example:

true

​
createdAt
string<date-time>
required

ISO-8601 creation timestamp

Example:

"2025-01-15T10:30:00Z"

​
updatedAt
string<date-time>
required

ISO-8601 last update timestamp

Example:

"2025-01-15T11:45:00Z"

​
sharingType
enum<string>

Sharing permission level for team folders. Controls who can access notes within the folder.

TypeView AccessEdit Access
ALL_MEMBER_EDITORAll team membersAll team members
ALL_MEMBER_VIEWERAll team membersNo team-wide edit access granted
LIMITEDInvited members onlyInvited members only (per-member role)

Details:

  • ALL_MEMBER_EDITOR: All team members can view and edit notes in this folder.
  • ALL_MEMBER_VIEWER: All team members can view notes. No edit access is granted at the team level.
  • LIMITED: Only explicitly invited members can access. When inviting members, you assign each member either VIEWER or EDITOR role individually.
Available options:
ALL_MEMBER_EDITOR,
ALL_MEMBER_VIEWER,
LIMITED
Example:

"ALL_MEMBER_VIEWER"