MOmoda
drive

Create Folder

Changed on

Create a drive folder (team-visible; nested when parent_folder_id is set).

Name conflicts are a 409 folder_name_conflict whose details carry existing_folder_id when the caller can see the conflicting folder — an agent re-running "create the project folder" should adopt that id rather than invent a suffixed name.

post/drive/folders

Request

  • Base URL
    https://api.moda.app/v1
  • URL
    https://api.moda.app/v1/drive/folders
  • Auth
    HTTP bearer

Headers

Moda-Version'2026-04-12' | '2026-05-01'
Example:2026-05-01

Calendar-dated API version pin. New integrations should pin 2026-05-01 to opt into the newest response shapes. For back-compat the server also accepts requests with no header and resolves them to the current default (today: 2026-04-12); that default advances on each sunset date. Any unsupported value returns 400 unsupported_version.

Request body

namestring required

Folder display name (unique per location).

parent_folder_idstring nullable

Prefixed fld_ wire ID (Crockford base32 body) — the canonical, recommended form. For back-compat, a bare UUID string is also accepted in both path parameters and JSON request bodies (older integrations that stored raw UUIDs keep working), as is the prefix over a UUID body (fld_00000000-0000-4000-8000-000000000000). All three are permanent, supported inputs; only the canonical form is ever emitted.

idempotency_keystring nullable

A retried create with the same key replays the stored result instead of failing on the name-conflict of its own earlier success. Use a fresh random key per intended create.

Example request

{
  "parent_folder_id": "fld_01HT9WK8N3M2J4A5Z6P7Q8R9TV"
}

Response

Successful Response

object required

Changes