WebDAV Operations

The WebDAV endpoints expose WebDAV-compatible file operations on Hoody file resources. These endpoints implement the HTTP verbs defined in RFC 4918 so that standard WebDAV clients — including Nextcloud, ownCloud, macOS Finder, Windows Explorer, and Cyberduck — can connect to Hoody as a WebDAV server.

Use these endpoints when you need to:

• Connect an external WebDAV client to a file path on Hoody.
• Discover server capabilities via OPTIONS.
• Copy or move files between paths.
• Issue LOCK / UNLOCK for client compatibility.
• Retrieve (PROPFIND) or modify (PROPPATCH) WebDAV properties.

Note

LOCK and UNLOCK are compatibility stubs — the server does not enforce locks. They exist only to satisfy WebDAV clients that require these verbs during normal browsing.

Access file via WebDAV

GET /{path}?type=webdav

Connect a WebDAV client (Nextcloud, ownCloud, etc.) to a Hoody file path. Returns the file content or a directory listing.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path on the Hoody WebDAV server
type	query	string	Yes	Must be webdav
server	query	string	Yes	Hoody server base URL
user	query	string	No	Username for WebDAV authentication
pass	query	string	No	Password for WebDAV authentication
webdav_path	query	string	No	WebDAV endpoint path. Default: /

Response

200

{
  "description": "File content or directory listing"
}

SDK usage

await client.files.webdav.access({
  path: "documents/report.pdf",
  type: "webdav",
  server: "https://app.hoody.com",
  user: "alice",
  pass: "••••••••",
  webdav_path: "/"
});

Get allowed methods

OPTIONS /{path}

Returns supported HTTP methods and WebDAV capabilities in the Allow header. Used by WebDAV clients for capability discovery (RFC 4918 §10.1).

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path to query for capabilities

This endpoint takes no body.

Response

Returns 204 No Content. The advertised methods and DAV class are conveyed via response headers:

Header	Description
Allow	Comma-separated list of supported HTTP methods. WebDAV-root paths advertise the full WebDAV verb set; /api/v1/* paths advertise the simple HTTP set.
DAV	WebDAV compliance class. Set to 1 on WebDAV-root OPTIONS responses; absent on /api/v1/* OPTIONS responses.
MS-Author-Via	Authoring-protocol hint for Microsoft WebDAV clients. Set to DAV on WebDAV-root OPTIONS responses.

SDK usage

await client.files.webdav.getOptions({
  path: "documents/"
});

Copy file or directory

COPY /{path}

WebDAV COPY: copy a file or directory to a new location specified by the Destination header.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Source file or directory path
Destination	header	string	Yes	Destination URL for the copy
Depth	header	string	No	Copy depth: 0 (file only) or infinity (recursive for directories). Default: infinity

This endpoint takes no body.

Response

201

{
  "description": "Resource copied successfully"
}

204

{
  "description": "Resource overwritten at destination"
}

403

{
  "error": "Copy not allowed",
  "success": false
}

404

{
  "description": "Source resource not found"
}

409

{
  "description": "Destination parent does not exist"
}

SDK usage

await client.files.webdav.copyResource({
  path: "documents/report.pdf",
  Destination: "https://app.hoody.com/webdav/archive/report.pdf",
  Depth: "0"
});

Move or rename file/directory

MOVE /{path}

WebDAV MOVE: move a file or directory to a new location specified by the Destination header. Requires both upload and delete permissions on the source.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Source file or directory path
Destination	header	string	Yes	Destination URL for the move

This endpoint takes no body.

Response

201

{
  "description": "Resource moved successfully"
}

204

{
  "description": "Resource overwritten at destination"
}

403

{
  "error": "Move not allowed: requires upload and delete permissions",
  "success": false
}

404

{
  "description": "Source resource not found"
}

409

{
  "description": "Destination parent does not exist"
}

SDK usage

await client.files.webdav.moveResource({
  path: "documents/draft.pdf",
  Destination: "https://app.hoody.com/webdav/documents/final.pdf"
});

Lock file (WebDAV compatibility)

LOCK /{path}

WebDAV LOCK: returns a lock token for WebDAV client compatibility. This is a compatibility stub — locks are not enforced server-side.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path to lock
Depth	header	string	No	Lock depth: 0 or infinity

Request Body

Optional XML lock request body (application/xml).

<?xml version="1.0" encoding="utf-8"?>

  </D:lockscope>
  </D:locktype>
</D:lockinfo>

Response

200

<?xml version="1.0" encoding="utf-8"?>



      opaquelocktoken:hoody-compat</D:href></D:locktoken>
    </D:activelock>
  </D:lockdiscovery>
</D:prop>

404

{
  "description": "File not found"
}

SDK usage

await client.files.webdav.lockResource({
  path: "documents/report.pdf",
  Depth: "0"
});

Unlock file (WebDAV compatibility)

UNLOCK /{path}

WebDAV UNLOCK: release a lock token. This is a no-op compatibility stub.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path to unlock
Lock-Token	header	string	Yes	Lock token to release

This endpoint takes no body.

Response

204

{
  "description": "Lock released (no-op)"
}

404

{
  "description": "Resource not found"
}

SDK usage

await client.files.webdav.unlockResource({
  path: "documents/report.pdf",
  Lock-Token: "opaquelocktoken:hoody-compat"
});

Get WebDAV properties

PROPFIND /{path}

WebDAV PROPFIND: retrieve properties (metadata) for files or directories. Returns XML with resource type, size, modification date, ETag, and more. Supports the Depth header (0, 1, infinity) to control recursion into directories.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path to query
Depth	header	string	No	Depth of property retrieval: 0 (resource only), 1 (immediate children), infinity (recursive). Default: 1

Request Body

Optional PROPFIND XML body (application/xml) specifying which properties to retrieve. If omitted, all properties are returned.

<?xml version="1.0" encoding="utf-8"?>





  </D:prop>
</D:propfind>

Response

207

<?xml version="1.0" encoding="utf-8"?>


    /documents/report.pdf</D:href>


        245760</D:getcontentlength>
        Mon, 10 Feb 2025 14:32:11 GMT</D:getlastmodified>

      </D:prop>
      HTTP/1.1 200 OK</D:status>
    </D:propstat>
  </D:response>
</D:multistatus>

404

{
  "description": "Resource not found"
}

SDK usage

await client.files.webdav.propfindResource({
  path: "documents/",
  Depth: "1"
});

Update WebDAV properties

PROPPATCH /{path}

WebDAV PROPPATCH: modify properties on a file. Returns a 207 Multi-Status response.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path to modify

Request Body

PROPPATCH XML body (application/xml) with set / remove instructions for the target properties.

<?xml version="1.0" encoding="utf-8"?>



      <customprop xmlns="https://hoody.com/ns/">archived</customprop>
    </D:prop>
  </D:set>
</D:propertyupdate>

Response

207

<?xml version="1.0" encoding="utf-8"?>


    /documents/report.pdf</D:href>


        <customprop xmlns="https://hoody.com/ns/">archived</customprop>
      </D:prop>
      HTTP/1.1 200 OK</D:status>
    </D:propstat>
  </D:response>
</D:multistatus>

404

{
  "description": "File not found"
}

SDK usage

await client.files.webdav.proppatchResource({
  path: "documents/report.pdf"
});