API keys and integrations

Create credentials with the access your tools need.

• Restrict an API key to a workspace folder Anchor an API key to one workspace and folder, verify access inside the subtree, and confirm files outside it remain unavailable.
• Create a full-access API key safely Create a full-access API key safely with a controlled test, clear verification, limits, and recovery steps.
• Review when a Dosya API key was last used Review when a Dosya API key was last used with a controlled test, clear verification, limits, and recovery steps.
• Name an API key for its owner and purpose Name an API key for its owner and purpose with a controlled test, clear verification, limits, and recovery steps.
• Limit an API key to selected protocol surfaces Allow a credential to work only with the REST API, WebDAV, S3, SFTP or another selected surface, then verify cross-protocol rejection.
• Create a read-only Dosya API key Create a read-only Dosya API key with a controlled test, clear verification, limits, and recovery steps.
• Choose read, upload or full API-key permission Select the least powerful key permission, prove an allowed and denied operation, and avoid granting write or delete access unnecessarily.
• Create an upload-only Dosya API key Create an upload-only Dosya API key with a controlled test, clear verification, limits, and recovery steps.
• List files with the REST API List files with the REST API. Follow a controlled workflow, verify the result, and avoid changing the wrong workspace or item.
• Paginate through REST API file results Paginate through REST API file results with a controlled test, clear verification, limits, and recovery steps.