This week, the mittwald API introduces several changes, including modifications to response formats and properties for the user authentication and lead management endpoints, the addition of a new endpoint for cronjob execution analysis, and updates to the response structure for various service-related operations.
This week's update to the mittwald API includes changes to the request parameter types for various endpoints, making the 'appInstallationId', 'cronjobId', 'customerId', 'fileId', and 'projectId' parameters more flexible, alongside the addition of new endpoints and required response properties for better clarity and functionality.
This week's changelog for the mittwald API includes significant updates such as changes to request parameter types, the addition of new optional properties, and the introduction of a new endpoint for copying MySQL databases.
mysqlDatabaseId path parameter has changed from 'string'/'uuid' to 'string' for the following operations: DELETE (delete a MySQLDatabase), GET (get a MySQLDatabase), PATCH (update a MySQLDatabase's default character settings), PATCH (update a MySQLDatabase's description), GET (list MySQLUsers belonging to a Database), and POST (create a MySQLUser).mysqlUserId path parameter has changed from 'string'/'uuid' to 'string' for the following operations: DELETE (delete a MySQLUser), GET (get a MySQLUser), PUT (update a MySQLUser), POST (disable a MySQLUser), POST (enable a MySQLUser), PATCH (update a MySQLUser's password), and GET (get a MySQLUser's PhpMyAdmin-URL).projectBackupId path parameter has changed from 'string'/'uuid' to 'string' for the following operations: DELETE (delete a ProjectBackup), GET (get a ProjectBackup), PATCH (update a ProjectBackup's description), DELETE (delete a ProjectBackupExport), and POST (create a ProjectBackupExport). TprojectId path parameter has changed from 'string'/'uuid' to 'string' for the following operations: GET (get a Project), DELETE (delete a Project's avatar), POST (request a Project avatar upload), GET (list BackupSchedules belonging to a Project), POST (create a BackupSchedule for a Project), GET (list Backups belonging to a Project), POST (create a Backup of a Project), PATCH (update a Project's description), GET (get a Project directory filesystem usage), GET (get a Project file's content), GET (get a Project file's information), GET (list MySQLDatabases belonging to a Project), POST (create a MySQLDatabase with a MySQLUser), GET (list RedisDatabases belonging to a Project), POST (create a RedisDatabase), GET (list Registries belonging to a Project), POST (create a Registry), GET (list Services belonging to a Project), GET (list Stacks belonging to a Project), and GET (list Volumes belonging to a Project).redisDatabaseId path parameter has changed from 'string'/'uuid' to 'string' for the following operations: DELETE (delete a RedisDatabase), GET (get a RedisDatabase), PATCH (update a RedisDatabase's configuration), and PATCH (update a RedisDatabase's description).serverId path parameter has changed from 'string'/'uuid' to 'string' for the following operations: DELETE (delete a Server's avatar), POST (request a Server avatar upload), PATCH (update a Server's description), and POST (create a Project belonging to a Server).serviceId path parameter has changed from 'string'/'uuid' to 'string' for the following operations: GET (get a Service belonging to a Stack), POST (pull image for a Service), POST (recreate a Service), POST (restart a Service), POST (start a Service), POST (stop a Service), and GET (get logs belonging to a Service).dryRun request property has been removed from the PUT operation to update extension pricing.priceInCents request property has been removed from the PUT operation to update extension pricing.PUT operation to update extension pricing has added 'subschema #1, subschema #2' to the request body 'oneOf' list.PUT operation to update extension pricing has added the optional property nextPossiblePriceChange to the response with the '200' status.PUT operation to update extension pricing has made the response properties extensionId and priceChangeConsequence required for the status '200'.GET operation to get the contract strategy of an extension instance has added the optional properties variantDescription, variantKey, and variantName to the response with the '200' status.PUT operation to update or create a contract for existing extension instances has added the new optional request property variantKey.POST operation to copy a MySQLDatabase with a MySQLUser.GET operation to get a Project has added the optional property deletionRequested to the response with the '200' status.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For a lot of routes, the format of the id parameter has changed from a UUID to a simple string, according to the API Spec. This is only logical, as we enabled resources to be queried using shortId some time ago.
For details, refer to the DELETE/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the DELETE/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the PUT/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the DELETE/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the DELETE/ endpoint.
For details, refer to the POST/ endpoint.
for the 'path' request parameter 'projectId', the type/format was changed from 'string'/'uuid' to 'string'/''
added the optional property 'deletionRequested' to the response with the '200' status
For details, refer to the GET/ endpoint.
For details, refer to the DELETE/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the DELETE/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the DELETE/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the PATCH/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the GET/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the POST/ endpoint.
For details, refer to the GET/ endpoint.
added the optional property '/oneOf[#/components/schemas/de.mittwald.v1.extension.SubscriptionBasedContract]/variantDescription' to the response with the '200' status
added the optional property '/oneOf[#/components/schemas/de.mittwald.v1.extension.SubscriptionBasedContract]/variantKey' to the response with the '200' status
added the optional property '/oneOf[#/components/schemas/de.mittwald.v1.extension.SubscriptionBasedContract]/variantName' to the response with the '200' status
For details, refer to the GET/ endpoint.
For details, refer to the PUT/ endpoint.
For details, refer to the POST/ endpoint.
The latest release of the mittwald PHP SDK, version 2.1.155, introduces several updates and improvements.
deletionRequested has been added to the Project schema. This boolean property indicates whether a deletion request for a project has been made.format: uuid specification has been removed from several request properties to simplify API interactions. This affects the following requests:
CreateProjectRequest.serverIdDeleteProjectAvatarRequest.projectIdDeleteServerAvatarRequest.serverIdGetProjectRequest.projectIdRequestProjectAvatarUploadRequest.projectIdRequestServerAvatarUploadRequest.serverIdUpdateProjectDescriptionRequest.projectIdUpdateServerDescriptionRequest.serverIdProjectFileSystemGetDiskUsageRequest.projectIdProjectFileSystemGetFileContentRequest.projectIdProjectFileSystemListFilesRequest.projectIddeletionRequested property has been added, allowing clients to check if a project deletion has been requested.deletionRequested property:
getDeletionRequested(): Retrieves the current value.withDeletionRequested(bool $deletionRequested): Sets the value.withoutDeletionRequested(): Removes the flag.For more details, visit the release page.
The latest release of the mittwald PHP SDK, v2.1.154, introduces new features and improvements to enhance database management capabilities.
format property for uuid has been removed from several request schemas within the Backup and Database clients, including:
CreateProjectBackupRequestCreateProjectBackupExportRequestCreateProjectBackupScheduleRequestCopyMysqlDatabaseRequestCopyMysqlDatabaseCreatedResponseCopyMysqlDatabaseBadRequestResponseCopyMysqlDatabaseNotFoundResponseCopyMysqlDatabaseTooManyRequestsResponseCopyMysqlDatabaseDefaultResponseThese updates provide a robust setup for managing MySQL databases and enhance the existing API capabilities.
The latest release of the mittwald PHP SDK, version 2.1.153, introduces several new features and changes aimed at enhancing the management of extension pricing and variants.
variantKey when updating an extension instance and choose pricing options based on price plans.Extension Update Requests:
ExtensionUpdateExtensionInstanceContractRequest: Introduces a new variantKey property, essential for extensions with multiple variants.ExtensionUpdateExtensionPricingRequest: Updated to support two alternative request bodies for specifying a price in cents or selecting a price plan, with added validations.Responses:
ExtensionUpdateExtensionPricingOKResponse: Includes a new nextPossiblePriceChange property to indicate the next valid time for price changes.Data Models:
PricePlan, Variant, and VariantDescriptionChangeType have been introduced to handle price plans and variant descriptions.SubscriptionBasedContract: Enhanced with new properties for extended variant information.Validation Enhancements: Improved validation logic to ensure the integrity of inputs related to price plans and variants.
Miscellaneous: Code refactoring for better clarity and maintainability, including improvements in cloning and JSON serialization.
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.242.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.242.0.
The mittwald JavaScript SDK has been updated to version 4.241.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.241.0.
The mittwald JavaScript SDK has been updated to version 4.240.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.240.0.
The mittwald JavaScript SDK has been updated to version 4.239.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the release on GitHub here.
This week's update to the mittwald API introduces several enhancements, including the addition of default values for request parameters, increased minimum values for certain parameters, new optional properties in responses, and the introduction of multiple new endpoints.
This week, the mittwald API introduces several enhancements, including the addition of optional properties for cronjob management, a new request parameter for ingress listing, and the enforcement of a maximum length for the 'hostnameSubstring' parameter.
This week, the mittwald API introduces several important changes, including the requirement of additional response properties for successful status codes in various endpoints, the addition of a new optional request parameter for listing ingresses, and the introduction of a new non-success response status for order creation.
This week, the mittwald API introduces several changes including the removal of default values for request parameters, updates to parameter types, the addition of new optional properties, and the introduction of required properties in responses, enhancing the overall functionality and flexibility of the API.
This week's update to the mittwald API includes significant changes such as the alteration of request parameter types for various endpoints, the addition of required and optional properties in responses, and the introduction of new optional request parameters, enhancing the overall functionality and flexibility of the API.
In the week of 8/29/2025 to 9/5/2025, the mittwald API introduced several enhancements, including changes to response property types, the addition of required and optional properties, new endpoints for managing contributors and DNS zones, and updates to request parameters for improved functionality.
This week's changelog for the mittwald API includes several updates, such as changes to response property types, the addition and removal of required and optional properties, new optional request parameters, and the introduction of new endpoints.