Hey, human!
HTTP/2 200 OK content-type: text/markdown; charset=utf-8 vary: accept, user-agent x-agent: [ai_agent]
Loading the agent response…
Rename and/or move a file or folder, and/or set a file's own modification time (body: name, parent_id: a folder id or null for the root, modified_at)
Renames and/or moves a file or folder, and/or sets a file's own modification time (modified_at, files only). Send at least one of name, parent_id (a folder id, or null for the library root) and modified_at; other keys such as a path or a parent name are refused. A name already used in the destination is 409 name_taken. Protected items (system, request or team folders, or an item a paid transfer holds) are 403 protected. Returns the item after the change. Needs files:write.
What you provide
- Nameoptional: The new name, at most 255 bytes
- Parent idoptional: Move into this folder; null moves to the library root
- Modified atoptional: The file's own modification time: ISO 8601 with a time zone, after 1970-01-02 and at most one day ahead. Files only
- Visibilityoptional: Folders only: who can see it. Only the person who made the folder, an owner or an admin can change it
Do this with AI
I want to rename and/or move a file or folder, and/or set a file's own modification time (body: name, parent_id: a folder id or null for the root, modified_at). Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/updatefile.md Authenticate with your API key as a Bearer token in the Authorization header. Then make the request for me and tell me what came back.
Paste this into Claude, Cursor, or any AI assistant and it will do it for you.
https://tarkle.com/api/v1/files/{id}curl --request PATCH \
--url https://tarkle.com/api/v1/files/id \
--header 'Authorization: Bearer $API_KEY' \
--header 'Content-Type: application/json' \
--header 'X-Workspace-Key: X-Workspace-Key' \
--data '
{
"name": "name",
"parent_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"modified_at": "2024-01-01T00:00:00Z",
"visibility": "private"
}
'Path parameters
idstringrequiredA file id (digits) or a folder id (uuid)
Query parameters
workspace_keystringThe same key as the X-Workspace-Key header, for clients that cannot set headers. Send one of the two, or both with the same value (different values are 400 conflicting_workspace)
Header parameters
X-Workspace-KeystringrequiredThe 8-character key of the workspace this call acts on; GET /workspaces lists the keys a token can use. A workspace id is refused (400 workspace_key_required)
Idempotency-KeystringMakes a write safe to repeat. Send a random value (a UUID is fine) of up to 255 visible characters. A repeat of the same request gets the first answer again, with the header `Idempotent-Replayed: true`, and does nothing twice. The same key for a different request is 422 `idempotency_key_reused`; the same request while the first one is still running is 409 `idempotency_in_progress`. A 5xx or 429 is not remembered, so retrying it runs the request again. Keys last 24 hours and belong to the account that created the token.
Body
application/jsonrequirednamestringThe new name, at most 255 bytes
parent_idstring · uuid | nullMove into this folder; null moves to the library root
modified_atstring · date-timeThe file's own modification time: ISO 8601 with a time zone, after 1970-01-02 and at most one day ahead. Files only
visibilitystringFolders only: who can see it. Only the person who made the folder, an owner or an admin can change it