CDN and content
WebDAV
#Overview
WebDAV reuses an API token and the console file rules.
#Use file storage as a remote volume
The WebDAV endpoint accepts OPTIONS, PROPFIND, GET, HEAD, PUT, DELETE, and MKCOL. Use HTTP Basic authentication: the verified account email is the username and the personal API token is the password. OPTIONS is public.
Reads require a token with * or files:read; writes require * or files:write. Writes follow the same delivery guards as the Files API. Start PROPFIND with bounded depth and avoid concurrent synchronization of the same path.
#Configure a client
Create a dedicated token with the minimum file ability.
Enter the
/webdav/or/api/files/webdav/URL required by the integration.Set the verified email as username and the token as password.
Test OPTIONS and then PROPFIND before creating, reading, and removing a test file.
#WebDAV methods
https://api.cdn.pizza/api/files/webdav/
HTTP Basic authentication: use the verified email as the username and the personal API token as the password. OPTIONS is public; other methods enforce the token’s files:read and files:write abilities.
Discover capabilities
List a collection and its properties
Download an object
Read response headers only
Create or replace an object
Delete an object or collection
Create a collection
curl --request PROPFIND \
--url 'https://api.cdn.pizza/api/files/webdav/' \
--user 'EMAIL:YOUR_API_TOKEN' \
--header 'Depth: 1'