Documents
Dokploy API Changes (December 2025 - February 2026)
Dokploy API Changes (December 2025 - February 2026)
Type
Changelog
Status
Published
Created
Feb 27, 2026
Updated
Feb 27, 2026
Created by
Dosu Bot
Updated by
Dosu Bot

Dokploy API & Swagger/OpenAPI Documentation Changes#

I found several merged pull requests related to API changes, authentication, and system improvements in the Dokploy repository from the last few months. However, I did not find any PRs specifically focused on Swagger or OpenAPI documentation changes during this period.

API Endpoint Changes#

Authentication & Authorization#

  • Multi-admin support (PR #2506, merged 2025-12-15): Added ability to assign multiple administrators within an organization through new role management interfaces and API endpoints. Users can now be assigned "admin" role alongside owners, with proper authorization checks.

Database Management#

  • Return database instances from creation endpoints (PR #3269, merged 2025-12-20): Modified MongoDB, MySQL, MariaDB, and PostgreSQL creation endpoints to return the full database instance object instead of a boolean, enabling automation workflows to immediately access database details including databaseID.

  • Return database objects from create endpoints (PR #3276, merged 2025-12-17): Similar enhancement ensuring all database creation endpoints return the created database object, facilitating automation workflows.

Notification System#

  • Resend notification functionality (PR #3512, merged 2026-02-05): Added new "resend" notification type to support email resending operations, with new API schemas for apiKey, fromAddress, and toAddresses fields.

  • Optional access token for notifications (PR #3148, merged 2025-12-01): Made accessToken field optional in notification configurations, particularly for "ntfy" notification type, allowing public topics without authentication.

  • Pushover notification provider (PR #3447, merged 2026-01-28): Introduced Pushover as a new notification provider with dedicated schema, API endpoints, and support for real-time push notifications.

Environment & Project Management#

  • Environment isDefault flag (PR #3217, merged 2025-12-24): Added isDefault boolean flag to environment management with protections preventing deletion or renaming of default environments through API.

  • createEnvFile option (PR #3212, merged 2025-12-10): Added createEnvFile boolean option to environment settings API, controlling whether .env files are generated during Docker builds.

Deployment & Build#

  • Manual rebuild for preview deployments (PR #3389, merged 2026-01-12): Introduced "redeploy" capability through new API mutation previewDeployment.redeploy, enabling users to rebuild existing preview deployments without full code redeployment.

  • Background deployment execution (PR #3259, merged 2025-12-13): Refactored deployment API endpoints to execute deployments asynchronously in background, preventing timeouts during long-running deployments.

Registry & Cluster Management#

  • Enhanced registry handling (PR #3292, merged 2025-12-17): Made registry password optional during updates and added testRegistryById mutation for credential validation without re-entering passwords.

  • Build server categorization (PR #3298, merged 2025-12-18): Improved server selection by categorizing deploy servers (api.server.withSSHKey) and build servers (api.server.buildServers) separately.

Mount & Storage#

  • Enhanced mount API (PR #3800, merged 2026-02-26): Added service type filtering to mount API through new listByServiceId procedure, supporting multiple service types including application, postgres, mysql, mariadb, mongo, redis, and compose.

Settings & Configuration#

  • Web server settings migration (PR #3327, merged 2025-12-28): Migrated user web server configuration to dedicated webServerSettings schema with new API hook api.settings.getWebServerSettings.useQuery().

  • Deployment queue management (PR #3625, merged 2026-02-07): Added "Clean all deployment queue" feature through new mutation cleanAllDeploymentQueue in settings router.

Security & Validation Improvements#

Input Validation#

  • Container ID validation (PR #3529, merged 2026-01-27): Added container ID format validation in WebSocket server to prevent malicious inputs and potential command injection.

  • Directory validation for WebSocket logs (PR #3530, merged 2026-01-27): Implemented directory validation for WebSocket server log paths to prevent directory traversal attacks.

Authentication#

  • Admin check improvements (PR #3275, merged 2025-12-15): Updated admin check to safely access user property using optional chaining (admin?.user), preventing potential runtime errors.

Breaking Changes & Deprecations#

Field Renames#

  • Profile firstName field (PR #3527, merged 2026-01-27): Aligned profile form and API to use firstName field consistently instead of name field, requiring updates to profile update payloads.

Billing Changes#

  • Stripe customer handling (PR #3455, merged 2026-01-15): Modified Stripe checkout session creation to conditionally use either customer (when stripeCustomerId exists) or customer_email field.

API Documentation Status#

Based on the search results, I did not find specific pull requests related to:

  • Swagger UI updates or configuration changes
  • OpenAPI specification modifications
  • API documentation synchronization

The workflow file .github/workflows/sync-openapi-docs.yml was mentioned in the v0.28.0 release notes, suggesting there may be automation in place for API documentation, but no significant changes to the actual OpenAPI/Swagger documentation were merged during this period.