WebDAV Operations

The WebDAV operations expose RFC 4918-compliant file management endpoints for accessing, copying, moving, locking, and inspecting properties on container files. Use these endpoints when integrating with WebDAV-aware clients such as Nextcloud, ownCloud, Cyberduck, macOS Finder, and Windows Explorer.

All endpoints operate on paths relative to the container’s workspace. Authentication uses a container-scoped token. LOCK and UNLOCK are compatibility stubs — the server does not enforce locking semantics, but responds with valid tokens so WebDAV clients can complete their workflows.

Note

The base URL is host-scoped to your container’s file service. Construct the full URL as https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/{path}.

Connection and Capability Discovery

GET /api/files/webdav/{path}

Connect to a remote WebDAV server (Nextcloud, ownCloud, etc.) through this container. Returns the file content or a directory listing proxied from the upstream endpoint. Use this endpoint to provide WebDAV access when clients cannot reach the upstream server directly.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path inside the container
type	query	string	Yes	Must be webdav
server	query	string	Yes	Target WebDAV server hostname
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: "/"

cURL

curl -X GET "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/remote.php/webdav/Documents?type=webdav&server=cloud.example.com&user=alice&pass=$WEBDAV_PASS&webdav_path=/"

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.access('/remote.php/webdav/Documents', {
  type: 'webdav',
  server: 'cloud.example.com',
  user: 'alice',
  pass: process.env.WEBDAV_PASS,
  webdav_path: '/',
});

Responses

200

File content or directory listing returned from the upstream WebDAV server.

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

OPTIONS /api/files/webdav/{path}

Returns supported HTTP methods and WebDAV capabilities in the Allow header. WebDAV clients call this endpoint first to discover which verbs they can use.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path inside the container

cURL

curl -X OPTIONS "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/report.pdf" \
  -i

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.getOptions('/Documents/report.pdf');

Responses

204

Capability discovery per RFC 4918 §10.1. No response body. The advertised methods and DAV class are returned in response headers:

• 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.

File Operations

COPY /api/files/webdav/{path}

WebDAV COPY: copy a file or directory to a new location specified by the Destination header. Use Depth: 0 to copy a single file, or Depth: infinity to recursively copy a directory.

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. Allowed values: 0 (file only) or infinity (recursive for directories). Default: "infinity"

cURL

curl -X COPY "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/report.pdf" \
  -H "Destination: https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Archive/report.pdf" \
  -H "Depth: 0"

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.copyResource('/Documents/report.pdf', {
  Destination: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Archive/report.pdf',
  Depth: '0',
});

Responses

201

Resource copied successfully.

204

Resource overwritten at destination.

403

Copy not allowed.

{
  "success": false,
  "error": "Copy not allowed: insufficient permissions on source resource"
}

404

Source resource not found.

409

Destination parent does not exist.

MOVE /api/files/webdav/{path}

WebDAV MOVE: move or rename a file or directory to a new location specified by the Destination header. The caller must hold both upload and delete permissions on the source and destination.

Parameters

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

cURL

curl -X MOVE "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/draft.txt" \
  -H "Destination: https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/final.txt"

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.moveResource('/Documents/draft.txt', {
  Destination: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/final.txt',
});

Responses

201

Resource moved successfully.

204

Resource overwritten at destination.

403

Move not allowed. The caller must hold both upload and delete permissions.

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

404

Source resource not found.

409

Destination parent does not exist.

Locking

LOCK /api/files/webdav/{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 inside the container
Depth	header	string	No	Allowed values: 0 or infinity

Request Body

The optional request body is a WebDAV lock XML document describing the requested lock scope, type, and owner. Omit the body to request a default exclusive write lock.

cURL

curl -X LOCK "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/report.pdf" \
  -H "Depth: infinity" \
  -H "Content-Type: application/xml" \
  -d '<?xml version="1.0" encoding="utf-8"?>
<D:lockinfo xmlns:D="DAV:">
  <D:lockscope><D:exclusive/></D:lockscope>
  <D:locktype><D:write/></D:locktype>
  <D:owner><D:href>mailto:alice@example.com</D:href></D:owner>
</D:lockinfo>'

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.lockResource('/Documents/report.pdf', `<?xml version="1.0" encoding="utf-8"?>
<D:lockinfo xmlns:D="DAV:">
  <D:lockscope><D:exclusive/></D:lockscope>
  <D:locktype><D:write/></D:locktype>
  <D:owner><D:href>mailto:alice@example.com</D:href></D:owner>
</D:lockinfo>`, { Depth: 'infinity' });

Responses

200

Lock token issued for compatibility. The response body is a WebDAV XML prop document containing a lockdiscovery element with the issued token.

<?xml version="1.0" encoding="utf-8"?>
<D:prop xmlns:D="DAV:">
  <D:lockdiscovery>
    <D:activelock>
      <D:locktype><D:write/></D:locktype>
      <D:lockscope><D:exclusive/></D:lockscope>
      <D:depth>infinity</D:depth>
      <D:timeout>Second-3600</D:timeout>
      <D:locktoken>
        <D:href>urn:uuid:e71d3c20-3e3f-11ec-8d3d-0242ac130004</D:href>
      </D:locktoken>
    </D:activelock>
  </D:lockdiscovery>
</D:prop>

404

File not found.

UNLOCK /api/files/webdav/{path}

WebDAV UNLOCK: release a previously issued lock token. This is a no-op compatibility stub — the server does not track lock state.

Parameters

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

cURL

curl -X UNLOCK "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/report.pdf" \
  -H "Lock-Token: <urn:uuid:e71d3c20-3e3f-11ec-8d3d-0242ac130004>"

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.unlockResource('/Documents/report.pdf', {
  'Lock-Token': 'urn:uuid:e71d3c20-3e3f-11ec-8d3d-0242ac130004',
});

Responses

204

Lock released (no-op).

404

Resource not found.

Properties

PROPFIND /api/files/webdav/{path}

WebDAV PROPFIND: retrieve properties (metadata) for files or directories. Returns a 207 Multi-Status response containing resource type, size, modification date, ETag, and other properties in WebDAV XML format. Use the Depth header to control recursion into directories.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path inside the container
Depth	header	string	No	Depth of property retrieval. Allowed values: 0 (resource only), 1 (immediate children), infinity (recursive). Default: "1"

Request Body

The optional request body is a PROPFIND XML document specifying which properties to retrieve. Omit the body to retrieve the standard set of properties.

cURL

curl -X PROPFIND "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents" \
  -H "Depth: 1" \
  -H "Content-Type: application/xml" \
  -d '<?xml version="1.0" encoding="utf-8"?>
<D:propfind xmlns:D="DAV:">
  <D:prop>
    <D:resourcetype/>
    <D:getcontentlength/>
    <D:getlastmodified/>
    <D:getetag/>
  </D:prop>
</D:propfind>'

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.propfindResource('/Documents', `<?xml version="1.0" encoding="utf-8"?>
<D:propfind xmlns:D="DAV:">
  <D:prop>
    <D:resourcetype/>
    <D:getcontentlength/>
    <D:getlastmodified/>
    <D:getetag/>
  </D:prop>
</D:propfind>`, { Depth: '1' });

Responses

207

Multi-Status response with resource properties in WebDAV XML format.

<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
  <D:response>
    <D:href>/Documents</D:href>
    <D:propstat>
      <D:prop>
        <D:resourcetype><D:collection/></D:resourcetype>
        <D:getcontentlength>0</D:getcontentlength>
        <D:getlastmodified>Mon, 01 Jan 2024 12:00:00 GMT</D:getlastmodified>
        <D:creationdate>2024-01-01T12:00:00Z</D:creationdate>
        <D:getetag>"d41d8cd98f00b204e9800998ecf8427e"</D:getetag>
      </D:prop>
      <D:status>HTTP/1.1 200 OK</D:status>
    </D:propstat>
  </D:response>
  <D:response>
    <D:href>/Documents/report.pdf</D:href>
    <D:propstat>
      <D:prop>
        <D:resourcetype/>
        <D:getcontentlength>1048576</D:getcontentlength>
        <D:getlastmodified>Fri, 12 Jan 2024 09:30:00 GMT</D:getlastmodified>
        <D:creationdate>2024-01-12T09:30:00Z</D:creationdate>
        <D:getetag>"a1b2c3d4e5f67890"</D:getetag>
        <D:getcontenttype>application/pdf</D:getcontenttype>
      </D:prop>
      <D:status>HTTP/1.1 200 OK</D:status>
    </D:propstat>
  </D:response>
</D:multistatus>

404

Resource not found.

PROPPATCH /api/files/webdav/{path}

WebDAV PROPPATCH: modify dead properties on a file or directory. Returns a 207 Multi-Status response confirming the property changes.

Parameters

Name	In	Type	Required	Description
path	path	string	Yes	Resource path inside the container

Request Body

The request body is a PROPPATCH XML document with set and/or remove instructions for the target properties.

cURL

curl -X PROPPATCH "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/files/webdav/Documents/report.pdf" \
  -H "Content-Type: application/xml" \
  -d '<?xml version="1.0" encoding="utf-8"?>
<D:propertyupdate xmlns:D="DAV:">
  <D:set>
    <D:prop>
      <D:displayname>Annual Report 2024</D:displayname>
    </D:prop>
  </D:set>
</D:propertyupdate>'

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.files.webdav.proppatchResource('/Documents/report.pdf', `<?xml version="1.0" encoding="utf-8"?>
<D:propertyupdate xmlns:D="DAV:">
  <D:set>
    <D:prop>
      <D:displayname>Annual Report 2024</D:displayname>
    </D:prop>
  </D:set>
</D:propertyupdate>`);

Responses

207

Multi-Status response confirming property changes.

<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
  <D:response>
    <D:href>/Documents/report.pdf</D:href>
    <D:propstat>
      <D:prop>
        <D:displayname>Annual Report 2024</D:displayname>
      </D:prop>
      <D:status>HTTP/1.1 200 OK</D:status>
    </D:propstat>
  </D:response>
</D:multistatus>

404

File not found.