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…
Create a team folder
Creates a team folder: a Pro-only shared folder with its own storage budget. Only an owner or admin of this workspace may create one. No members are assigned at creation -- add them through the app. A name already used in the workspace is 409 name_taken. Needs teams:create.
What you provide
- Name
- Descriptionoptional
- Accessoptional: everyone: every workspace member sees it. members: only members added later, through the app
- Budget gboptional: A fixed storage budget in GB. Omit or null for no limit
Do this with AI
I want to create a team folder. Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/createteam.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/teamscurl --request POST \
--url https://tarkle.com/api/v1/teams \
--header 'Authorization: Bearer $API_KEY' \
--header 'Content-Type: application/json' \
--header 'X-Workspace-Key: X-Workspace-Key' \
--data '
{
"name": "name",
"description": "description",
"access": "everyone",
"budget_gb": 1
}
'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/jsonrequirednamestringrequireddescriptionstringaccessstringeveryone: every workspace member sees it. members: only members added later, through the app
budget_gbnumberA fixed storage budget in GB. Omit or null for no limit