This week's update to the mittwald API introduces the new 'unspecified' enum value across various response properties and request parameters, enhances error handling with additional non-success status responses, and adds new endpoints for managing AI hosting keys and plans.
The new enum value 'unspecified' has been added to the /items/status response property for the response status '200' in the following operations:
GET /v2/projects/{projectId}/services (List Services belonging to a Project)GET /v2/services (List Services the executing user has access to)GET /v2/stacks (List Stacks of the Projects in which the executing user is owner or external member)GET /v2/stacks/{stackId} (Get a Stack)The new enum value 'unspecified' has been added to the /items/services/items/status response property for the response status '200' in the following operations:
GET /v2/projects/{projectId}/stacks (List Stacks belonging to a Project)GET /v2/stacks (List Stacks of the Projects in which the executing user is owner or external member)GET /v2/stacks/{stackId} (Get a Stack)PATCH /v2/stacks/{stackId} (Create, update or delete Services or Volumes belonging to a Stack)PUT /v2/stacks/{stackId} (Declaratively create, update or delete Services or Volumes belonging to a Stack)The new enum value 'unspecified' has been added to the services/items/status response property for the response status '201' in the operation:
POST /v2/projects/{projectId}/stacks (Create a Stack)The new enum value 'unspecified' has been added to the services/items/status response property for the response status '200' in the operation:
GET /v2/stacks/{stackId} (Get a Stack)The following endpoints have been added:
GET /v2/ai-hosting-keys (Get all ai hosting keys the authenticated user can access)GET /v2/ai-hostings (Get all ai hosting plans the authenticated user can access)The non-success response with the status '403' has been added to the following operations:
GET /v2/certificates/{certificateId}/contract (Return the Contract for the given Certificate)GET /v2/contracts/{contractId} (Returns the Contract with the given ID)GET /v2/contracts/{contractId}/base-items (Return the BaseItem of the Contract with the given ID)GET /v2/contracts/{contractId}/items/{contractItemId} (Get the ContractItem with the given ID)GET /v2/customers/{customerId}/ai-hostings/{aiHostingId}/contract (Return the AI Hosting Contract for the given Customer)GET /v2/customers/{customerId}/lead-fyndr-profile/contract (Return the Contract for the given LeadFyndrProfile)GET /v2/domains/{domainId}/contract (Return the Contract for the given Domain)GET /v2/licenses/{licenseId}/contract (Return the Contract for the given License)GET /v2/mail-addresses/{mailAddressId}/contract (Return the Contract for the given Mail Address)GET /v2/projects/{projectId}/contract (Return the Contract for the given Project)GET /v2/servers/{serverId}/contract (Return the Contract for the given Server)The non-success response with the status '400' has been added to the following operations:
PATCH /v2/customer-memberships/{customerMembershipId} (Update a CustomerMembership)PATCH /v2/project-memberships/{projectMembershipId} (Update a ProjectMembership)The non-success response with the status '404' has been added to the following operations:
PATCH /v2/customer-memberships/{customerMembershipId} (Update a CustomerMembership)PATCH /v2/project-memberships/{projectMembershipId} (Update a ProjectMembership)The non-success response with the status '412' has been added to the following operations:
PATCH /v2/customer-memberships/{customerMembershipId} (Update a CustomerMembership)PATCH /v2/project-memberships/{projectMembershipId} (Update a ProjectMembership)The new enum value 'unspecified' has been added to the query request parameter 'status' in the operation:
GET /v2/projects/{projectId}/services (List Services belonging to a Project)Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
added the new 'unspecified' enum value to the '/items/status' response property for the response status '200'
added the new enum value 'unspecified' to the 'query' request parameter 'status'
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the PATCH/v2/
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
For details, refer to the unknown operation ai-hosting-user-get-keys endpoint.
For details, refer to the unknown operation ai-hosting-user-get-plans endpoint.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the non-success response with the status '400'
added the non-success response with the status '403'
added the non-success response with the status '404'
added the non-success response with the status '412'
For details, refer to the PATCH/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the non-success response with the status '400'
added the non-success response with the status '403'
added the non-success response with the status '404'
added the non-success response with the status '412'
For details, refer to the PATCH/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The mittwald PHP SDK has been updated to version 2.2.20. This release includes several enhancements and clarifications across various components:
Container & Stack Networking: Improved DNS resolution and isolation rules for containerized services. Managed applications within the same project can resolve services using <serviceName>.<prefix>, while containers within the same stack use the service name directly. Cross-stack communication is not supported to prevent unintended network exposure.
Volume Lifecycle & Management: Updated behavior for stack configuration regarding volumes. Volumes omitted from a stack request are safely detached but not deleted, ensuring data preservation. Explicit deletion is required via the dedicated volume endpoint. The orphaned flag now clearly indicates that unmounted volumes retain their data until explicitly removed.
Service Configuration & Runtime Behavior:
unless-stopped restart policy and noted that retry limits are accepted but ignored.Stack Identifiers & Service States:
unspecified to the ServiceStatus enum.prefix field in stack responses to emphasize its role as an immutable identifier.shortId field for SSH connections, noting that all API routes require the primary service id.SDK Documentation & Generated Code Cleanup: Comprehensive updates to PHPDoc comments and removal of redundant docblocks to align with the latest API specifications and improve the IDE experience.
For more details, please visit the release page.
The mittwald PHP SDK has been updated to version 2.2.19. This release introduces new features, enhancements, and bug fixes to improve functionality and user experience.
userGetKeys and userGetPlans methods to the AI Hosting client.UserKey and UserPlan schema definitions.403 Forbidden responses for various contract endpoints.400, 403, 404, and 412.412 Precondition Failed responses for pull-image webhooks when stacks are disabled or suspended.BackupRestoreRequested.declare(strict_types=1); from all generated client files to align with updated code generator configurations.For more details, please visit the release page.
The mittwald JavaScript SDK has been updated to version 4.507.0. This release includes an update to the generated client, enhancing the functionality and performance of the SDK. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.507.0.
The mittwald JavaScript SDK has been updated to version 4.506.0. This release includes an update to the generated client, enhancing the functionality and performance of the SDK. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.505.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.505.0.
The mittwald JavaScript SDK version 4.504.0 has been released on October 26, 2026. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub.
This week, the mittwald API introduces several enhancements, including changes to response body formats, the addition of optional and required properties across various endpoints, and the deprecation of certain operations, aimed at improving the overall functionality and user experience.
GET operation at the path /v2/password-policies/{passwordPolicy} has changed from string to object for status 200. This is a breaking change.GET operation at the path /v2/password/policies/{path} has also changed from string to object for status 200. This is a breaking change.POST operation at the path /v2/actions/list-ingresses-compatible-with-certificate now includes an optional property /items/senderLoginProtection in the response for status 200.GET operation at the path /v2/customers/{customerId}/invoice-settings has a new non-success response with status 403.GET operation at the path /v2/domains now includes an optional property /items/ownerVerification in the response for status 200.GET operation at the path /v2/domains/{domainId} now includes an optional property ownerVerification in the response for status 200.GET operation at the path /v2/ingresses now includes an optional property /items/senderLoginProtection in the response for status 200.GET operation at the path /v2/ingresses/{ingressId} now includes an optional property senderLoginProtection in the response for status 200.POST operation at the path /v2/oauth2/token has added a new optional request property refresh_token.POST operation at the path /v2/oauth2/token has added 'subschema #1, subschema #2' to the request body oneOf list.code, grant_type, and redirect_uri have all become optional for the POST operation at the path /v2/oauth2/token.grant_type has a new enum value refresh_token added for the POST operation at the path /v2/oauth2/token.GET operation at the path /v2/password-policies/{passwordPolicy} now includes required properties minComplexity and rules in the response for status 200.GET operation at the path /v2/password/policies/{path} also includes required properties minComplexity and rules in the response for status 200.GET operation at the path /v2/projects/{projectId}/activities has added several schemas to the /items/action response property anyOf list for the response status 200.GET operation at the path /v2/projects/{projectId}/domains now includes an optional property /items/ownerVerification in the response for status 200.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Breaking the response's body type/format changed from 'string'/'' to 'object'/'' for status '200'
added the required property 'minComplexity' to the response with the '200' status
added the required property 'rules' to the response with the '200' status
For details, refer to the GET/v2/
Breaking the response's body type/format changed from 'string'/'' to 'object'/'' for status '200'
added the required property 'minComplexity' to the response with the '200' status
added the required property 'rules' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the new optional request property 'refresh_token'
added 'subschema #1, subschema #2' to the request body 'oneOf' list
the request property 'code' became optional
the request property 'grant_type' became optional
the request property 'redirect_uri' became optional
added the new 'refresh_token' enum value to the request property 'grant_type'
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The mittwald PHP SDK has been updated to version 2.2.18. This release focuses on enhancing API client error handling, specifically for HTTP 403 (Forbidden) responses when accessing invoice settings details. Key improvements include:
InvoiceGetDetailOfInvoiceSettingsForbiddenResponse to handle 403 responses with a standardized schema for validation and JSON serialization.ContractClientImpl to ensure HTTP 403 status codes are correctly routed to the new forbidden response handler.For more details, visit the release page.
The mittwald PHP SDK has been updated to version 2.2.17. This release introduces new features and enhancements aimed at improving security and usability.
senderLoginProtection boolean field has been added to the Ingress schema. When enabled, it restricts email sending from the Ingress and its SubIngresses exclusively to mailboxes within the same project.Policy and PolicyRulesItem schema classes have been introduced to represent structured password validation policies. This feature provides developers with access to minimum password complexity requirements and a list of configurable rule types.PasswordValidationGetPasswordPolicyOKResponse and its deprecated V2 counterpart have been updated to return a strongly typed Policy object instead of a raw string. This change enhances type safety and provides direct access to policy rules and complexity metrics.For more details, please visit the release page.
The mittwald PHP SDK has been updated to version 2.2.16. This release focuses on schema and documentation enhancements to improve integration and developer experience. Key updates include:
monthlyTokens and requestsPerMinute in the AI Hosting Order schema, emphasizing the need for exact matches with available articles via the /articles endpoint.machineType field in the Machine Type Specification schema, aligning it with article matching requirements.For more details, visit the release page.
The mittwald PHP SDK has released version v2.2.15, which introduces new features and updates to enhance functionality and user experience.
Activity Log Schemas for Backup Operations: This release includes a comprehensive suite of auto-generated PHP schema classes for modeling backup-related activity log events. These schemas offer structured data handling, JSON schema validation, serialization capabilities, and immutable builder methods. Supported activity log events include:
backup.created and backup.deleted (covering standard, export, and schedule deletions)backup.description-updatedbackup.expiration-updatedbackup.export-requestedbackup.restore-requestedbackup.schedule-createdbackup.schedule-interval-updatedbackup.schedule-ttl-updatedEach event type is paired with dedicated Changes, Parameters, and Name classes, enforcing strict typing and providing utilities for seamless API integration.
resendContactVerificationEmail() method in DomainClient is now deprecated. Users are advised to migrate to the POST /v2/domains/{domainId}/actions/resend-email endpoint.resendDomainEmail() operation has been expanded to clarify its scope and constraints, including details on when a 412 Precondition Failed error will be returned.For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.503.0. This release includes the following feature:
For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.503.0.
The mittwald JavaScript SDK has been updated to version 4.502.0. This release includes the following feature:
For more details, please visit the release page.
This week's changelog for the mittwald API includes the removal of an API path without deprecation, the addition of new optional request parameters and properties across various endpoints, and the introduction of new enum values in response properties, enhancing the overall functionality and flexibility of the API.
/v2/legacy-tariff-change has been removed without deprecation for the POST operation relocation-create-legacy-tariff-change. This is a breaking change.GET operations database-get-mysql-database (/v2/mysql-databases/{mysqlDatabaseId}) and database-get-redis-database (/v2/redis-databases/{redisDatabaseId}) with a response status of '200'.GET operations database-list-mysql-databases (/v2/projects/{projectId}/mysql-databases) and database-list-redis-databases (/v2/projects/{projectId}/redis-databases) with a response status of '200'.GET operation app-list-appinstallations-for-user (/v2/app-installations) has received several updates: the new optional request parameters 'autoUpdatesActivated' and 'autoUpdatesSupported' have been added, along with the optional response property '/items/lastAutoUpdateFailedAt'.GET operation app-get-appinstallation (/v2/app-installations/{appInstallationId}) has had the optional response property 'lastAutoUpdateFailedAt' added.GET operation app-list-appversions (/v2/apps/{appId}/versions) has had the optional response property '/items/updateConstraint' added.GET operation app-get-appversion (/v2/apps/{appId}/versions/{appVersionId}) has had the optional response property 'updateConstraint' added.GET operation app-list-update-candidates-for-appversion (/v2/apps/{appId}/versions/{baseAppVersionId}/update-candidates) has had the optional response property '/items/updateConstraint' added.GET operation ai-hosting-customer-get-usage (/v2/customers/{customerId}/ai-hosting) has had the optional response property 'suspended' added.GET operation ai-hosting-customer-get-plans (/v2/customers/{customerId}/ai-hostings) has had the optional response property 'plans/items/suspended' added.GET operation ai-hosting-customer-get-plan (/v2/customers/{customerId}/ai-hostings/{planId}) has had the optional response property 'suspended' added.GET operation project-list-customer-projects (/v2/customers/{customerId}/projects) has had the optional response property '/items/primaryIpAddresses' added.POST operation domain-check-domain-transferability (/v2/domain-transferable) has had the required property 'reasons/premiumDomain' added to the response with a status of '200'.POST operation file-create-file (/v2/files) has had a non-success response with the status '413' added.POST operation database-copy-mysql-database (/v2/mysql-databases/{mysqlDatabaseId}/actions/copy) has had the new optional request property 'user/description' added.GET operation notifications-get-notification-settings (/v2/notification-settings) has been added as a new endpoint.PATCH operation notifications-adjust-notification-message-type-settings (/v2/notification-settings/{messageType}) has been added as a new endpoint.GET operation notifications-list-notifications (/v2/notifications) has had the new optional request parameters 'order' and 'sort' added.PUT operation notifications-read-notification has been removed and replaced with notifications-update-notification-status (/v2/notifications/{notificationId}/status).GET operation project-list-projects (/v2/projects) has had the optional response property '/items/primaryIpAddresses' added.GET operation project-get-project (/v2/projects/{projectId}) has had the optional response property 'primaryIpAddresses' added.GET operation project-list-project-activities (/v2/projects/{projectId}/activities) has had several schemas added to the '/items/action' response property 'anyOf' list for the response status '200'.GET operation ai-hosting-project-get-usage (/v2/projects/{projectId}/ai-hosting) has had the optional response property 'suspended' added.GET operation ai-hosting-project-get-plans (/v2/projects/{projectId}/ai-hostings) has had the optional response property 'plans/items/suspended' added.GET operation ai-hosting-project-get-plan (/v2/projects/{projectId}/ai-hostings/{planId}) has had the optional response property 'suspended' added.GET operation app-list-appinstallations (/v2/projects/{projectId}/app-installations) has had the new optional request parameters 'autoUpdatesActivated' and 'autoUpdatesSupported' added, along with the optional response property '/items/lastAutoUpdateFailedAt'.POST operation database-create-mysql-database (/v2/projects/{projectId}/mysql-databases) has had the new optional request property 'user/description' added.GET operation sftp-user-list-sftp-users (/v2/projects/{projectId}/sftp-users) has had the optional response property '/items/detailedPublicKeys' added.POST operation sftp-user-create-sftp-user (/v2/projects/{projectId}/sftp-users) has had the optional response property 'detailedPublicKeys' added with a status of '201'.GET operation ssh-user-list-ssh-users (/v2/projects/{projectId}/ssh-users) has had the optional response property '/items/detailedPublicKeys' added.POST operation ssh-user-create-ssh-user (/v2/projects/{projectId}/ssh-users) has had the optional response property 'detailedPublicKeys' added with a status of '201'.GET operation project-list-servers (/v2/servers) has had the optional response property '/items/primaryIpAddresses' added.GET operation project-get-server (/v2/servers/{serverId}) has had the optional response property 'primaryIpAddresses' added.GET operation sftp-user-get-sftp-user (/v2/sftp-users/{sftpUserId}) has had the optional response property 'detailedPublicKeys' added.GET operation ssh-user-get-ssh-user (/v2/ssh-users/{sshUserId}) has had the optional response property 'detailedPublicKeys' added.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the unknown operation relocation-create-legacy-tariff-change endpoint.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the new optional 'query' request parameter 'autoUpdatesActivated'
added the new optional 'query' request parameter 'autoUpdatesSupported'
added the optional property '/items/lastAutoUpdateFailedAt' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
For details, refer to the unknown operation notifications-get-notification-settings endpoint.
For details, refer to the unknown operation notifications-adjust-notification-message-type-settings endpoint.
added the new optional 'query' request parameter 'order'
added the new optional 'query' request parameter 'sort'
For details, refer to the GET/v2/
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the new optional 'query' request parameter 'autoUpdatesActivated'
added the new optional 'query' request parameter 'autoUpdatesSupported'
added the optional property '/items/lastAutoUpdateFailedAt' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The mittwald PHP SDK has released version 2.2.14, which includes several new features, deprecations, and updates. This release focuses on improving error handling, enhancing status tracking, and implementing important security updates.
CreateFileRequestEntityTooLargeResponse class.suspended boolean field to CustomerPlan and ProjectPlan schemas to track suspension status, including validation and JSON serialization/deserialization support.key field in the AIHosting/Key schema is now deprecated. Future responses will not expose the secret API key, and clients should prepare to transition away from using this field.FileClientImpl to route 413 status codes to the new error response handler.For more details, visit the release page.
The mittwald PHP SDK has been updated to version 2.2.13. This release introduces new features and updates to enhance domain transferability checks and network visibility for servers and projects.
premiumDomain boolean field has been added to domain transfer checks. This flag indicates when a registry charges a premium price for transferring a domain. Note that premium domains are not currently supported for transfer operations.primaryIpAddresses attribute has been added to the Project, ProjectListItem, and Server models. This feature provides access to the primary public IPv4 and IPv6 addresses, facilitating easier network configuration.CheckDomainTransferability response classes have been updated to include logic for the premiumDomain property.PrimaryIpAddresses schema class has been introduced, featuring nullable v4 and v6 string properties with JSON schema validation.primaryIpAddresses feature has been integrated into relevant models, with corresponding methods for manipulation and serialization.For more details, visit the release page.
The latest release of the mittwald PHP SDK, v2.2.12, introduces enhancements to the activity log schema, focusing on comprehensive tracking for SSH and SFTP user operations. This update includes new event types to capture the lifecycle of SSH/SFTP users, such as creation, modification, and deletion, along with detailed before/after state snapshots for audit purposes.
The release supports the following new SSH/SFTP user activity log events:
SshUserCreated: Logs the creation of new SSH users.SftpUserCreated: Logs the creation of new SFTP users.SshUserDeleted: Tracks the deletion or expiration of SSH/SFTP users.SshUserActiveUpdated: Monitors changes to the active/inactive status of users.SshUserDescriptionUpdated: Captures updates to user descriptions.SshUserPasswordUpdated: Logs password configuration changes.SshUserPublicKeysUpdated: Tracks updates to user public keys.SshUserExpiryUpdated: Monitors changes to user expiration dates.SftpUserAccessLevelUpdated: Tracks modifications to SFTP user access levels (e.g., read vs full).SftpUserDirectoriesUpdated: Records updates to SFTP user directory mappings.These updates are seamlessly integrated with the existing LogEntry structure to enhance detailed activity monitoring.
The mittwald PHP SDK has released version 2.2.11, introducing several enhancements and improvements. This release focuses on expanding the notification API and adding comprehensive support for activity log membership events. Key updates include:
Notification API Enhancements:
autoUpdatesActivated and autoUpdatesSupported for app installation listings.notificationsUpdateNotificationStatus.Activity Log Membership Events:
Changes and Parameters objects for detailed state comparisons.Improvements & Refactoring:
Migration Notes:
notificationsUpdateNotificationStatus for managing notification statuses.For more details, visit the release page.
The latest release of the mittwald PHP SDK, version 2.2.10, introduces significant changes and new features. This release removes the legacy tariff change relocation functionality from the Relocation client and introduces a new ScopedToken schema to support restricted authentication tokens within the Signup module.
createLegacyTariffChange method and all related request/response classes have been removed from RelocationClient and RelocationClientImpl.ScopedToken schema for interacting with scoped authentication tokens.createdAt and createdBy fields.For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.501.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.
The mittwald JavaScript SDK version 4.500.2 has been released on October 16, 2026. This update primarily focuses on bug fixes, specifically addressing security issues by bumping runtime dependencies to their latest minor or patch versions. Notable updates include security fixes for dependencies such as axios and path-to-regexp. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK version 4.500.1 has been released. This update includes a bug fix in the generator, where declare namespace is now emitted instead of declare module. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.500.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.500.0.
The mittwald JavaScript SDK has been updated to version 4.499.1. This release includes a version bump for the package root. For more details, you can view the release on GitHub: mittwald/api-client-js 4.499.1.
The mittwald JavaScript SDK has been updated to version 4.499.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details on the changes and improvements, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.498.1. This release includes a version bump for the package root. For more details, you can view the release on GitHub: mittwald/api-client-js 4.498.1.
The mittwald JavaScript SDK has been updated to version 4.498.0. This release includes a significant update to dependencies, with major version bumps across the board. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.498.0.
The mittwald JavaScript SDK has been updated to version 4.497.1. This release primarily involves a version bump for the package root, with no additional changes or new features introduced. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.497.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.
The mittwald JavaScript SDK has been updated to version 4.496.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.
The mittwald JavaScript SDK has been updated to version 4.495.1. This release primarily involves a version bump for the package root, with no additional changes or features introduced. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.495.0. This release introduces a new feature in the generator, which now emits @deprecated JSDoc annotations for type aliases and parameters. This enhancement addresses issues raised in #297 and closes #166.
For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.495.0.
The mittwald JavaScript SDK has been updated to version 4.494.0. This release includes the following feature:
For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.493.1. This release is a version bump only for the package root, with no additional changes or new features introduced. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.493.0. This release includes the following feature:
For more details, please visit the release page.
The mittwald JavaScript SDK has been updated to version 4.492.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the full release notes on GitHub.
This week, the mittwald API introduces a new endpoint for rotating keys, adds optional properties to various invoice responses, and includes non-success status responses for specific operations.
POST at the path /v2/customers/{customerId}/ai-hosting-keys/{keyId}/actions/rotate.POST at the path /v2/projects/{projectId}/ai-hosting-keys/{keyId}/actions/rotate.GET operation invoice-list-customer-invoices at the path /v2/customers/{customerId}/invoices now includes two optional properties: /items/cancellation/xRechnungId and /items/xRechnungId.GET operation deprecated-invoice-detail-of-invoice at the path /v2/customers/{customerId}/invoices/{invoiceId} now includes two optional properties: cancellation/xRechnungId and xRechnungId.GET operation invoice-detail at the path /v2/invoices/{invoiceId} now includes two optional properties: cancellation/xRechnungId and xRechnungId.fileType has been added to the GET operation invoice-get-file-access-token at the path /v2/customers/{customerId}/invoices/{invoiceId}/file-access-token.PUT operation notifications-read-notification at the path /v2/notifications/{notificationId}/status now includes a non-success response with the status 403.GET operation project-list-project-activities at the path /v2/projects/{projectId}/activities has had multiple schemas added to the /items/action response property anyOf list for the response status 200.POST operation dns-create-dns-zone-file-import at the path /v2/projects/{projectId}/dns-zone-imports now includes a non-success response with the status 409.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the POST/v2/
added the optional property '/items/cancellation/xRechnungId' to the response with the '200' status
added the optional property '/items/xRechnungId' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'cancellation/xRechnungId' to the response with the '200' status
added the optional property 'xRechnungId' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the optional property 'cancellation/xRechnungId' to the response with the '200' status
added the optional property 'xRechnungId' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
The mittwald PHP SDK has been updated to version 2.2.9. This release introduces several new features and enhancements:
gracePeriod parameter, allowing the old secret to remain valid for a specified duration (e.g., 24h, 1m) alongside the new one before being revoked.400, 403, 404, 429) with structured error payloads.API Additions:
AIHostingClient::customerRotateKey(CustomerRotateKeyRequest $request): CustomerRotateKeyOKResponseAIHostingClient::projectRotateKey(ProjectRotateKeyRequest $request): ProjectRotateKeyOKResponseGenerated Types:
CustomerRotateKey and ProjectRotateKey namespaces. These include request builders with automatic URL construction, request body models with gracePeriod support, and dedicated response containers for success and error states, complete with validation and JSON serialization utilities.For more details, please visit the release page.
The mittwald PHP SDK has been updated to version 2.2.8. This release introduces new activity log schemas, enhancing the tracking and handling of container lifecycle and configuration changes. The update includes comprehensive auto-generated PHP schema classes for container activity log events, providing structured data models for both before and after states, along with contextual parameters and strict JSON schema validation.
container.started, container.stopped, container.restarted, and container.recreated.Mittwald\\ApiClient\\Generated\\V2\\Schemas\\Activitylog.For more details, visit the release page.
The mittwald PHP SDK has been updated to version 2.2.7. This release introduces several enhancements and new features:
Notification API Enhancements:
403 Forbidden HTTP responses in the NotificationsReadNotification endpoint.NotificationsReadNotificationForbiddenResponse class to parse, validate, and serialize forbidden error payloads.Activity Log: Project Event Tracking:
ProjectCreated and ProjectDescriptionUpdated schema classes to capture project lifecycle events.After and Before state classes for comparing pre- and post-modification data.ParameterProperty and Name enum models for structured metadata representation.LogEntry type unions, match statements, and JSON serialization logic to support the new action types.For more details, visit the release page.
The mittwald PHP SDK has been updated to version 2.2.6. This release focuses on enhancing the database client schema, particularly for MySQL user password requirements. Key updates include:
Database Client Updates: The V2 Database client schema now explicitly documents MySQL user password requirements for both creation and update operations. This ensures developers are aware of complexity rules, character restrictions, and minimum length requirements when using the MySQL user API.
Schema & Documentation Improvements:
description fields for the password parameter in CreateMySqlUser and CreateMySqlUserWithDatabase schemas.UpdateMysqlUserRequest and UpdateMysqlUserRequestBody.$password properties across all affected request and schema classes.For more details, visit the release page.
The mittwald PHP SDK version 2.2.5 has been released, introducing several enhancements and new features. You can view the full release details here.
Invoice File Access Token Enhancement:
fileType enum (PDF, XRECHNUNG) for InvoiceGetFileAccessTokenRequest, defaulting to PDF.InvoiceGetFileAccessTokenRequestFileType enum with updated request builders, getters, and setters.DNS Zone Import Conflict Handling:
DnsCreateDnsZoneFileImportConflictResponse to manage 409 Conflict HTTP status codes during DNS zone imports.DomainClientImpl to map 409 responses to the new conflict response class.XRechnung ID Support:
xRechnungId (UUID) field to Invoice and Cancellation schema objects for tracking XRechnung XML files.Documentation & Code Quality:
These updates aim to enhance functionality and improve the handling of specific scenarios within the SDK.
The mittwald JavaScript SDK has been updated to version 4.491.0. This release includes the following feature:
For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.491.0.
The mittwald JavaScript SDK has been updated to version 4.490.0. This release includes an update to the generated client, enhancing the functionality and performance of the SDK. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.489.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.
The mittwald JavaScript SDK has been updated to version 4.488.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.
The mittwald JavaScript SDK has been updated to version 4.487.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.
The mittwald JavaScript SDK has been updated to version 4.486.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.
The mittwald JavaScript SDK has been updated to version 4.485.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.
The mittwald JavaScript SDK has been updated to version 4.484.0. This release includes the following feature:
For more details, please visit the release page.
The mittwald JavaScript SDK version 4.483.1 has been released. This update includes performance improvements specifically in the models, where all resources of an invalidated URL are refreshed in one pass. This enhancement is aimed at optimizing resource handling and improving overall efficiency.
For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.483.1.
The mittwald JavaScript SDK has been updated to version 4.483.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the full release notes on GitHub.
The mittwald JavaScript SDK has been updated to version 4.482.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.482.0.
The mittwald JavaScript SDK has been updated to version 4.481.0. This release includes the following feature:
For more details, you can view the release on GitHub.
This week, the mittwald API introduces several enhancements, including the addition of optional properties to existing responses, new endpoints for managing DNS zone-file imports, and expanded activity log schemas for project activities.
/items/description has been added to the response with the 200 status for the GET operation on the path /v2/apps (List Apps).description has been added to the response with the 200 status for the GET operation on the path /v2/apps/{appId} (Get an App).GET operation on the path /v2/dns-zone-imports/{zoneFileImportId} to get the status of a DNS zone-file import job.GET operation on the path /v2/projects/{projectId}/dns-zone-imports to list DNS zone-file import jobs belonging to a project.POST operation on the path /v2/projects/{projectId}/dns-zone-imports to import a DNS zone file into a project, or preview it with a dry-run.POST operation on the path /v2/projects/{projectId}/dns-zones to create a DNSZone for a verified Ingress in a project.anyOf list for the 200 status has been updated for the GET operation on the path /v2/projects/{projectId}/activities to include multiple new activity log schemas.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
The mittwald PHP SDK has released version 2.2.4, which introduces a comprehensive set of auto-generated PHP schema classes for the V2 API Client's Activity Log, focusing on Cronjob event tracking. These new models provide strict type-safe representations for lifecycle events and configuration modifications, allowing developers to accurately parse, validate, and serialize activity log payloads with built-in JSON Schema validation and immutable state management.
CronjobCreated, CronjobDeleted, and CronjobExecution have been added to track lifecycle and execution events.CronjobActiveUpdated and CronjobCommandUpdated have been introduced to handle configuration updates.*ChangesAfter and *ChangesBefore classes for tracking state differences, enumerations for standardized event naming, and built-in methods for serialization/deserialization.These classes are auto-generated by the mittwald/api-client-builder package, featuring strict type declarations and immutable state management.
For more details, visit the release page.
The mittwald PHP SDK has been updated to version 2.2.3, introducing significant enhancements and new features. This release focuses on improving DNS zone file management and DNS zone creation for verified Ingresses.
DNS Zone File Import Support:
dnsCreateDnsZoneFileImport, dnsGetDnsZoneFileImport, and dnsListDnsZoneFileImports.CreateZoneFileImportResponse, ZoneFileImport, and ZoneImportPreview are introduced.DNS Zone Creation for Verified Ingress:
dnsCreateProjectDnsZone for creating DNS zones within a project for verified Ingresses, determining root or subzone provisioning automatically.DnsCreateDnsZone operation is deprecated, replaced by DnsCreateProjectDnsZone and DnsCreateDnsZoneFileImport.description field added to the App Schema for localized descriptions.MailClient and UserClient to reflect changes in asynchronous workflows.For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.480.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.
The mittwald JavaScript SDK has been updated to version 4.479.0. This release includes a feature update with an updated generated client. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.478.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.
The mittwald JavaScript SDK has been updated to version 4.477.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub: mittwald/api-client-js 4.477.0.
The mittwald JavaScript SDK version 4.476.0 has been released. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.475.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.
The mittwald JavaScript SDK has been updated to version 4.474.0. This release includes an update to the generated client, enhancing the functionality and performance of the SDK. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.473.0. This release includes the following feature:
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.472.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, the mittwald API introduces several changes, including the addition of new optional request parameters and properties, the requirement of request bodies for specific endpoints, and updates to response properties, enhancing the overall functionality and flexibility of the API.
/anyOf[#/components/schemas/de.mittwald.v1.marketplace.UnpublishedExtension]/context became optional for the status 200 in the GET operation for the path /v2/extensions/{extensionId}. This is a breaking change.POST operations for the paths /v2/users/self/spotlights/{spotlightId} and /v2/users/self/spotlights/{spotlightId}/feedback. This is a breaking change.Accept-Language for the GET operations for the paths /v2/app-installations/{appInstallationId}/error-analysis, /v2/container-image-config, and /v2/stacks/{stackId}/services/{serviceId}/log-analysis.projectId for the POST operation for the path /v2/domain-transferable.reasons/enabledIngressInOtherProject to the response with the 200 status for the POST operation for the path /v2/domain-transferable.GET operations for the paths /v2/leaked-passwords/{passwordHashPrefix} and /v2/oauth2/clients/{oauthClientId}.|^\+([0-9]{2,3}|1)-[0-9]{2,5}-[0-9]+$ from the request property contact/phoneNumber for the POST operation for the path /v2/relocation.x-description and x-update-schedule for the PATCH operation for the path /v2/stacks/{stackId}.owner became optional for the POST operation for the path /v2/users/self/spotlights/{spotlightId}/feedback.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the GET/v2/
For details, refer to the POST/v2/
Breaking request body became required
the request property 'owner' became optional
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the new optional request property 'projectId'
added the required property 'reasons/enabledIngressInOtherProject' to the response with the '200' status
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
added the new optional request property 'x-description'
added the new optional request property 'x-update-schedule'
For details, refer to the PATCH/v2/
For details, refer to the GET/v2/
The mittwald PHP SDK has released version 2.2.2, which introduces new features, enhancements, and adjustments to improve user experience and functionality.
passwordHashPrefix (up to 5 characters), the API returns all matching password hashes with their prevalence counts, allowing applications to warn users about leaked credentials.projectId to specify the target project, and the response includes enabledIngressInOtherProject, which indicates if an enabled ingress for the domain exists in another project.phoneNumber field in relocation requests have been relaxed by removing a strict regex constraint, allowing more flexible phone number formats.For more details, visit the release page.
The mittwald PHP SDK has been updated to version 2.2.1. This release introduces several new features and enhancements, particularly focusing on Marketplace OAuth2 client management, webhook execution resumption, and User spotlight tracking. Additionally, it includes improvements in extension listing capabilities and updates to request/response schemas for container service declarations.
Marketplace Enhancements:
contributorGetOauthClient for detailed OAuth2 client information.extensionResumeWebhookExecutionForExtensionInstance to resume suspended webhook executions.contract.interactionRequired for extension instances.User Spotlight Management:
getSpotlightInfo to fetch spotlight status and decision details.spotlightFeedback for submitting user feedback and decisions.spotlightUsage for recording usage metrics.description and updateSchedule are deprecated in favor of x-description and x-update-schedule.restartPolicy in service declarations is deprecated; use restart instead.owner field in spotlight feedback and usage requests is deprecated.context field in UnpublishedExtension is now optional.For more details, please refer to the release page.
The mittwald JavaScript SDK has been updated to version 4.471.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.
The mittwald JavaScript SDK has been updated to version 4.470.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.
The mittwald JavaScript SDK has been updated to version 4.469.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the release notes on GitHub.
The mittwald JavaScript SDK has been updated to version 4.468.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.468.0.
The mittwald JavaScript SDK has been updated to version 4.467.0. This release introduces a new feature that allows the acceptance of JavaScript Date objects for date-time request values, addressing issues raised in #209. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.466.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.
During the week of September 11 to September 18, 2026, the mittwald API introduced several significant changes, including the addition of new endpoints for managing GDPR contracts and authentication, the removal of deprecated paths, updates to response properties, and the requirement of certain request parameters.
domainIdentifier request parameter in the DELETE operation for deleting a certificate has become required, which is a breaking change. The endpoint is DELETE /accounts/{accountIdentifier}/domains/{domainIdentifier}/certificate.GET operation to list application tokens has become nullable, and the property type for /items/crdate has changed from string/date-time to integer for status 200. The endpoint is GET /authentication/tokens.crdate response property type has changed from string/date-time to integer for status 201 in the POST operation for creating an application token. The endpoint is POST /authentication/tokens.POST /gdpr/contracts/{contractIdentifier}/actions/acceptPOST /gdpr/contracts/{contractIdentifier}/actions/mailPOST /gdpr/contracts/{contractIdentifier}/actions/pdfPOST /gdpr/pdfs/{pdfIdentifier}/actions/downloadcontract/items/payload/statusFields/editLock has become nullable for status 200 in the GET operation for menu generation, along with similar changes for left, support, and top properties. The endpoint is GET /menu.POST operation for authenticating with a token has been added at the endpoint POST /authenticate/token.401 has been added for the GET operation to list application tokens, the POST operation to create an application token, and the DELETE operation to delete an application token. The endpoints are GET /authentication/tokens, POST /authentication/tokens, and DELETE /authentication/tokens/{uuid} respectively.200 for the GET operation to retrieve GDPR contracts, including client/creationDate, client/type, recipient/creationDate, recipient/type, tom/content, and tom/creationDate. The endpoint is GET /gdpr/contracts.200 for the GET operation to retrieve GDPR contracts, including client/city, client/houseNumber, client/mail, client/name, client/street, client/zipCode, recipient/city, recipient/houseNumber, recipient/mail, recipient/name, recipient/street, and recipient/zipCode. The endpoint is GET /gdpr/contracts.POST /gdpr/contracts/{contractIdentifier}/actions/acceptPOST /gdpr/contracts/{contractIdentifier}/actions/mailPOST /gdpr/contracts/{contractIdentifier}/actions/pdfPOST /gdpr/pdfs/{pdfIdentifier}/actions/downloadGET operation for retrieving navigation meta has a new endpoint at GET /menu-meta.oneOf list for the response properties contract/items/payload/statusFields/editLock, left/items/payload/statusFields/editLock, support/items/payload/statusFields/editLock, and top/items/payload/statusFields/editLock has had certain subschemas removed for the response status 200. The endpoint is GET /menu.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the DELETE/accounts/
Breaking the response's body became nullable
Breaking the '/items/crdate' response's property type/format changed from 'string'/'date-time' to 'integer'/'' for status '200'
added the non-success response with the status '401'
For details, refer to the GET/authentication/
Breaking the 'crdate' response's property type/format changed from 'string'/'date-time' to 'integer'/'' for status '201'
added the new optional request property 'token'
added the non-success response with the status '401'
For details, refer to the POST/authentication/
Breaking api path removed without deprecation
endpoint added
For details, refer to the POST/gdpr/
Breaking api path removed without deprecation
endpoint added
For details, refer to the POST/gdpr/
Breaking api path removed without deprecation
endpoint added
For details, refer to the POST/gdpr/
Breaking api path removed without deprecation
endpoint added
For details, refer to the POST/gdpr/
Breaking the response property 'contract/items/payload/statusFields/editLock' became nullable for the status '200'
Breaking the response property 'left/items/payload/statusFields/editLock' became nullable for the status '200'
Breaking the response property 'support/items/payload/statusFields/editLock' became nullable for the status '200'
Breaking the response property 'top/items/payload/statusFields/editLock' became nullable for the status '200'
Breaking the 'contract/items/payload/statusFields/editLock' response's property type/format changed from ''/'' to 'string'/'' for status '200'
Breaking the 'left/items/payload/statusFields/editLock' response's property type/format changed from ''/'' to 'string'/'' for status '200'
Breaking the 'support/items/payload/statusFields/editLock' response's property type/format changed from ''/'' to 'string'/'' for status '200'
Breaking the 'top/items/payload/statusFields/editLock' response's property type/format changed from ''/'' to 'string'/'' for status '200'
removed 'subschema #1, subschema #2' from the 'contract/items/payload/statusFields/editLock' response property 'oneOf' list for the response status '200'
removed 'subschema #1, subschema #2' from the 'left/items/payload/statusFields/editLock' response property 'oneOf' list for the response status '200'
removed 'subschema #1, subschema #2' from the 'support/items/payload/statusFields/editLock' response property 'oneOf' list for the response status '200'
removed 'subschema #1, subschema #2' from the 'top/items/payload/statusFields/editLock' response property 'oneOf' list for the response status '200'
For details, refer to the GET/menu endpoint.
Breaking api path removed without deprecation
endpoint added
For details, refer to the GET/menu-meta endpoint.
For details, refer to the POST/authenticate/
For details, refer to the DELETE/authentication/
added the optional property '/items/client/creationDate' to the response with the '200' status
added the optional property '/items/client/type' to the response with the '200' status
added the optional property '/items/recipient/creationDate' to the response with the '200' status
added the optional property '/items/recipient/type' to the response with the '200' status
added the optional property '/items/tom/content' to the response with the '200' status
added the optional property '/items/tom/creationDate' to the response with the '200' status
added the required property '/items/client/city' to the response with the '200' status
added the required property '/items/client/houseNumber' to the response with the '200' status
added the required property '/items/client/mail' to the response with the '200' status
added the required property '/items/client/name' to the response with the '200' status
added the required property '/items/client/street' to the response with the '200' status
added the required property '/items/client/zipCode' to the response with the '200' status
added the required property '/items/recipient/city' to the response with the '200' status
added the required property '/items/recipient/houseNumber' to the response with the '200' status
added the required property '/items/recipient/mail' to the response with the '200' status
added the required property '/items/recipient/name' to the response with the '200' status
added the required property '/items/recipient/street' to the response with the '200' status
added the required property '/items/recipient/zipCode' to the response with the '200' status
For details, refer to the GET/gdpr/
added the optional property 'client/creationDate' to the response with the '201' status
added the optional property 'client/type' to the response with the '201' status
added the optional property 'recipient/creationDate' to the response with the '201' status
added the optional property 'recipient/type' to the response with the '201' status
added the optional property 'tom/content' to the response with the '201' status
added the optional property 'tom/creationDate' to the response with the '201' status
added the required property 'client/city' to the response with the '201' status
added the required property 'client/houseNumber' to the response with the '201' status
added the required property 'client/mail' to the response with the '201' status
added the required property 'client/name' to the response with the '201' status
added the required property 'client/street' to the response with the '201' status
added the required property 'client/zipCode' to the response with the '201' status
added the required property 'recipient/city' to the response with the '201' status
added the required property 'recipient/houseNumber' to the response with the '201' status
added the required property 'recipient/mail' to the response with the '201' status
added the required property 'recipient/name' to the response with the '201' status
added the required property 'recipient/street' to the response with the '201' status
added the required property 'recipient/zipCode' to the response with the '201' status
For details, refer to the POST/gdpr/
added the optional property 'client/creationDate' to the response with the '200' status
added the optional property 'client/type' to the response with the '200' status
added the optional property 'recipient/creationDate' to the response with the '200' status
added the optional property 'recipient/type' to the response with the '200' status
added the optional property 'tom/content' to the response with the '200' status
added the optional property 'tom/creationDate' to the response with the '200' status
added the required property 'client/city' to the response with the '200' status
added the required property 'client/houseNumber' to the response with the '200' status
added the required property 'client/mail' to the response with the '200' status
added the required property 'client/name' to the response with the '200' status
added the required property 'client/street' to the response with the '200' status
added the required property 'client/zipCode' to the response with the '200' status
added the required property 'recipient/city' to the response with the '200' status
added the required property 'recipient/houseNumber' to the response with the '200' status
added the required property 'recipient/mail' to the response with the '200' status
added the required property 'recipient/name' to the response with the '200' status
added the required property 'recipient/street' to the response with the '200' status
added the required property 'recipient/zipCode' to the response with the '200' status
For details, refer to the GET/gdpr/
During the week of September 11 to September 18, 2026, the mittwald API introduced several new endpoints, including the ability to resume webhook execution for extension instances, retrieve spotlight information, and submit spotlight usage and feedback, along with a new optional request parameter for listing extension instances.
POST at the path /v2/contributors/{contributorId}/extensions/{extensionId}/extension-instances/{extensionInstanceId}/actions/resume-webhook-execution.contract.interactionRequired has been added to the GET operation for listing ExtensionInstances at the path /v2/extension-instances.GET at the path /v2/users/self/spotlights/{spotlightId}.POST at the path /v2/users/self/spotlights/{spotlightId}.POST at the path /v2/users/self/spotlights/{spotlightId}/feedback.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
The mittwald JavaScript SDK has been updated to version 4.465.0. This release includes a feature update with an updated generated client. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.464.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.
The mittwald JavaScript SDK has been updated to version 4.463.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.463.0.
The mittwald JavaScript SDK has been updated to version 4.462.0. This release introduces a new feature in the generator, adding support for the JSON Schema const keyword. This enhancement addresses issues raised in #283 and is detailed in commit 56ae2db.
For more information, visit the release page.
This week's update to the mittwald API includes changes to the response structure for the /v2/authenticate-mfa endpoint, the addition of new endpoints for AI hosting plan billing periods and usage statistics, and the introduction of a new enum value for VAT ID validation states.
The POST /v2/authenticate-mfa operation has undergone several breaking changes:
#/components/schemas/de.mittwald.v1.commons.ValidationErrors and #/components/schemas/de.mittwald.v1.commons.Error in the 'anyOf' list for status '400'.The GET /v2/customers operation has a new enum value 'unsupported' added to the vatIdValidationState response property for status '200'.
The GET /v2/customers/{customerId} operation has a new enum value 'unsupported' added to the vatIdValidationState response property for status '200'.
Two new endpoints have been added:
GET /v2/customers/{customerId}/ai-hostings/{planId}/billing-periods to list the contract months of an AI hosting plan.GET /v2/customers/{customerId}/ai-hostings/{planId}/usage to get aggregated token usage statistics for an AI hosting plan of a customer.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Breaking the response's body type/format changed from 'object'/'' to ''/'' for status '400'
Breaking removed the required property 'type' from the response with the '400' status
Breaking removed the required property 'validationErrors' from the response with the '400' status
removed the optional property 'message' from the response with the '400' status
added '#/components/schemas/de.mittwald.v1.commons.ValidationErrors, #/components/schemas/de.mittwald.v1.commons.Error' to the response body 'anyOf' list for the response status '400'
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The latest release of the mittwald PHP SDK, version v2.1.220, introduces improvements in the API client, specifically in the handling of MFA authentication errors. The AuthenticateMfaBadRequestResponse class has been removed, and now HTTP status codes 400 and 408 during MFA authentication consistently return UntypedResponse. This update aims to streamline error handling and remove unused generated classes, ensuring a more standardized authentication process.
For more details, visit the release page.
The latest release of the mittwald PHP SDK, version 2.1.219, introduces significant enhancements and bug fixes. This update focuses on improving the AI Hosting API and clarifying database API documentation.
planGetBillingPeriods, allows users to retrieve contract months for a given plan, including token limits and period status.planGetUsageStats method provides aggregated token usage data, offering insights into daily token breakdowns and usage per API key.accessIpMask field has been updated across several classes to clarify that it currently has no effect, reducing potential confusion during implementation.For more details, visit the release page.
The mittwald PHP SDK has been updated to version v2.1.218. This release introduces enhancements to the customer VAT ID validation process. The SDK now supports the new unsupported validation state, which allows for accurate handling of API responses when VAT ID validation cannot be processed, is outside supported regions, or requires alternative verification methods.
Key Changes:
unsupported to the validation state options in the Customer schema.unsupported case to the CustomerVatIdValidationState enum.For more details, visit the release page.
The latest release of the mittwald PHP SDK, version v2.1.217, introduces significant enhancements to the AI Hosting client capabilities. This update includes comprehensive plan lifecycle management, improved key filtering, and pagination support.
customerDeclareProfile for creating AI hosting profiles.customerGetPlan and customerGetPlans for customer-specific plans; projectGetPlan and projectGetPlans for project-specific plans.customerUpdatePlan for renaming or updating plan descriptions.planId is now required for key creation operations.planId.limit, skip, and page parameters.customerGetUsage and projectGetUsage are deprecated in favor of new plan-specific routes. Existing integrations will continue to function but will emit deprecation notices.For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.461.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.461.0.
The mittwald JavaScript SDK has been updated to version 4.460.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.
The mittwald JavaScript SDK has been updated to version 4.459.0. This release includes the following feature:
For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.458.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/api-client-js/releases/tag/4.458.0.
The mittwald JavaScript SDK version 4.457.1 has been released. This update includes a bug fix that widens the peer dependency range for @mittwald/react-use-promise to include versions 3.x and 4.x. This change addresses issue #293 and is documented in pull request #294. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.457.0. This release includes the following feature:
For more details, you can view the full release notes on GitHub.
This week's changelog for the mittwald API includes the addition of new endpoints, required properties, and optional request parameters, as well as the removal of certain success responses and media types, enhancing the overall functionality and usability of the API.
The success response with the status 200 has been removed for the POST operations at the following endpoints:
POST /v2/app-installations/{appInstallationId}/actions/detach-stagingPOST /v2/app-installations/{appInstallationId}/actions/promote-staging
This is a breaking change.The media type application/json for the response with the status 204 has been removed for the POST operation at the endpoint POST /v2/contributors/{contributorId}/extensions/{extensionId}/verification-process. This is a breaking change.
A new required request property planId has been added for the POST operations at the following endpoints:
POST /v2/customers/{customerId}/ai-hosting-keysPOST /v2/projects/{projectId}/ai-hosting-keysThe databaseRestores request property's minItems has been increased to 1 for the POST operation at the endpoint POST /v2/project-backups/{projectBackupId}/restore.
The pathRestore/sourcePaths request property's minItems has been increased to 1 for the POST operation at the endpoint POST /v2/project-backups/{projectBackupId}/restore.
The following optional properties have been added to the responses with the 200 status:
autoUpdatesActivated for the GET operations at:
GET /v2/app-installationsGET /v2/app-installations/{appInstallationId}recommendation for the GET operation at GET /v2/cronjobs/{cronjobId}/executions/{executionId}/analysis.The following required properties have been added to the responses with the 200 status:
summary for the GET operation at GET /v2/cronjobs/{cronjobId}/executions/{executionId}/analysis.description and planId for the GET operation at GET /v2/customers/{customerId}/ai-hosting./items/planId and /items/profileId for the GET operation at GET /v2/customers/{customerId}/ai-hosting-keys.planId and profileId for the POST operation at POST /v2/customers/{customerId}/ai-hosting-keys.planId and profileId for the GET operation at GET /v2/customers/{customerId}/ai-hosting-keys/{keyId}.planId and profileId for the PUT operation at PUT /v2/customers/{customerId}/ai-hosting-keys/{keyId}.New optional request parameters have been added for the following GET operations:
limit, page, planId, and skip for GET /v2/projects/{projectId}/ai-hosting-keys.baseArticleNames, order, search, and sort for GET /v2/customers/{customerId}/contracts.referenceAggregate, referenceDomain, and referenceId for GET /v2/notifications.The following endpoints have been added:
GET /v2/app-installations/{appInstallationId}/error-analysisGET /v2/customers/{customerId}/ai-hostingsPOST /v2/customers/{customerId}/ai-hostingsGET /v2/customers/{customerId}/ai-hostings/{planId}PUT /v2/customers/{customerId}/ai-hostings/{planId}GET /v2/stacks/{stackId}/services/{serviceId}/log-analysisGET /v2/projects/{projectId}/ai-hostingsGET /v2/projects/{projectId}/ai-hostings/{planId}The non-success response with the status 500 has been removed for the POST operation at the endpoint POST /v2/customers/{customerId}/avatar.
The following optional request parameters have been added for the GET operation at GET /v2/projects/{projectId}/filesystem-file-content:
If-RangeRangeThe success response with the status 206 and the non-success response with the status 416 have been added for the GET operation at GET /v2/projects/{projectId}/filesystem-file-content.
The following optional request parameters have been added for the GET operation at GET /v2/stacks/{stackId}/services/{serviceId}/logs:
If-RangeRangeThe non-success response with the status 416 and the success response with the status 206 have been added for the GET operation at GET /v2/stacks/{stackId}/services/{serviceId}/logs.
Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Breaking removed the success response with the status '200'
added the success response with the status '204'
For details, refer to the POST/v2/
Breaking removed the success response with the status '200'
added the success response with the status '204'
For details, refer to the POST/v2/
For details, refer to the POST/v2/
Breaking added the new required request property 'planId'
added the required property 'planId' to the response with the '201' status
added the required property 'profileId' to the response with the '201' status
For details, refer to the POST/v2/
Breaking the 'databaseRestores' request property's minItems was increased to '1'
Breaking the 'pathRestore/sourcePaths' request property's minItems was increased to '1'
For details, refer to the POST/v2/
Breaking added the new required request property 'planId'
added the required property 'planId' to the response with the '201' status
added the required property 'profileId' to the response with the '201' status
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the optional property 'recommendation' to the response with the '200' status
added the required property 'summary' to the response with the '200' status
For details, refer to the GET/v2/
added the required property 'description' to the response with the '200' status
added the required property 'planId' to the response with the '200' status
For details, refer to the GET/v2/
added the new optional 'query' request parameter 'limit'
added the new optional 'query' request parameter 'page'
added the new optional 'query' request parameter 'planId'
added the new optional 'query' request parameter 'skip'
added the required property '/items/planId' to the response with the '200' status
added the required property '/items/profileId' to the response with the '200' status
For details, refer to the GET/v2/
added the required property 'planId' to the response with the '200' status
added the required property 'profileId' to the response with the '200' status
For details, refer to the GET/v2/
added the required property 'planId' to the response with the '200' status
added the required property 'profileId' to the response with the '200' status
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the PUT/v2/
For details, refer to the POST/v2/
added the new optional 'query' request parameter 'baseArticleNames'
added the new optional 'query' request parameter 'order'
added the new optional 'query' request parameter 'search'
added the new optional 'query' request parameter 'sort'
For details, refer to the GET/v2/
For details, refer to the PUT/v2/
added the new optional 'query' request parameter 'referenceAggregate'
added the new optional 'query' request parameter 'referenceDomain'
added the new optional 'query' request parameter 'referenceId'
For details, refer to the GET/v2/
For details, refer to the POST/v2/
added the new optional 'query' request parameter 'planId'
added the optional property 'description' to the response with the '200' status
added the required property 'planId' to the response with the '200' status
For details, refer to the GET/v2/
added the new optional 'query' request parameter 'limit'
added the new optional 'query' request parameter 'page'
added the new optional 'query' request parameter 'planId'
added the new optional 'query' request parameter 'skip'
added the required property '/items/planId' to the response with the '200' status
added the required property '/items/profileId' to the response with the '200' status
For details, refer to the GET/v2/
added the required property 'planId' to the response with the '200' status
added the required property 'profileId' to the response with the '200' status
For details, refer to the GET/v2/
added the required property 'planId' to the response with the '200' status
added the required property 'profileId' to the response with the '200' status
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the new optional 'header' request parameter 'If-Range'
added the new optional 'header' request parameter 'Range'
added the non-success response with the status '416'
added the success response with the status '206'
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the new optional 'header' request parameter 'If-Range'
added the new optional 'header' request parameter 'Range'
added the non-success response with the status '416'
added the success response with the status '206'
For details, refer to the GET/v2/
The mittwald PHP SDK has been updated to version v2.1.216. This release introduces several enhancements and new features across various components of the SDK. For detailed information, please visit the release page.
App Installation Staging & System Software:
Container & Service Management:
Domain & Mail Configuration:
Marketplace & Extension Management:
Notifications & User Access Control:
Schema Robustness & Cleanup:
This release focuses on improving workflow management, service discovery, and API response consistency, while also enhancing error handling and documentation clarity.
The mittwald JavaScript SDK has been updated to version 4.456.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.456.0.
The mittwald JavaScript SDK has been updated to version 4.455.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.454.0. This release includes the following feature:
For more details, please visit the release page.
The mittwald JavaScript SDK has been updated to version 4.453.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.
The mittwald JavaScript SDK has been updated to version 4.452.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.
The mittwald JavaScript SDK has been updated to version 4.451.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub: mittwald/api-client-js 4.451.0.
The mittwald JavaScript SDK has been updated to version 4.450.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.
The mittwald JavaScript SDK has been updated to version 4.449.0. This release includes a feature update where the generated client has been updated. For more details, you can view the release on GitHub here.
This week's update to the mittwald API includes the removal of the 'application/json' media type for '204' responses in several endpoints, the addition of new optional and required properties across various responses, and the introduction of new endpoints for managing app installations and extensions.
The media type application/json has been removed for the response with status 204 for the following operations:
DELETE operation extension-delete-extension-instance at the path /v2/extension-instances/{extensionInstanceId}.POST operation extension-disable-extension-instance at the path /v2/extension-instances/{extensionInstanceId}/actions/disable.POST operation extension-enable-extension-instance at the path /v2/extension-instances/{extensionInstanceId}/actions/enable. This is a breaking change.The new enum value hasOrdersInProgress has been added to the /items/deletionProhibitedBy/items/ response property for the response status 200 for the following operations:
GET operation customer-list-customers at the path /v2/customers.GET operation customer-get-customer at the path /v2/customers/{customerId}.The optional property /items/sourceAppInstallationId has been added to the response with status 200 for the GET operation app-list-appinstallations-for-user at the path /v2/app-installations.
The optional property /items/staging has been added to the response with status 200 for the GET operation app-list-appinstallations-for-user at the path /v2/app-installations.
The optional property sourceAppInstallationId has been added to the response with status 200 for the GET operation app-get-appinstallation at the path /v2/app-installations/{appInstallationId}.
The optional property staging has been added to the response with status 200 for the GET operation app-get-appinstallation at the path /v2/app-installations/{appInstallationId}.
The following endpoints have been added:
POST operation app-detach-appinstallation-staging at the path /v2/app-installations/{appInstallationId}/actions/detach-staging.POST operation app-promote-appinstallation-staging at the path /v2/app-installations/{appInstallationId}/actions/promote-staging.POST operation app-request-appinstallation-staging at the path /v2/app-installations/{appInstallationId}/actions/staging.The optional property /items/createdAt has been added to the response with status 200 for the GET operation extension-list-own-extensions at the path /v2/contributors/{contributorId}/extensions.
The optional property /items/publishedAt has been added to the response with status 200 for the GET operation extension-list-own-extensions at the path /v2/contributors/{contributorId}/extensions.
The optional property createdAt has been added to the response with status 200 for the GET operation extension-get-own-extension at the path /v2/contributors/{contributorId}/extensions/{extensionId}.
The optional property publishedAt has been added to the response with status 200 for the GET operation extension-get-own-extension at the path /v2/contributors/{contributorId}/extensions/{extensionId}.
The optional property createdAt has been added to the response with status 200 for the PATCH operation extension-patch-extension at the path /v2/contributors/{contributorId}/extensions/{extensionId}.
The optional property publishedAt has been added to the response with status 200 for the PATCH operation extension-patch-extension at the path /v2/contributors/{contributorId}/extensions/{extensionId}.
The optional property /items/recipient/leitwegId has been added to the response with status 200 for the GET operation contributor-list-incoming-invoices at the path /v2/contributors/{contributorId}/invoices/incoming.
The optional property /items/recipient/purchaseOrderReference has been added to the response with status 200 for the GET operation contributor-list-incoming-invoices at the path /v2/contributors/{contributorId}/invoices/incoming.
The optional property /items/owner/purchaseOrderReference has been added to the response with status 200 for the GET operation customer-list-customers at the path /v2/customers.
The new optional request property owner/purchaseOrderReference has been added for the following operations:
POST operation customer-create-customer at the path /v2/customers.PUT operation customer-update-customer at the path /v2/customers/{customerId}.The optional property owner/purchaseOrderReference has been added to the response with status 200 for the GET operation customer-get-customer at the path /v2/customers/{customerId}.
The required property parentCustomerId has been added to the response with status 200 for the following operations:
GET operation extension-get-extension-instance-for-customer at the path /v2/customers/{customerId}/extensions/{extensionId}.GET operation extension-list-extension-instances at the path /v2/extension-instances.GET operation extension-get-extension-instance at the path /v2/extension-instances/{extensionInstanceId}.The new optional request parameter parentCustomerId has been added for the GET operation extension-list-extension-instances at the path /v2/extension-instances.
The required property /items/publishedAt has been added to the response with status 200 for the GET operation extension-list-extensions at the path /v2/extensions.
The required property /anyOf[#/components/schemas/de.mittwald.v1.marketplace.Extension]/publishedAt has been added to the response with status 200 for the GET operation extension-get-extension at the path /v2/extensions/{extensionId}.
The optional property recipient/leitwegId has been added to the response with status 200 for the GET operation invoice-detail at the path /v2/invoices/{invoiceId}.
The optional property recipient/purchaseOrderReference has been added to the response with status 200 for the GET operation invoice-detail at the path /v2/invoices/{invoiceId}.
The required property /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareDeleted]/parameters/appInstallation has been added to the response with status 200 for the GET operation project-list-project-activities at the path /v2/projects/{projectId}/activities.
The required property /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/parameters/appInstallation has been added to the response with status 200 for the GET operation project-list-project-activities at the path /v2/projects/{projectId}/activities.
The optional property /items/sourceAppInstallationId has been added to the response with status 200 for the GET operation app-list-appinstallations at the path /v2/projects/{projectId}/app-installations.
The optional property /items/staging has been added to the response with status 200 for the GET operation app-list-appinstallations at the path /v2/projects/{projectId}/app-installations.
The required property parentCustomerId has been added to the response with status 200 for the GET operation extension-get-extension-instance-for-project at the path /v2/projects/{projectId}/extensions/{extensionId}.
Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the DELETE/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
added the new 'hasOrdersInProgress' enum value to the '/items/deletionProhibitedBy/items/' response property for the response status '200'
added the optional property '/items/owner/purchaseOrderReference' to the response with the '200' status
For details, refer to the GET/v2/
added the new 'hasOrdersInProgress' enum value to the 'deletionProhibitedBy/items/' response property for the response status '200'
added the optional property 'owner/purchaseOrderReference' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property '/items/sourceAppInstallationId' to the response with the '200' status
added the optional property '/items/staging' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'sourceAppInstallationId' to the response with the '200' status
added the optional property 'staging' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
For details, refer to the POST/v2/
added the optional property '/items/createdAt' to the response with the '200' status
added the optional property '/items/publishedAt' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'createdAt' to the response with the '200' status
added the optional property 'publishedAt' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'createdAt' to the response with the '200' status
added the optional property 'publishedAt' to the response with the '200' status
For details, refer to the PATCH/v2/
added the optional property '/items/recipient/leitwegId' to the response with the '200' status
added the optional property '/items/recipient/purchaseOrderReference' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
added the optional property 'recipient/leitwegId' to the response with the '200' status
added the optional property 'recipient/purchaseOrderReference' to the response with the '200' status
For details, refer to the GET/v2/
added the new optional request property 'recipient/leitwegId'
added the new optional request property 'recipient/purchaseOrderReference'
added the optional property 'recipient/leitwegId' to the response with the '200' status
added the optional property 'recipient/purchaseOrderReference' to the response with the '200' status
For details, refer to the PUT/v2/
added the optional property '/items/recipient/leitwegId' to the response with the '200' status
added the optional property '/items/recipient/purchaseOrderReference' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'recipient/leitwegId' to the response with the '200' status
added the optional property 'recipient/purchaseOrderReference' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
added the new optional 'query' request parameter 'parentCustomerId'
added the required property '/items/parentCustomerId' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the new enum value 'relevance' to the 'query' request parameter 'sort'
added the required property '/items/publishedAt' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.UnpublishedExtension]/publishedAt' to the response with the '200' status
added the required property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.Extension]/publishedAt' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'recipient/leitwegId' to the response with the '200' status
added the optional property 'recipient/purchaseOrderReference' to the response with the '200' status
For details, refer to the GET/v2/
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareDeleted]/parameters/appInstallation' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/parameters/appInstallation' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property '/items/sourceAppInstallationId' to the response with the '200' status
added the optional property '/items/staging' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The mittwald JavaScript SDK has been updated to version 4.449.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.
The mittwald JavaScript SDK version 4.448.2 has been released on August 27, 2026. This update includes a bug fix related to the continuous integration process, specifically addressing issues with recovering from partial npm publishes via Lerna's from-package command. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK version 4.448.1 has been released on August 27, 2026. This release includes a bug fix related to the continuous integration process, specifically pinning the development publish job to the development branch and restoring version 4.448.0. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.448.1.
The latest prerelease of the mittwald JavaScript SDK, version 0.0.0-development-f13d74a-20260826.0, is now available. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.448.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.
The mittwald JavaScript SDK version 4.447.0 has been released. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.446.0. This release includes the following feature:
For more details, please visit the release page.
This week's update to the mittwald API includes the removal of several required properties from responses, the addition of default values for request parameters, new optional properties in responses, and the introduction of new endpoints and request parameters to enhance functionality.
/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/purpose was removed from the response with the '200' status for the operation GET /v2/projects/{projectId}/activities. This is a breaking change./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/purpose was removed from the response with the '200' status for the operation GET /v2/projects/{projectId}/activities. This is a breaking change./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/purpose was removed from the response with the '200' status for the operation GET /v2/projects/{projectId}/activities. This is a breaking change./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/purpose was removed from the response with the '200' status for the operation GET /v2/projects/{projectId}/activities. This is a breaking change.GET /v2/projects/{projectId}/sftp-users.GET /v2/projects/{projectId}/ssh-users./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseVersionSet]/name response property for the operation GET /v2/projects/{projectId}/activities.GET /v2/projects/{projectId}/sftp-users and GET /v2/projects/{projectId}/ssh-users.GET /v2/app-installations/{appInstallationId}/system-software to retrieve the installed SystemSoftware for a specific AppInstallation./items/owner/leitwegId was added to the response with the '200' status for the operations GET /v2/customers, POST /v2/customers, and PUT /v2/customers/{customerId}.GET /v2/customers/{customerId}/extensions/{extensionId}, GET /v2/extension-instances, and GET /v2/extension-instances/{extensionInstanceId}.GET /v2/extension-instances.GET /v2/projects/{projectId}/cronjobs.GET /v2/projects/{projectId}/sftp-users and GET /v2/projects/{projectId}/ssh-users.GET /v2/services to list services the executing user has access to.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/purpose' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/purpose' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/purpose' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/purpose' from the response with the '200' status
added the new 'database.redis-version-set' enum value to the '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseVersionSet]/name' response property for the response status '200'
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/before/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/before/ttl' to the response with the '200' status
added '#/components/schemas/de.mittwald.v1.activitylog.AppInstallationMainDatabaseChanged' to the '/items/action' response property 'anyOf' list for the response status '200'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
added the new optional 'query' request parameter 'page'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
added the new optional 'query' request parameter 'page'
For details, refer to the GET/v2/
For details, refer to the unknown operation endpoint.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
added the new optional 'query' request parameter 'hasAcceptedAllScopes'
added the optional property '/items/scopeChangeAcceptanceDeadline' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The mittwald JavaScript SDK has been updated to version 4.445.0. This release includes an update to the generated client, enhancing the functionality of the SDK. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK version 4.444.0 has been released. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.443.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.
The mittwald JavaScript SDK has been updated to version 4.442.0. This release includes the following feature:
For more details, visit the release page.
This week, the mittwald API introduces several enhancements, including the addition of the 'runtimeApps' enum value to various response properties, the introduction of a new endpoint for retrieving container template assets, and the inclusion of required properties in responses for file creation and metadata retrieval.
runtimeApps enum value has been added to the /items/features/items/ and /items/supportedFeatures/items/ response properties for the response status '200' in the GET /v2/customers/{customerId}/projects operation.runtimeApps enum value has also been added to the /items/features/items/ and /items/supportedFeatures/items/ response properties for the response status '200' in the GET /v2/projects operation.runtimeApps enum value has been added to the features/items/ and supportedFeatures/items/ response properties for the response status '200' in the GET /v2/projects/{projectId} operation.GET /v2/container-templates/{templateId}/assets/{assetPath}, which retrieves a Container Template asset.GET /v2/container-templates/{templateId}/icon operation, which retrieves a Container Template icon.shortId has been added to the response with the '201' status in the POST /v2/files operation, which creates a file.shortId has also been added to the response with the '200' status in the GET /v2/files/{fileId}/meta operation, which retrieves a file's metadata.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
added the new 'runtimeApps' enum value to the '/items/features/items/' response property for the response status '200'
added the new 'runtimeApps' enum value to the '/items/supportedFeatures/items/' response property for the response status '200'
For details, refer to the GET/v2/
added the new 'runtimeApps' enum value to the '/items/features/items/' response property for the response status '200'
added the new 'runtimeApps' enum value to the '/items/supportedFeatures/items/' response property for the response status '200'
For details, refer to the GET/v2/
added the new 'runtimeApps' enum value to the 'features/items/' response property for the response status '200'
added the new 'runtimeApps' enum value to the 'supportedFeatures/items/' response property for the response status '200'
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
The mittwald PHP SDK has been updated to version v2.1.215. This release introduces a new endpoint for retrieving container template assets, enhancing the flexibility of cloud resource management. The new endpoint allows users to request specific assets within a given template.
/v2/container-templates/{templateId}/assets/{assetPath}GetTemplateAssetRequestGetTemplateAssetBadRequestResponseGetTemplateAssetForbiddenResponseGetTemplateAssetNotFoundResponseGetTemplateAssetDefaultResponseGetTemplateAssetInternalServerErrorResponseGetTemplateAssetServiceUnavailableResponseGetTemplateAssetTooManyRequestsResponseAdditionally, the FileMeta class has been updated to include a new shortId property, providing a shorter identifier for files. The constructor for FileMeta has been updated to support this new parameter.
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.441.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.
The mittwald JavaScript SDK has been updated to version 4.440.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.440.0.
The mittwald JavaScript SDK has been updated to version 4.439.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.
This week's update to the mittwald API includes the removal of an API path without deprecation, several changes to required and optional response properties across various endpoints, and the addition of new enum values, enhancing the overall functionality and flexibility of the API.
/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/database, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/database, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/database, and /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/database have been removed from the response with the '200' status for the GET operation project-list-project-activities./items/originalAddress has been added to the response with the '200' status for the GET operation mail-list-mail-addresses-for-user at the path /v2/mail-addresses/.originalAddress has been added to the response with the '200' status for the GET operation mail-get-mail-address at the path /v2/mail-addresses/{mailAddressId}./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/after/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/before/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCaaRecordSet]/changes/after/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCaaRecordSet]/changes/before/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCnameRecordSet]/changes/after/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCnameRecordSet]/changes/before/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSet]/changes/after/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSet]/changes/before/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsSrvRecordSet]/changes/after/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsSrvRecordSet]/changes/before/ttl, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsTxtRecordSet]/changes/after/ttl, and /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsTxtRecordSet]/changes/before/ttl have been added to the response with the '200' status for the GET operation project-list-project-activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/name, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/purpose, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/name, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/purpose, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/name, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/purpose, /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/name, and /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/purpose have been added to the response with the '200' status for the GET operation project-list-project-activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/before/aRecords and /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/before/mx have been added to the response with the '200' status for the GET operation project-list-project-activities./items/originalAddress has been added to the response with the '200' status for the GET operation mail-list-mail-addresses at the path /v2/projects/{projectId}/mail-addresses.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the GET/v2/
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/database' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/database' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/database' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/database' from the response with the '200' status
added the new 'managed' enum value to the '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/after/aRecords' response property for the response status '200'
added the new 'managed' enum value to the '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/after/mx' response property for the response status '200'
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/before/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCaaRecordSet]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCaaRecordSet]/changes/before/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCnameRecordSet]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsCnameRecordSet]/changes/before/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSet]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSet]/changes/before/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsSrvRecordSet]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsSrvRecordSet]/changes/before/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsTxtRecordSet]/changes/after/ttl' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsTxtRecordSet]/changes/before/ttl' to the response with the '200' status
added '#/components/schemas/de.mittwald.v1.activitylog.DatabaseVersionSet, #/components/schemas/de.mittwald.v1.activitylog.AppInstallationFailed' to the '/items/action' response property 'anyOf' list for the response status '200'
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/name' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/after/purpose' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/name' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked]/changes/before/purpose' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/name' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/after/purpose' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/name' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked]/changes/before/purpose' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/before/aRecords' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/before/mx' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The latest release of the mittwald PHP SDK, version v2.1.214, introduces several significant changes aimed at improving the efficiency and clarity of the API usage.
deprecatedContainerGetTemplateAsset has been removed. Users are advised to use direct asset URLs from the Template's fields instead.iconUrl and screenshots fields.GET /v2/container-templates/{templateId}/assets/icon.svg.For more details, please visit the release page.
The mittwald PHP SDK has released version v2.1.213, introducing several new features and improvements. This update focuses on enhancing logging capabilities and schema updates to provide users with a more comprehensive overview of database interactions.
New Database Version Set Activity Logs:
DatabaseVersionSet schema to log changes in database version sets.Activity Log Schema Updates:
AppInstallationDatabaseLinked and AppInstallationDatabaseUnlinked to include name and purpose properties.unspecified, primary, cache, and custom.New Enum Types:
AppInstallationDatabaseLinkedChangesAfterPurpose and DatabaseVersionSetName for better state representation in activity logs.Improvements in Existing Schemas:
Consolidated Data Structures:
Documentation Updates:
This release aims to improve tracking and debugging processes by providing a more detailed logging mechanism. For more information, visit the release page.
The mittwald PHP SDK has been updated to version v2.1.212. This release introduces several changes and new features, focusing on deprecating certain methods and enhancing response handling.
deprecatedContainerGetTemplateAsset, has been added for retrieving Container Template assets. Users are encouraged to use the direct asset URLs provided in the Template's iconUrl and screenshots fields.getTemplateAsset: The getTemplateAsset method has been removed from the ContainerClient interface. A new method, deprecatedContainerGetTemplateAsset, has been introduced to replace the deprecated functionality, with a recommendation to use alternative approaches.deprecatedContainerGetTemplateAsset method, including:
DeprecatedContainerGetTemplateAssetBadRequestResponseDeprecatedContainerGetTemplateAssetNotFoundResponseDeprecatedContainerGetTemplateAssetForbiddenResponseDeprecatedContainerGetTemplateAssetInternalServerErrorResponseDeprecatedContainerGetTemplateAssetServiceUnavailableResponseDeprecatedContainerGetTemplateAssetTooManyRequestsResponseoriginalAddress Field in Mail Address Schema: A new field, originalAddress, has been introduced in the MailAddress class to store the address the mailbox had before it was archived.For more details, visit the release page.
The latest release of the mittwald PHP SDK, version v2.1.211, introduces enhancements aimed at improving integration with Go clients. Notably, new metadata fields have been added to the GetFileRequest and GetFileWithNameRequest to enhance documentation and type safety. Specifically, the x-go-type field has been incorporated for the accept and content-disposition parameters in both request types. These improvements are designed to facilitate better code generation and reduce errors during file retrieval processes.
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.438.0. This release includes the following feature:
For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.437.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.437.0.
The mittwald JavaScript SDK has been updated to version 4.436.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.436.0.
The mittwald JavaScript SDK has been updated to version 4.435.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.
The mittwald JavaScript SDK has been updated to version 4.434.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/api-client-js v4.434.0.
This week, the mittwald API introduces several updates, including changes to default values for request parameters, the addition of new optional properties and parameters, and the removal of deprecated operation IDs across various endpoints.
limit request parameter in the GET /v2/cronjobs/{cronjobId}/executions operation has been changed from 1000.00 to 10000.00. This is a breaking change.limit and skip request parameters have been added to the following operations:
GET /v2/customer-invites: limit is 1000.00, skip is 0.00.GET /v2/customer-memberships: limit is 1000.00, skip is 0.00.GET /v2/customers/{customerId}/invites: limit is 1000.00, skip is 0.00.GET /v2/customers/{customerId}/memberships: limit is 1000.00, skip is 0.00.GET /v2/project-invites: limit is 1000.00, skip is 0.00.GET /v2/project-memberships: limit is 1000.00, skip is 0.00.GET /v2/projects/{projectId}/invites: limit is 1000.00, skip is 0.00.GET /v2/projects/{projectId}/memberships: limit is 1000.00, skip is 0.00.limit request parameter has been set to 0.00 for the following operations:
GET /v2/customer-invitesGET /v2/customer-membershipsGET /v2/customers/{customerId}/invitesGET /v2/customers/{customerId}/membershipsGET /v2/project-invitesGET /v2/project-membershipsGET /v2/projects/{projectId}/invitesGET /v2/projects/{projectId}/membershipspage has been added to the following operations:
GET /v2/customers/{customerId}/invitesGET /v2/customers/{customerId}/membershipsGET /v2/projects/{projectId}/invitesGET /v2/projects/{projectId}/membershipsdatabases has been added to the PATCH /v2/app-installations/{appInstallationId} operation.400 has been added to the PATCH /v2/app-installations/{appInstallationId} operation.PATCH /v2/app-installations/{appInstallationId}/database/replace is now PATCH /v2/app-installations/{appInstallationId}/database/replace.PATCH /v2/cronjobs/{cronjobId}/app-installation-id is now PATCH /v2/cronjobs/{cronjobId}/app-installation-id.PUT /v2/cronjobs/{cronjobId}/app-installation-id is now PUT /v2/cronjobs/{cronjobId}/app-installation-id.GET /v2/customers/{customerId}/ai-hosting/contract is now GET /v2/customers/{customerId}/ai-hostings/{aiHostingId}/contract.PATCH /v2/project-backups/{projectBackupId}/description is now PATCH /v2/project-backups/{projectBackupId}/description.PUT /v2/project-backups/{projectBackupId}/expiration-time is now PUT /v2/project-backups/{projectBackupId}/expiration-time.PATCH /v2/projects/{projectId}/description is now PATCH /v2/projects/{projectId}/description.PUT /v2/projects/{projectId}/storage-space-notification-threshold is now PUT /v2/projects/{projectId}/storage-space-notification-threshold.PATCH /v2/servers/{serverId}/description is now PATCH /v2/servers/{serverId}/description.PUT /v2/servers/{serverId}/storage-space-notification-threshold is now PUT /v2/servers/{serverId}/storage-space-notification-threshold.PUT /v2/stacks/{stackId}/update-schedule is now PUT /v2/stacks/{stackId}/update-schedule.200:
GET /v2/container-templates: /items/userInputs/items/positionMeta.GET /v2/container-templates/{templateId}: userInputs/items/positionMeta.GET /v2/projects/{projectId}/activities: #/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserPasswordSet.GET /v2/projects/{projectId}/services: /items/templateId.GET /v2/projects/{projectId}/stacks: /items/services/items/templateId.POST /v2/projects/{projectId}/stacks: services/items/templateId.GET /v2/stacks: /items/services/items/templateId.GET /v2/stacks/{stackId}: services/items/templateId.PATCH /v2/stacks/{stackId}: services/items/templateId.PUT /v2/stacks/{stackId}: services/items/templateId.GET /v2/stacks/{stackId}/services/{serviceId}: templateId.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
added the new optional 'query' request parameter 'page'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
added the new optional 'query' request parameter 'page'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
added the new optional 'query' request parameter 'page'
For details, refer to the GET/v2/
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
for the 'query' request parameter 'limit', the min was set to '0.00'
added the new optional 'query' request parameter 'page'
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the PUT/v2/
added the new 'unread' enum value to the 'status' response property for the response status '200'
added the new 'unread' enum value to the request property 'status'
For details, refer to the PUT/v2/
added the new optional request property 'databases'
added the non-success response with the status '400'
For details, refer to the PATCH/v2/
For details, refer to the unknown operation app-replace-database endpoint.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the unknown operation cronjob-update-cronjob-app-id-deprecated endpoint.
For details, refer to the unknown operation cronjob-replace-cronjob-app-installation-id endpoint.
api operation id 'contract-get-detail-of-contract-by-ai-hosting' removed and replaced with 'deprecated-contract-get-detail-of-contract-by-ai-hosting'
endpoint added
For details, refer to the GET/v2/
For details, refer to the unknown operation backup-update-project-backup-description endpoint.
For details, refer to the unknown operation backup-replace-project-backup-expiration-time endpoint.
For details, refer to the GET/v2/
For details, refer to the unknown operation project-update-project-description endpoint.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the unknown operation storagespace-replace-project-notification-threshold endpoint.
For details, refer to the unknown operation project-update-server-description endpoint.
For details, refer to the unknown operation storagespace-replace-server-notification-threshold endpoint.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the PATCH/v2/
For details, refer to the PUT/v2/
For details, refer to the GET/v2/
For details, refer to the unknown operation container-set-stack-update-schedule endpoint.
The latest release of the mittwald PHP SDK, v2.1.210, introduces several new features and improvements aimed at enhancing functionality and type safety.
DesiredSystemSoftware and PatchLinkedDatabase schemas have been introduced to enhance the Patch App Installation requests.DeclareStack and UpdateStack request bodies have been updated to include new service and volume declaration structures.mixed[] type hints with more specific array types.PatchAppinstallationRequestBody now includes DesiredSystemSoftware and PatchLinkedDatabase.RequestAppinstallationRequestBody has been modified to utilize DesiredSystemSoftware.DeclareStackRequestBody and UpdateStackRequestBody now incorporate ServiceDeclareRequest and VolumeDeclareRequest.ExtensionPatchExtensionRequestBody and ExtensionRegisterExtensionRequestBody to use the FrontendFragment schema, enhancing frontend integration.User class has been refined to specify more precise types for customerMemberships and projectMemberships.GenericAction and DetailMetrics to improve validation and error handling.These updates collectively aim to enhance type safety, improve the API's robustness, and provide a clearer contract between systems utilizing these APIs.
The mittwald PHP SDK has released version v2.1.209, introducing several new features and improvements. You can view the full release details here.
PATCH /v2/app-installations/{appInstallationId} endpoint.linkDatabase and replaceDatabase methods are deprecated, with functionality moved to the new PATCH endpoint.DeprecatedAppReplaceDatabaseRequest and DeprecatedAppLinkDatabaseRequest have been created for better organization.limit and skip parameters in request classes simplify API usage.positionMeta to container-related template schemas.These updates aim to streamline API interactions and improve usability while facilitating a smooth transition from deprecated methods.
The latest release of the mittwald PHP SDK, version v2.1.208, introduces several new features, improvements, and deprecations.
For more details, visit the release page.
The latest release of the mittwald PHP SDK, version v2.1.207, introduces several enhancements aimed at improving data handling and service metadata management.
Increased Default Limit for ListExecutionsRequest: The default limit for executing requests in the ListExecutionsRequest class has been increased from 1,000 to 10,000. This enhancement allows for more efficient bulk data operations by retrieving a larger number of execution results in a single request.
Template ID Support in ServiceResponse: A new property, templateId, has been added to the ServiceResponse class. This property stores the ID of the template used during service creation, if applicable.
Getter and Setter Methods for Template ID:
getTemplateId(): Retrieves the templateId.withTemplateId(string $templateId): Sets the templateId with validation.withoutTemplateId(): Clears the templateId.These updates enhance the API's usability and flexibility, particularly for handling larger data sets and managing additional metadata related to services.
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.433.0. This release includes the following feature:
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.432.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.
The mittwald JavaScript SDK has been updated to version 4.431.0. This release includes the following feature:
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.430.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, please refer to the release page.
The mittwald JavaScript SDK version 4.429.1 has been released. This update includes a bug fix for the project module, specifically addressing the use of a generic patch route for updating project descriptions. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.429.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.428.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details on the changes and to view the release notes, visit the release page.
This week, the mittwald API introduces several enhancements, including default values for request parameters, the addition of new endpoints for updating various resources, and the removal of deprecated operation IDs to streamline API usage.
GET operation cronjob-list-executions at the path /v2/cronjobs/{cronjobId}/executions, default values of 1000.00 for the limit request parameter and 0.00 for the skip request parameter have been added. Note that this is a breaking change.header request parameter Accept-Language has been removed from the GET operation cronjob-get-execution-analysis at the path /v2/cronjobs/{cronjobId}/executions/{executionId}/analysis./items/type has been added to the response with the 200 status for the GET operation container-list-templates at the path /v2/container-templates.type has been added to the response with the 200 status for the GET operation container-get-template at the path /v2/container-templates/{templateId}.database-update-mysql-database-default-charset has been removed and replaced with deprecated-database-update-mysql-database-default-charset for the PATCH operation at the path /v2/mysql-databases/{mysqlDatabaseId}/default-charset.database-update-mysql-database-description has been removed and replaced with deprecated-database-update-mysql-database-description for the PATCH operation at the path /v2/mysql-databases/{mysqlDatabaseId}/description.PATCH operation database-update-mysql-user at the path /v2/mysql-users/{mysqlUserId}.database-update-mysql-user has been removed and replaced with deprecated-database-replace-mysql-user for the PUT operation at the path /v2/mysql-users/{mysqlUserId}.database-update-mysql-user-password has been removed and replaced with deprecated-database-update-mysql-user-password for the PATCH operation at the path /v2/mysql-users/{mysqlUserId}/password.PATCH operation backup-update-project-backup at the path /v2/project-backups/{projectBackupId}.PATCH operation project-update-project at the path /v2/projects/{projectId}.PATCH operation storagespace-update-project-statistics at the path /v2/projects/{projectId}/storage-space-statistics.database-update-redis-database-configuration has been removed and replaced with deprecated-database-update-redis-database-configuration for the PATCH operation at the path /v2/redis-databases/{redisDatabaseId}/configuration.database-update-redis-database-description has been removed and replaced with deprecated-database-update-redis-database-description for the PATCH operation at the path /v2/redis-databases/{redisDatabaseId}/description.PATCH operation project-update-server at the path /v2/servers/{serverId}.PATCH operation storagespace-update-server-statistics at the path /v2/servers/{serverId}/storage-space-statistics.updateSchedule has been added for the PATCH operation container-update-stack at the path /v2/stacks/{stackId}.POST operation container-add-template-component at the path /v2/stacks/{stackId}/actions/add-template-component.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Breaking for the 'query' request parameter 'limit', default value '1000.00' was added
Breaking for the 'query' request parameter 'skip', default value '0.00' was added
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the unknown operation database-update-mysql-database-default-charset endpoint.
For details, refer to the unknown operation database-update-mysql-database-description endpoint.
endpoint added
api operation id 'database-update-mysql-user' removed and replaced with 'deprecated-database-replace-mysql-user'
For details, refer to the PATCH/v2/
For details, refer to the unknown operation database-update-mysql-user-password endpoint.
For details, refer to the PATCH/v2/
For details, refer to the PATCH/v2/
For details, refer to the PATCH/v2/
For details, refer to the unknown operation database-update-redis-database-configuration endpoint.
For details, refer to the unknown operation database-update-redis-database-description endpoint.
For details, refer to the PATCH/v2/
For details, refer to the PATCH/v2/
For details, refer to the PATCH/v2/
For details, refer to the POST/v2/
The mittwald PHP SDK has been updated to version 2.1.206. This release introduces several new features, enhancements, and changes to improve functionality and usability.
updateSchedule feature for stacks allows users to schedule automatic image updates using a cron expression and timezone. Users can remove the schedule by setting it to null or omit the property to keep it unchanged.Template schema now includes a type field, distinguishing between 'component' and 'standalone' templates.declare-stack endpoint documentation, detailing which stack properties can be modified directly and which require separate PATCH requests.Schema Modifications:
UpdateStackRequest and UpdateStackRequestBody classes now include the updateSchedule property.UpdateStackRequestBodyUpdateSchedule, has been introduced for handling update schedules, including validation for cron and timezone formats.Template schema now requires a type property to specify the template's nature.Class Updates:
updateSchedule property in the UpdateStackRequestBody class.Template class now includes methods for accessing the type property, with constructor modifications to accept this parameter.For more details, visit the release page.
The mittwald PHP SDK has been updated to version v2.1.205. This release introduces several new features and updates to existing interfaces, enhancing the SDK's functionality for managing backups, containers, and project details.
Backup Client:
updateProjectBackup: A new method to update project backup information.Container Client:
addTemplateComponent: Allows adding a template component to a stack.Project Client:
updateProject: Enables updating project details.updateServer: Facilitates updating server details.Storage Space Statistics:
storagespaceUpdateProjectStatistics: Updates project storage space statistics.storagespaceUpdateServerStatistics: Manages server storage space statistics.updateProjectBackup method.addTemplateComponent method.updateProject and updateServer methods.For more details, visit the release page.
The mittwald PHP SDK has released version v2.1.204. This update introduces a legacy endpoint for user password updates, allowing the use of deprecated methods for MySQL and Redis database updates. The release includes several deprecated methods and new response classes to handle responses for these deprecated endpoints, ensuring backward compatibility while providing flexibility.
Deprecated Methods:
deprecatedDatabaseReplaceMysqlUserdeprecatedDatabaseUpdateMysqlDatabaseDefaultCharsetdeprecatedDatabaseUpdateMysqlDatabaseDescriptiondeprecatedDatabaseUpdateMysqlUserPassworddeprecatedDatabaseUpdateRedisDatabaseConfigurationdeprecatedDatabaseUpdateRedisDatabaseDescriptionNew Response Classes:
DeprecatedDatabaseReplaceMysqlUserBadRequestResponseDeprecatedDatabaseReplaceMysqlUserDefaultResponseDeprecatedDatabaseReplaceMysqlUserNotFoundResponseDeprecatedDatabaseReplaceMysqlUserTooManyRequestsResponseDeprecatedDatabaseUpdateMysqlDatabaseDefaultCharsetBadRequestResponseDeprecatedDatabaseUpdateMysqlDatabaseDefaultCharsetDefaultResponseDeprecatedDatabaseUpdateMysqlDatabaseDefaultCharsetNotFoundResponseDeprecatedDatabaseUpdateMysqlDatabaseDefaultCharsetTooManyRequestsResponseDeprecatedDatabaseUpdateMysqlDatabaseDescriptionBadRequestResponseDeprecatedDatabaseUpdateMysqlDatabaseDescriptionDefaultResponseDeprecatedDatabaseUpdateMysqlDatabaseDescriptionNotFoundResponseDeprecatedDatabaseUpdateMysqlDatabaseDescriptionTooManyRequestsResponseDeprecatedDatabaseUpdateMysqlUserPasswordBadRequestResponseDeprecatedDatabaseUpdateMysqlUserPasswordDefaultResponseDeprecatedDatabaseUpdateMysqlUserPasswordNotFoundResponseDeprecatedDatabaseUpdateRedisDatabaseConfigurationBadRequestResponseDeprecatedDatabaseUpdateRedisDatabaseConfigurationDefaultResponseDeprecatedDatabaseUpdateRedisDatabaseConfigurationNotFoundResponseDeprecatedDatabaseUpdateRedisDatabaseConfigurationTooManyRequestsResponseDeprecatedDatabaseUpdateRedisDatabaseDescriptionBadRequestResponseDeprecatedDatabaseUpdateRedisDatabaseDescriptionDefaultResponseDeprecatedDatabaseUpdateRedisDatabaseDescriptionNotFoundResponseDeprecatedDatabaseUpdateRedisDatabaseDescriptionTooManyRequestsResponseFor more details, visit the release page.
The mittwald PHP SDK has released version v2.1.203, which includes several breaking changes, new features, improvements, and deprecated functionalities.
UpdateMysqlDatabaseDefaultCharsetRequestUpdateMysqlDatabaseDescriptionRequestUpdateMysqlUserPasswordRequestUpdateRedisDatabaseConfigurationRequestUpdateRedisDatabaseDescriptionRequestUpdateMysqlUserRequest method has been changed from PUT to PATCH, allowing for partial updates to users, including optional password updates.UpdateMysqlUserRequestBody has been streamlined to optionally include access levels, descriptions, external access, and a password, enhancing flexibility during user updates.For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.427.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.
The mittwald JavaScript SDK has been updated to version 4.426.0. This release includes the following feature:
For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.425.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.
The mittwald JavaScript SDK has been updated to version 4.424.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.424.0.
The mittwald JavaScript SDK has been updated to version 4.422.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.
The mittwald JavaScript SDK has been updated to version 4.421.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.421.0.
The mittwald JavaScript SDK has been updated to version 4.420.0. This release includes the following feature:
For further information and to view the release, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.419.0. This release includes the following feature:
For more details, you can view the release on GitHub.
The mittwald JavaScript SDK has been updated to version 4.418.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.418.0.
The mittwald JavaScript SDK has been updated to version 4.417.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.
During the week of July 10 to July 17, 2026, the mittwald API introduced several changes, including the removal of certain media types and required properties, the addition of optional properties and request parameters, and updates to response types and enumerations across various endpoints.
application/octet-stream has been removed for the response with the status 200 in the GET operation at the path /v2/container-templates/{templateId}/icon. This is a breaking change.GET operation at the path /v2/projects/{projectId}/activities have become optional for the status 200:
/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/after/aRecords/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/after/aaaaRecords/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/before/aRecords/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/before/aaaaRecords/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/after/aRecords has changed from object to string for the status 200 in the GET operation at the path /v2/projects/{projectId}/activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/after/mx has changed from object to string for the status 200 in the GET operation at the path /v2/projects/{projectId}/activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/after/aRecords/managedByIngressId has been removed from the response with the status 200 in the GET operation at the path /v2/projects/{projectId}/activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/after/mx/managed has been removed from the response with the status 200 in the GET operation at the path /v2/projects/{projectId}/activities.notReachable has been added to the status/items/type response property for the status 200 in both the GET operation at the path /v2/customers/{customerId}/invoice-settings and the PUT operation at the same path.de.mittwald.v1.activitylog.DatabaseMysqlNameSet and de.mittwald.v1.activitylog.DatabaseVersionSet have been removed from the API schema.sortOrder has been added to the GET operation at the path /v2/container-templates./items/screenshots has been added to the response with the status 200 in the GET operation at the path /v2/container-templates.screenshots has been added to the response with the status 200 in the GET operation at the path /v2/container-templates/{templateId}.GET operation at the path /v2/container-templates/{templateId}/assets/{assetPath}.container-get-template-icon has been removed and replaced with deprecated-container-get-template-icon for the GET operation at the path /v2/container-templates/{templateId}/icon.image/webp has been added for the response with the status 200 in the GET operation at the path /v2/container-templates/{templateId}/icon.GET operation at the path /v2/contributors/{contributorId}/contract-partners: sort, page, limit, order, and skip./items/requestedChanges/purgeScopes and /items/requestedChanges/purgeWebhookUrls have been added to the response with the status 200 in the GET operation at the path /v2/contributors/{contributorId}/extensions.requestedChanges/purgeScopes and requestedChanges/purgeWebhookUrls have been added to the response with the status 200 in the GET operation at the path /v2/contributors/{contributorId}/extensions/{extensionId}.requestedChanges/purgeScopes and requestedChanges/purgeWebhookUrls have been added to the response with the status 200 in the PATCH operation at the path /v2/contributors/{contributorId}/extensions/{extensionId}.403 has been added for the GET operation at the path /v2/extension-instances/{extensionInstanceId}.anyOf list for the /items/action response in the GET operation at the path /v2/projects/{projectId}/activities has been updated to include new schemas: de.mittwald.v1.activitylog.AppInstallationDescriptionSet, de.mittwald.v1.activitylog.AppInstallationDeleted, de.mittwald.v1.activitylog.AppInstallationDatabaseLinked, and de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked.anyOf list for the /items/action response in the GET operation at the path /v2/projects/{projectId}/activities has had the schemas de.mittwald.v1.activitylog.DatabaseVersionSet and de.mittwald.v1.activitylog.DatabaseMysqlNameSet removed.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Breaking removed the media type 'application/octet-stream' for the response with the status '200'
added the media type 'image/webp' for the response with the status '200'
For details, refer to the GET/v2/
Breaking the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/after/aRecords' became optional for the status '200'
Breaking the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/after/aaaaRecords' became optional for the status '200'
Breaking the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/before/aRecords' became optional for the status '200'
Breaking the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSet]/changes/before/aaaaRecords' became optional for the status '200'
Breaking the '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/after/aRecords' response's property type/format changed from 'object'/'' to 'string'/'' for status '200'
Breaking the '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/after/mx' response's property type/format changed from 'object'/'' to 'string'/'' for status '200'
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged]/changes/after/aRecords/managedByIngressId' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged]/changes/after/mx/managed' from the response with the '200' status
added '#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDescriptionSet, #/components/schemas/de.mittwald.v1.activitylog.AppInstallationDeleted, #/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseLinked, #/components/schemas/de.mittwald.v1.activitylog.AppInstallationDatabaseUnlinked' to the '/items/action' response property 'anyOf' list for the response status '200'
removed '#/components/schemas/de.mittwald.v1.activitylog.DatabaseVersionSet, #/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlNameSet' from the '/items/action' response property 'anyOf' list for the response status '200'
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the PUT/v2/
removed the schema 'de.mittwald.v1.activitylog.DatabaseMysqlNameSet'
removed the schema 'de.mittwald.v1.activitylog.DatabaseVersionSet'
For details, refer to the unknown operation endpoint.
added the new optional 'query' request parameter 'sortOrder'
added the optional property '/items/screenshots' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the unknown operation container-get-template-icon endpoint.
added the new optional 'query' request parameter 'limit'
added the new optional 'query' request parameter 'order'
added the new optional 'query' request parameter 'page'
added the new optional 'query' request parameter 'skip'
added the new optional 'query' request parameter 'sort'
For details, refer to the GET/v2/
added the optional property '/items/requestedChanges/purgeScopes' to the response with the '200' status
added the optional property '/items/requestedChanges/purgeWebhookUrls' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'requestedChanges/purgeScopes' to the response with the '200' status
added the optional property 'requestedChanges/purgeWebhookUrls' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'requestedChanges/purgeScopes' to the response with the '200' status
added the optional property 'requestedChanges/purgeWebhookUrls' to the response with the '200' status
For details, refer to the PATCH/v2/
For details, refer to the GET/v2/
The latest release of the mittwald PHP SDK, version v2.1.202, introduces new features and changes to enhance data management capabilities.
purgeScopes and purgeWebhookUrls to the OwnExtension and OwnExtensionRequestedChanges schemas. These options provide improved control over data management.OwnExtension Class:
purgeScopes and purgeWebhookUrls as boolean types in the schema definition.OwnExtensionRequestedChanges Class:
purgeScopes and purgeWebhookUrls as boolean properties.withPurgeScopes and withPurgeWebhookUrls with validation.withoutPurgeScopes and withoutPurgeWebhookUrls for property removal.For more details, visit the release page.
The latest release of the Mittwald PHP SDK, version v2.1.201, introduces several new features and improvements. Key highlights include:
Template Asset Management: A new request and response structure has been introduced for managing assets associated with container templates, enhancing flexibility in specifying and retrieving template-related resources.
Deprecated Functionality: The getTemplateIcon method is deprecated in favor of the new getTemplateAsset method, which offers more comprehensive handling of template resources.
Enhanced List Templates Request: A sortOrder parameter has been added to the list templates request, allowing sorting by specific criteria such as trend over 30 days.
Core Changes: Updates to the ContainerClient interface and implementation, including new request and response classes for template asset management.
Domain Migration Adjustments: Enhancements to the NonMigratableDomain schema and introduction of the OwnerContactIssue class to manage domain migration issues.
Activity Log Enhancements: New classes for handling activity logs related to app installations.
Template Enhancements: Introduction of the TemplateScreenshotsItem class for managing screenshots associated with container templates.
Bug Fixes and Improvements: Improved validation and construction logic for better error handling and usability.
For more details, visit the release page.
The mittwald PHP SDK has been updated to version v2.1.200. This release introduces several new features and improvements:
Enhanced ContributorListContractPartnersOfContributorRequest Object:
limit, skip, page, sort, and order.New ExtensionGetExtensionInstanceForbiddenResponse Class:
For more details, please visit the release page.
The latest release of the mittwald PHP SDK, version 2.1.199, introduces a new feature and several changes:
InvoiceSettingsStatus class has been updated to include the new notReachable status.InvoiceSettingsStatusType enumeration has been modified to define the new notReachable status.For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.416.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.
The mittwald JavaScript SDK version 4.415.0 has been released on July 16, 2026. This update includes the following feature:
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.414.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details on the changes and to view the release, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.413.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.
The mittwald JavaScript SDK has been updated to version 4.412.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more detailed information, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.411.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.
The mittwald JavaScript SDK has been updated to version 4.410.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.
In the week of July 3 to July 10, 2026, the mittwald API introduced several changes, including the addition of new endpoints for mail rate limits and template statistics, the removal of optional properties from project activity responses, and the addition of required properties and new optional request parameters across various endpoints.
In the GET /v2/projects/{projectId}/activities operation, the following changes were made:
/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsZoneCreated]/changes/after was removed from the response with the '200' status./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsZoneCreated]/changes/before was removed from the response with the '200' status.app.version-updated was added to the /items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/name response property for the response status '200'./items/action response property 'anyOf' list for the response status '200': #/components/schemas/de.mittwald.v1.activitylog.DnsDomainDeleted, #/components/schemas/de.mittwald.v1.activitylog.DnsIngressDeleted, #/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged, and #/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged.The GET /v2/container-template-statistics operation had an endpoint added.
The GET /v2/ingresses operation had a new optional request parameter containerId added.
In the GET /v2/mail-addresses/ operation, the following changes were made:
/items/rateLimitChangeRequest was added to the response with the '200' status./items/mailbox/mailsystemSettings was added to the response with the '200' status.In the GET /v2/mail-addresses/{mailAddressId} operation, the following changes were made:
rateLimitChangeRequest was added to the response with the '200' status.mailbox/mailsystemSettings was added to the response with the '200' status.The POST /v2/mail-addresses/{mailAddressId}/actions/request-rate-limit-change operation had an endpoint added.
The GET /v2/mail-rate-limits operation had an endpoint added.
The GET /v2/mail-rate-limits/{mailRateLimitId} operation had an endpoint added.
In the GET /v2/projects/{projectId}/mail-addresses operation, the following changes were made:
/items/rateLimitChangeRequest was added to the response with the '200' status./items/mailbox/mailsystemSettings was added to the response with the '200' status.The GET /v2/projects/{projectId}/stacks operation had a new optional request parameter searchTerm added.
Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
removed the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsZoneCreated]/changes/after' from the response with the '200' status
removed the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DnsZoneCreated]/changes/before' from the response with the '200' status
added the new 'app.version-updated' enum value to the '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/name' response property for the response status '200'
added '#/components/schemas/de.mittwald.v1.activitylog.DnsDomainDeleted, #/components/schemas/de.mittwald.v1.activitylog.DnsIngressDeleted, #/components/schemas/de.mittwald.v1.activitylog.DnsARecordSetManaged, #/components/schemas/de.mittwald.v1.activitylog.DnsMxRecordSetManaged' to the '/items/action' response property 'anyOf' list for the response status '200'
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the optional property '/items/rateLimitChangeRequest' to the response with the '200' status
added the required property '/items/mailbox/mailsystemSettings' to the response with the '200' status
For details, refer to the GET/v2/
added the optional property 'rateLimitChangeRequest' to the response with the '200' status
added the required property 'mailbox/mailsystemSettings' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
added the optional property '/items/rateLimitChangeRequest' to the response with the '200' status
added the required property '/items/mailbox/mailsystemSettings' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the GET/v2/
The mittwald PHP SDK has been updated to version v2.1.198. This release introduces several new features and improvements:
New Endpoints:
Updated Project Usage: The response for project usage now includes a property indicating if model terms approval is required.
AIHostingClient Interface:
customerAcceptModelTermscustomerGetDetailedModelsprojectGetDetailedModelsprojectLinkContainerAIHostingClient Implementation: Implementations for the new methods added in the AIHostingClient interface.
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.409.0. This release includes the following feature:
For more details, please visit the release page.
The mittwald JavaScript SDK has been updated to version 4.408.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.
The mittwald JavaScript SDK has been updated to version 4.407.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.407.0.
The mittwald JavaScript SDK has been updated to version 4.406.0. This release includes the following feature:
For more details, please visit the release page.
The mittwald JavaScript SDK has been updated to version 4.405.1. This release is a version bump only for the package root, with no additional changes or features introduced. For more details, you can view the release on GitHub here.
This week's changelog for the mittwald API includes significant updates such as changes in response property types, the addition and removal of required properties, and the introduction of new optional request parameters across various endpoints.
GET /v2/container-templates has changed for the properties /items/license and /items/name from string to object. This is a breaking change./items/icon has been removed from the response for GET /v2/container-templates. This is a breaking change.GET /v2/container-templates/{templateId} has changed for the properties license and name from string to object. This is a breaking change.icon has been removed from the response for GET /v2/container-templates/{templateId}. This is a breaking change./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after has become nullable for the status 200 in GET /v2/projects/{projectId}/activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/before has become nullable for the status 200 in GET /v2/projects/{projectId}/activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after/softwareVersion has become optional for the status 200 in GET /v2/projects/{projectId}/activities.GET /v2/projects/{projectId}/activities, including:
/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/after/appId/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/after/appVersionId/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationCopyRequested]/changes/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after/software/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after/updatePolicy/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/after/permissions/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/after/permissions/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/before/permissionsGET /v2/projects/{projectId}/activities:
/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/before/appId/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/before/appVersionId/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/before/software/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/before/updatePolicy/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/before/permissionstype has been added to GET /v2/container-templates.GET /v2/container-templates, including:
/items/domains/items/purpose/items/help/items/license/link/items/supportLink/items/userInputs/items/labelGET /v2/container-templates, including:
/items/iconUrl/items/license/name/items/name/de/items/name/enGET /v2/container-templates/{templateId}/icon has been added to retrieve a Container Template icon.GET /v2/customers/{customerId}/projects and GET /v2/projects, including /items/serverShortId.GET /v2/customers/{customerId}/projects and GET /v2/projects, including /items/deletionRequested.409 has been added for POST /v2/files.GET /v2/projects/{projectId}/activities, including:
/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/before/version/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/before/permissionsRead/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/before/permissionsWrite/items/action has been updated to include new schemas in the anyOf list for the status 200 in GET /v2/projects/{projectId}/activities./items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/parameters has become required for the status 200 in GET /v2/projects/{projectId}/activities.GET /v2/projects/{projectId}/activities, including various parameters and descriptions for different actions related to database and app installations.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Breaking the '/items/license' response's property type/format changed from 'string'/'' to 'object'/'' for status '200'
Breaking the '/items/name' response's property type/format changed from 'string'/'' to 'object'/'' for status '200'
Breaking removed the required property '/items/icon' from the response with the '200' status
added the new optional 'query' request parameter 'type'
added the optional property '/items/domains/items/purpose' to the response with the '200' status
added the optional property '/items/help' to the response with the '200' status
added the optional property '/items/license/link' to the response with the '200' status
added the optional property '/items/supportLink' to the response with the '200' status
added the optional property '/items/userInputs/items/label' to the response with the '200' status
added the required property '/items/iconUrl' to the response with the '200' status
added the required property '/items/license/name' to the response with the '200' status
added the required property '/items/name/de' to the response with the '200' status
added the required property '/items/name/en' to the response with the '200' status
For details, refer to the GET/v2/
Breaking the 'license' response's property type/format changed from 'string'/'' to 'object'/'' for status '200'
Breaking the 'name' response's property type/format changed from 'string'/'' to 'object'/'' for status '200'
Breaking removed the required property 'icon' from the response with the '200' status
added the optional property 'domains/items/purpose' to the response with the '200' status
added the optional property 'help' to the response with the '200' status
added the optional property 'license/link' to the response with the '200' status
added the optional property 'supportLink' to the response with the '200' status
added the optional property 'userInputs/items/label' to the response with the '200' status
added the required property 'iconUrl' to the response with the '200' status
added the required property 'license/name' to the response with the '200' status
added the required property 'name/de' to the response with the '200' status
added the required property 'name/en' to the response with the '200' status
For details, refer to the GET/v2/
Breaking the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after' became nullable for the status '200'
Breaking the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/before' became nullable for the status '200'
Breaking the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after/softwareVersion' became optional for the status '200'
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/after/appId' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/after/appVersionId' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationCopyRequested]/changes' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after/software' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/after/updatePolicy' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/after/permissions' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/after/permissions' from the response with the '200' status
Breaking removed the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/before/permissions' from the response with the '200' status
removed the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/before/appId' from the response with the '200' status
removed the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/before/appVersionId' from the response with the '200' status
removed the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/before/software' from the response with the '200' status
removed the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/changes/before/updatePolicy' from the response with the '200' status
removed the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/before/permissions' from the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/before/version' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/before/permissionsRead' to the response with the '200' status
added the optional property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/before/permissionsWrite' to the response with the '200' status
added '#/components/schemas/de.mittwald.v1.activitylog.AppInstallationRequested, #/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareDeleted' to the '/items/action' response property 'anyOf' list for the response status '200'
the response property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/parameters' became required for the status '200'
removed the 'app.systemsoftware-deleted' enum value from the '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationDesiredSystemSoftwareSet]/name' response property for the response status '200'
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/changes/after/version' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationAppVersionSet]/parameters' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.AppInstallationCopyRequested]/parameters' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseCreated]/parameters/description' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseDeleted]/parameters/description' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseDescriptionSet]/parameters/description' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlNameSet]/parameters/description' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/after/permissionsRead' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/changes/after/permissionsWrite' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/parameters/databaseDescription' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserCreated]/parameters/description' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserDeleted]/parameters/databaseDescription' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserDeleted]/parameters/description' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/after/permissionsRead' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/after/permissionsWrite' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/before/permissionsRead' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/changes/before/permissionsWrite' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/parameters/databaseDescription' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseMysqlUserUpdated]/parameters/description' to the response with the '200' status
added the required property '/items/action/anyOf[#/components/schemas/de.mittwald.v1.activitylog.DatabaseVersionSet]/parameters/description' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the unknown operation container-get-template-icon endpoint.
added the optional property '/items/serverShortId' to the response with the '200' status
added the required property '/items/deletionRequested' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
added the optional property '/items/serverShortId' to the response with the '200' status
added the required property '/items/deletionRequested' to the response with the '200' status
For details, refer to the GET/v2/
For details, refer to the POST/v2/
The mittwald JavaScript SDK has been updated to version 4.405.0. This release includes the following feature:
For more details, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.404.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.
The mittwald JavaScript SDK has been updated to version 4.403.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.
The mittwald JavaScript SDK has been updated to version 4.402.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.
The mittwald JavaScript SDK has been updated to version 4.401.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.
The mittwald JavaScript SDK has been updated to version 4.400.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details on the changes, you can view the release notes.
The mittwald JavaScript SDK has been updated to version 4.399.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.
The mittwald JavaScript SDK version 4.398.1 has been released. This update includes a bug fix specifically addressing a compile issue within the Models component. For more details on the changes and to view the release notes, visit the release page.
This week's changes are primarily spec cleanup and new endpoint additions. The conversation-related changes are technically breaking but have no practical impact on existing integrations — the actual API responses remain unchanged.
GET /v2/conversations and GET /v2/conversations/{conversationId} have been restructured. Fields like conversationId, createdAt, mainUser, shortId, status, title, visibility, and all previously optional fields have been moved into the BasicConversation schema and are now composed via allOf. The actual response payloads are unchanged — this is a spec-level reorganization only.GET /v2/conversations/{conversationId}/members and GET /v2/conversations/{conversationId}/messages responses: atlasGroup, department, and group. These fields were accidentally exposed in the spec but were never returned to external API users. Their removal corrects the spec to match actual behavior.de.mittwald.v1.conversation.Department and de.mittwald.v1.conversation.Group have been removed from the API, as they were never part of the public API surface.GET /v2/container-templates to list Container Templates.GET /v2/container-templates/{templateId} to get a Container Template by ID.GET /v2/customers/{customerId}/projects to list Projects belonging to a Customer.GET /v2/projects/{projectId}/domain-migrations to list Domain-Migrations belonging to a Project.POST /v2/projects/{projectId}/stacks to create a Stack.DELETE /v2/stacks/{stackId} to delete a Stack.state has been added to the GET /v2/contributors/{contributorId}/webhook-executions operation.isEmployee has been added to user objects in conversation member and message responses.description has been added to the PATCH /v2/stacks/{stackId} operation.Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
The response schema has been restructured: all conversation fields are now defined in the BasicConversation schema and composed into the response via allOf. This is a spec-level reorganization — the response payload is identical for API consumers. All previously required and optional fields (conversationId, createdAt, mainUser, shortId, status, title, visibility, category, createdBy, lastMessage, lastMessageAt, lastMessageBy, notificationRoles, relatedTo, relations, sharedWith) remain available via BasicConversation.
/items/ response type changed from object to allOf[BasicConversation] for status 200 — response payload is unchanged#/components/schemas/de.mittwald.v1.conversation.BasicConversation to the /items/ response allOf list for status 200For details, refer to the GET/v2/
Same restructuring as above — all conversation fields are now defined in BasicConversation and composed via allOf. The response payload is unchanged.
object to allOf[BasicConversation] for status 200 — response payload is unchanged#/components/schemas/de.mittwald.v1.conversation.BasicConversation to the response body allOf list for status 200For details, refer to the GET/v2/
The fields atlasGroup, department, and group have been removed. These were internal mittwald fields accidentally exposed in the spec — they were never returned to external API users. Their removal corrects the spec to match actual behavior.
/items/allOf[de.mittwald.v1.conversation.User]/atlasGroup from the response with status 200/items/allOf[de.mittwald.v1.conversation.User]/department from the response with status 200/items/allOf[de.mittwald.v1.conversation.User]/group from the response with status 200/items/allOf[de.mittwald.v1.conversation.User]/isEmployee to the response with status 200For details, refer to the GET/v2/
Same cleanup as above — atlasGroup, department, and group were internal fields never returned to external users. Additionally, isEmployee is now officially documented.
createdBy/atlasGroup from Message itemscreatedBy/department from Message itemscreatedBy/group from Message itemsmeta/user/atlasGroup from GenericStatusUpdate and ResubmissionStatusUpdate itemsmeta/user/department from GenericStatusUpdate and ResubmissionStatusUpdate itemsmeta/user/group from GenericStatusUpdate and ResubmissionStatusUpdate itemscreatedBy/isEmployee to Message itemsmeta/user/isEmployee to GenericStatusUpdate and ResubmissionStatusUpdate itemsFor details, refer to the GET/v2/
de.mittwald.v1.conversation.Departmentde.mittwald.v1.conversation.GroupThese schemas were never part of the public API surface and only appeared internally in the spec.
For details, refer to the GET/v2/
For details, refer to the GET/v2/
query request parameter stateFor details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the GET/v2/
For details, refer to the POST/v2/
For details, refer to the DELETE/v2/
descriptionFor details, refer to the PATCH/v2/
The mittwald JavaScript SDK has been updated to version 4.398.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.
The mittwald JavaScript SDK has been updated to version 4.397.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.396.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.
The mittwald JavaScript SDK has been updated to version 4.395.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.
The mittwald JavaScript SDK has been updated to version 4.394.0. This release includes the following feature:
For further information and to view the release notes, visit the release page.
The mittwald JavaScript SDK has been updated to version 4.393.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.
The mittwald JavaScript SDK has been updated to version 4.392.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.
The mittwald JavaScript SDK has been updated to version 4.391.0. This release includes an update to the generated client, enhancing the functionality of the SDK. For more details, you can view the release on GitHub here.
The mittwald JavaScript SDK has been updated to version 4.390.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/api-client-js 4.390.0.
The mittwald JavaScript SDK has been updated to version 4.389.0. This release includes an updated generated client, enhancing the SDK's functionality and performance. For more details, you can view the release on GitHub here.