Summary​

• The GET /v2/app-installations operation has been updated to include several new required properties in the response with a 200 status:

  • /items/appExternalVersion
  • /items/appName
  • /items/systemSoftware/items/externalVersion
  • /items/systemSoftware/items/name
  • /items/systemSoftware/items/updateAvailable
  • /items/updateAvailable

• The GET /v2/app-installations/{appInstallationId} operation has been updated to include the following new required properties in the response with a 200 status:

  • appExternalVersion
  • appName
  • systemSoftware/items/externalVersion
  • systemSoftware/items/name
  • systemSoftware/items/updateAvailable
  • updateAvailable

• The GET /v2/projects/{projectId}/app-installations operation has been updated to include several new required properties in the response with a 200 status:

  • /items/appExternalVersion
  • /items/appName
  • /items/systemSoftware/items/externalVersion
  • /items/systemSoftware/items/name
  • /items/systemSoftware/items/updateAvailable
  • /items/updateAvailable

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "List app installations that a user has access to"​

• added the required property '/items/appExternalVersion' to the response with the '200' status

• added the required property '/items/appName' to the response with the '200' status

• added the required property '/items/systemSoftware/items/externalVersion' to the response with the '200' status

• added the required property '/items/systemSoftware/items/name' to the response with the '200' status

• added the required property '/items/systemSoftware/items/updateAvailable' to the response with the '200' status

• added the required property '/items/updateAvailable' to the response with the '200' status

For details, refer to the GET/v2/app-installations/ endpoint.

Changes in "Get an app installation"​

• added the required property 'appExternalVersion' to the response with the '200' status

• added the required property 'appName' to the response with the '200' status

• added the required property 'systemSoftware/items/externalVersion' to the response with the '200' status

• added the required property 'systemSoftware/items/name' to the response with the '200' status

• added the required property 'systemSoftware/items/updateAvailable' to the response with the '200' status

• added the required property 'updateAvailable' to the response with the '200' status

For details, refer to the GET/v2/app-installations/{appInstallationId}/ endpoint.

Changes in "List app installations belonging to a Project"​

• added the required property '/items/appExternalVersion' to the response with the '200' status

• added the required property '/items/appName' to the response with the '200' status

• added the required property '/items/systemSoftware/items/externalVersion' to the response with the '200' status

• added the required property '/items/systemSoftware/items/name' to the response with the '200' status

• added the required property '/items/systemSoftware/items/updateAvailable' to the response with the '200' status

• added the required property '/items/updateAvailable' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/app-installations/ endpoint.

Client package releases​

mittwald JavaScript SDK Release 4.343.0​

The mittwald JavaScript SDK has been updated to version 4.343.0. This release includes the following feature:

• Updated the generated client to enhance functionality (commit 65629b9).

For more details, visit the release page.

Summary​

• The response property destination became optional for the status 200 in the GET /v2/cronjobs/{cronjobId} operation. This is a breaking change.
• The response properties appId and appInstallationId changed their type/format from string/uuid to string/'' for the status 200 in the GET /v2/cronjobs/{cronjobId} operation. This is a breaking change.
• The response property /items/destination became optional for the status 200 in the GET /v2/projects/{projectId}/cronjobs operation. This is a breaking change.
• The response properties /items/appId and /items/appInstallationId changed their type/format from string/uuid to string/'' for the status 200 in the GET /v2/projects/{projectId}/cronjobs operation. This is a breaking change.
• The request property failedExecutionAlertThreshold's maximum value was set to 80.00 in the POST /v2/projects/{projectId}/cronjobs operation.
• An optional property target was added to the response with the 200 status in the GET /v2/cronjobs/{cronjobId} operation.
• A new optional request property target was added in the PATCH /v2/cronjobs/{cronjobId} operation.
• The required property /items/serverGroupId was added to the response with the 200 status in the GET /v2/projects operation.
• The required property serverGroupId was added to the response with the 200 status in the GET /v2/projects/{projectId} operation.
• A new optional request parameter includeServiceCronjobs was added in the GET /v2/projects/{projectId}/cronjobs operation.
• An optional property /items/target was added to the response with the 200 status in the GET /v2/projects/{projectId}/cronjobs operation.
• A new optional request property target was added in the POST /v2/projects/{projectId}/cronjobs operation.
• The request property appId became optional in the POST /v2/projects/{projectId}/cronjobs operation.
• The request property destination became optional in the POST /v2/projects/{projectId}/cronjobs operation.
• The required property /items/groupId was added to the response with the 200 status in the GET /v2/servers operation.
• The required property groupId was added to the response with the 200 status in the GET /v2/servers/{serverId} operation.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Get a cronjob"​

• ⚠️ Breaking: the response property 'destination' became optional for the status '200'

• ⚠️ Breaking: the 'appId' response's property type/format changed from 'string'/'uuid' to 'string'/'' for status '200'

• ⚠️ Breaking: the 'appInstallationId' response's property type/format changed from 'string'/'uuid' to 'string'/'' for status '200'

• added the optional property 'target' to the response with the '200' status

For details, refer to the GET/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "List cronjobs belonging to a Project"​

• ⚠️ Breaking: the response property '/items/destination' became optional for the status '200'

• ⚠️ Breaking: the '/items/appId' response's property type/format changed from 'string'/'uuid' to 'string'/'' for status '200'

• ⚠️ Breaking: the '/items/appInstallationId' response's property type/format changed from 'string'/'uuid' to 'string'/'' for status '200'

• added the new optional 'query' request parameter 'includeServiceCronjobs'

• added the optional property '/items/target' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/cronjobs/ endpoint.

Changes in "Create a cronjob"​

• the 'failedExecutionAlertThreshold' request property's max was set to '80.00'

• added the new optional request property 'target'

• the request property 'appId' became optional

• the request property 'destination' became optional

For details, refer to the POST/v2/projects/{projectId}/cronjobs/ endpoint.

Changes in "Update a cronjob"​

• added the new optional request property 'target'

For details, refer to the PATCH/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "List Projects belonging to the executing user"​

• added the required property '/items/serverGroupId' to the response with the '200' status

For details, refer to the GET/v2/projects/ endpoint.

Changes in "Get a Project"​

• added the required property 'serverGroupId' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/ endpoint.

Changes in "List Servers belonging to the executing user"​

• added the required property '/items/groupId' to the response with the '200' status

For details, refer to the GET/v2/servers/ endpoint.

Changes in "Get a Server"​

• added the required property 'groupId' to the response with the '200' status

For details, refer to the GET/v2/servers/{serverId}/ endpoint.

Client package releases​

mittwald JavaScript SDK Release 4.342.0​

The mittwald JavaScript SDK has been updated to version 4.342.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.

mittwald JavaScript SDK Release 4.341.0​

The mittwald JavaScript SDK has been updated to version 4.341.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, please refer to the release page.

mittwald JavaScript SDK Release 4.340.0​

The mittwald JavaScript SDK has been updated to version 4.340.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub here.

mittwald JavaScript SDK Release 4.339.0​

The mittwald JavaScript SDK has been updated to version 4.339.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 Release 4.338.1​

The mittwald JavaScript SDK has been updated to version 4.338.1. This release includes a version bump for the package root. For more details, you can view the release on GitHub here.

mittwald JavaScript SDK Release 4.338.0​

The mittwald JavaScript SDK has been updated to version 4.338.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.338.0.

mittwald JavaScript SDK Release 4.337.0​

The mittwald JavaScript SDK has been updated to version 4.337.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.

Summary​

• The API operation app-execute-action has been removed and replaced with deprecated-app-installation-execute-action.
• A new optional request parameter onlyRecommended has been added to the GET operation for listing update candidates at the endpoint /v2/apps/{appId}/versions/{baseAppVersionId}/update-candidates.
• The required property modelTermsApprovalRequired has been added to the response with a 200 status for the GET operation at the endpoint /v2/customers/{customerId}/ai-hosting.
• A new endpoint has been added for the GET operation to retrieve a list of currently active models at /v2/customers/{customerId}/ai-hosting-models.
• A new endpoint has been added for the POST operation to accept model terms for a customer at /v2/customers/{customerId}/ai-hosting-models/actions/accept-terms.
• The required property modelTermsApprovalRequired has also been added to the response with a 200 status for the GET operation at the endpoint /v2/projects/{projectId}/ai-hosting.
• A new endpoint has been added for the GET operation to retrieve a list of currently active models at /v2/projects/{projectId}/ai-hosting-models.
• A new endpoint has been added for the POST operation to create or rotate a pull-image webhook token at /v2/stacks/{stackId}/services/{serviceId}/webhook-token.
• A new endpoint has been added for the GET operation to call a pull-image webhook at /v2/stacks/{stackId}/webhooks/pull-image.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "app-execute-action"​

• api operation id 'app-execute-action' removed and replaced with 'deprecated-app-installation-execute-action'

For details, refer to the unknown operation app-execute-action endpoint.

Changes in "List update candidates belonging to an app version"​

• added the new optional 'query' request parameter 'onlyRecommended'

For details, refer to the GET/v2/apps/{appId}/versions/{baseAppVersionId}/update-candidates/ endpoint.

Changes in "Get ai hosting plan and usages of a customer"​

• added the required property 'modelTermsApprovalRequired' to the response with the '200' status

For details, refer to the GET/v2/customers/{customerId}/ai-hosting/ endpoint.

Changes in "Get a list of currently active models"​

• endpoint added

For details, refer to the GET/v2/customers/{customerId}/ai-hosting-models/ endpoint.

Changes in "Accepts the model terms for a customer"​

• endpoint added

For details, refer to the POST/v2/customers/{customerId}/ai-hosting-models/actions/accept-terms/ endpoint.

Changes in "Get ai hosting plan and usages of a project. Same as the customer route, but less details"​

• added the required property 'modelTermsApprovalRequired' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/ai-hosting/ endpoint.

Changes in "Get a list of currently active models"​

• endpoint added

For details, refer to the GET/v2/projects/{projectId}/ai-hosting-models/ endpoint.

Changes in "Create or rotate pull-image webhook token"​

• endpoint added

For details, refer to the POST/v2/stacks/{stackId}/services/{serviceId}/webhook-token/ endpoint.

Changes in "Call pull-image webhook"​

• endpoint added

For details, refer to the GET/v2/stacks/{stackId}/webhooks/pull-image/ endpoint.

Client package releases​

mittwald JavaScript SDK Release 4.336.0​

The mittwald JavaScript SDK has been updated to version 4.336.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.

mittwald JavaScript SDK Release 4.335.0​

The mittwald JavaScript SDK has been updated to version 4.335.0. This release includes the following feature:

• Updated the generated client to enhance functionality (commit fac3120).

For more details, visit the release page.

mittwald JavaScript SDK Release 4.334.0​

The mittwald JavaScript SDK has been updated to version 4.334.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.334.0.

mittwald JavaScript SDK Release 4.333.0​

The mittwald JavaScript SDK has been updated to version 4.333.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.

Summary​

• The response property type for the GET /v2/conversations/{conversationId}/messages operation has changed from 'object' to '' for status '200'. Additionally, several required properties (conversationId, createdAt, messageContent, and type) have been removed from the response. This is a breaking change.

• The response property type for the GET /v2/projects/{projectId}/mail-settings operation has changed for both blacklist/items/ and whitelist/items/ from 'string' with format 'idn-email' to 'string' for status '200'.

• The request body for the PATCH /v2/projects/{projectId}/mail-settings/{mailSetting} and PUT /v2/projects/{projectId}/mail-settings/{mailSetting} operations has had 'subschema #1, subschema #2' removed from the 'oneOf' list.

• The request property type for the PUT /v2/projects/{projectId}/mailsettings/blacklist and PUT /v2/projects/{projectId}/mailsettings/whitelist operations has changed from 'string' with format 'idn-email' to 'string'.

• The optional property internal and meta have been removed from the response of the GET /v2/conversations/{conversationId}/messages operation.

• A new pattern has been added to the request property blacklist/items/ and whitelist/items/ for the PUT /v2/projects/{projectId}/mailsettings/blacklist and PUT /v2/projects/{projectId}/mailsettings/whitelist operations.

• The schema de.mittwald.v1.verification.VerifyAddressConfidence and de.mittwald.v1.verification.VerifyAddressResponse have been removed from the API schema.

• The non-success response with status '400' has been removed from the POST /v2/actions/verify-address operation.

• The response property oneOf list for the GET /v2/conversations/{conversationId}/messages operation has been updated to include #/components/schemas/de.mittwald.v1.conversation.ResubmissionStatusUpdate and #/components/schemas/de.mittwald.v1.conversation.GenericStatusUpdate.

• A new non-success response with status '412' has been added to the POST /v2/domain-transferable operation.

• A new optional request parameter types has been added to the GET /v2/orders operation.

• The endpoint PUT /v2/project-backups/{projectBackupId}/expiration-time has been added to update a Backup's expiration time.

• The response property pattern for blacklist/items/ and whitelist/items/ has been added for the GET /v2/projects/{projectId}/mail-settings operation.

• The request body oneOf list has been updated to include 'subschema #1, subschema #2' for the PATCH /v2/projects/{projectId}/mail-settings/{mailSetting} and PUT /v2/projects/{projectId}/mail-settings/{mailSetting} operations.

• The endpoint GET /v2/stacks has been added to list Stacks belonging to the executing user.

• The required property refreshToken has been added to the response of the PUT /v2/users/self/credentials/password operation.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Get all message of the conversation"​

• ⚠️ Breaking: the '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/' response's property type/format changed from 'object'/'' to ''/'' for status '200'

• ⚠️ Breaking: removed the required property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/conversationId' from the response with the '200' status

• ⚠️ Breaking: removed the required property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/createdAt' from the response with the '200' status

• ⚠️ Breaking: removed the required property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/messageContent' from the response with the '200' status

• ⚠️ Breaking: removed the required property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/type' from the response with the '200' status

• removed the optional property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/internal' from the response with the '200' status

• removed the optional property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/meta' from the response with the '200' status

• added '#/components/schemas/de.mittwald.v1.conversation.ResubmissionStatusUpdate, #/components/schemas/de.mittwald.v1.conversation.GenericStatusUpdate' to the '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/' response property 'oneOf' list for the response status '200'

For details, refer to the GET/v2/conversations/{conversationId}/messages/ endpoint.

Changes in "List mail settings of a Project"​

• ⚠️ Breaking: the 'blacklist/items/' response's property type/format changed from 'string'/'idn-email' to 'string'/'' for status '200'

• ⚠️ Breaking: the 'whitelist/items/' response's property type/format changed from 'string'/'idn-email' to 'string'/'' for status '200'

• the 'blacklist/items/' response's property pattern ^([a-zA-Z0-9.!#$%&'*\/=?^_{|}~-]+@[a-zA-Z0-9-*]+(?:\.([a-zA-Z0-9-]+|\*))+)$ was added for the status '200'

• the 'whitelist/items/' response's property pattern ^([a-zA-Z0-9.!#$%&'*\/=?^_{|}~-]+@[a-zA-Z0-9-*]+(?:\.([a-zA-Z0-9-]+|\*))+)$ was added for the status '200'

For details, refer to the GET/v2/projects/{projectId}/mail-settings/ endpoint.

Changes in "Update a mail setting of a Project"​

• ⚠️ Breaking: removed 'subschema #1, subschema #2' from the request body 'oneOf' list

• added 'subschema #1, subschema #2' to the request body 'oneOf' list

For details, refer to the PATCH/v2/projects/{projectId}/mail-settings/{mailSetting}/ endpoint.

Changes in "Update a mail setting of a Project"​

• ⚠️ Breaking: removed 'subschema #1, subschema #2' from the request body 'oneOf' list

• added 'subschema #1, subschema #2' to the request body 'oneOf' list

For details, refer to the PUT/v2/projects/{projectId}/mail-settings/{mailSetting}/ endpoint.

Changes in "Update blacklist for a given project ID"​

• ⚠️ Breaking: the 'blacklist/items/' request property type/format changed from 'string'/'idn-email' to 'string'/''

• added the pattern ^([a-zA-Z0-9.!#$%&'*\/=?^_{|}~-]+@[a-zA-Z0-9-*]+(?:\.([a-zA-Z0-9-]+|\*))+)$ to the request property 'blacklist/items/'

For details, refer to the PUT/v2/projects/{projectId}/mailsettings/blacklist/ endpoint.

Changes in "Update whitelist for a given project ID"​

• ⚠️ Breaking: the 'whitelist/items/' request property type/format changed from 'string'/'idn-email' to 'string'/''

• added the pattern ^([a-zA-Z0-9.!#$%&'*\/=?^_{|}~-]+@[a-zA-Z0-9-*]+(?:\.([a-zA-Z0-9-]+|\*))+)$ to the request property 'whitelist/items/'

For details, refer to the PUT/v2/projects/{projectId}/mailsettings/whitelist/ endpoint.

Changes in ""​

• removed the schema 'de.mittwald.v1.verification.VerifyAddressConfidence'

• removed the schema 'de.mittwald.v1.verification.VerifyAddressResponse'

For details, refer to the unknown operation endpoint.

Changes in "Check if an address exists"​

• removed the non-success response with the status '400'

For details, refer to the POST/v2/actions/verify-address/ endpoint.

Changes in "Check if a Domain is available to transfer"​

• added the non-success response with the status '412'

For details, refer to the POST/v2/domain-transferable/ endpoint.

Changes in "Get list of Orders"​

• added the new optional 'query' request parameter 'types'

For details, refer to the GET/v2/orders/ endpoint.

Changes in "Update a Backup's expiration time"​

• endpoint added

For details, refer to the PUT/v2/project-backups/{projectBackupId}/expiration-time/ endpoint.

Changes in "List Stacks belonging to the executing user"​

• endpoint added

For details, refer to the GET/v2/stacks/ endpoint.

Changes in "Change your password"​

• added the required property 'refreshToken' to the response with the '200' status

For details, refer to the PUT/v2/users/self/credentials/password/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.197​

The latest release of the mittwald PHP SDK, version 2.1.197, introduces some significant changes and enhancements.

Breaking Changes​

• The VerificationVerifyAddressBadRequestResponse class has been removed from the codebase.

Enhancements​

• Documentation for the country field in VerificationVerifyAddressRequest and VerificationVerifyAddressRequestBody has been updated. It now specifies that the input can be the full English or German name in addition to the ISO 3166-2 country codes.

For more details, visit the release page.

mittwald JavaScript SDK Release 4.332.0​

The mittwald JavaScript SDK has been updated to version 4.332.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.332.0.

mittwald JavaScript SDK Release 4.331.0​

The mittwald JavaScript SDK has been updated to version 4.331.0. This release includes the following feature:

• Updated the generated client to improve functionality and performance. For more details, refer to the commit f295949.

For the full release notes and to download the latest version, visit the release page.

mittwald JavaScript SDK Release 4.330.0​

The mittwald JavaScript SDK has been updated to version 4.330.0, released on March 19, 2026. 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.

mittwald JavaScript SDK Release 4.329.0​

The mittwald JavaScript SDK has been updated to version 4.329.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.

mittwald JavaScript SDK Release 4.328.0​

The mittwald JavaScript SDK has been updated to version 4.328.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.

mittwald JavaScript SDK Release 4.327.0​

The mittwald JavaScript SDK has been updated to version 4.327.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 Release 4.326.0​

The mittwald JavaScript SDK has been updated to version 4.326.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.326.0.

Summary​

• The request property database/projectId was removed from the POST /v2/projects/{projectId}/mysql-databases operation.
• Non-success responses with status 400, 412, and 409 were added to the POST /v2/app-installations/{appInstallationId}/actions/{action} and POST /v2/dns-zones operations.
• A new optional request parameter versionRange was added to the GET /v2/apps/{appId}/versions operation.
• A new optional request property avoidEmailConfirmation was added to the PATCH /v2/domains/{domainId}/contacts/{contact} operation.
• Several new endpoints were added, including:
  • GET /v2/licenses/{licenseId} for retrieving a license.
  • POST /v2/licenses/{licenseId}/actions/rotate-key for rotating a license key.
  • GET /v2/licenses/{licenseId}/contract for retrieving the contract for a given license.
  • POST /v2/projects/{projectId}/actions/validate-license-key for validating a license key for a project.
  • GET /v2/projects/{projectId}/licenses for listing licenses belonging to a project.
• The optional property /items/updateSchedule was added to the response with status 200 for the GET /v2/projects/{projectId}/stacks}, GET /v2/stacks/{stackId}, PATCH /v2/stacks/{stackId}, and PUT /v2/stacks/{stackId} operations.
• The request property orderType received a new enum value license in the POST /v2/order-previews and POST /v2/orders operations.
• The request property orderData received new oneOf entries in the POST /v2/order-previews and POST /v2/orders operations.
• The response body for the POST /v2/order-previews operation now includes #/components/schemas/de.mittwald.v1.order.LicenseOrderPreviewResponse in the anyOf list for the response status 200.
• The request property minimum value for settings/ttl/seconds was decreased from 300.00 to 60.00 for various record types in the PUT /v2/dns-zones/{dnsZoneId}/record-sets/{recordSet} and deprecated operations.
• The minimum value for the response property settings/ttl/seconds was decreased from 300.00 to 60.00 for various record types in the GET /v2/dns-zones/{dnsZoneId} and GET /v2/projects/{projectId}/dns-zones operations.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Get a DNS Zone"​

• The 'recordSet/caa/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCAAComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The 'recordSet/cname/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The 'recordSet/combinedARecords/oneOf[#/components/schemas/de.mittwald.v1.dns.CombinedACustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The 'recordSet/mx/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The 'recordSet/srv/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The 'recordSet/txt/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordTXTComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

For details, refer to the GET/v2/dns-zones/{dnsZoneId}/ endpoint.

Changes in "List DNS Zones belonging to a Project"​

• The '/items/recordSet/caa/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCAAComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The '/items/recordSet/cname/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The '/items/recordSet/combinedARecords/oneOf[#/components/schemas/de.mittwald.v1.dns.CombinedACustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The '/items/recordSet/mx/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The '/items/recordSet/srv/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

• The '/items/recordSet/txt/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordTXTComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' response property's min was decreased from '300.00' to '60.00' for the response status '200'

For details, refer to the GET/v2/projects/{projectId}/dns-zones/ endpoint.

Changes in "Create a MySQL database with a MySQL user"​

• removed the request property 'database/projectId'

For details, refer to the POST/v2/projects/{projectId}/mysql-databases/ endpoint.

Changes in "Trigger a runtime action belonging to an app installation"​

• added the non-success response with the status '400'

• added the non-success response with the status '412'

For details, refer to the unknown operation app-execute-action endpoint.

Changes in "List app versions belonging to an app"​

• added the new optional 'query' request parameter 'versionRange'

For details, refer to the GET/v2/apps/{appId}/versions/ endpoint.

Changes in "Create a DNS Zone"​

• added the non-success response with the status '409'

For details, refer to the POST/v2/dns-zones/ endpoint.

Changes in "Update a record set on a DNS Zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.CombinedACustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCAAComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordTXTComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

For details, refer to the PUT/v2/dns-zones/{dnsZoneId}/record-sets/{recordSet}/ endpoint.

Changes in "updates a-records for a specific zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.CombinedACustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/acombined/custom/ endpoint.

Changes in "updates cname-record for a specific zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/cname/ endpoint.

Changes in "updates mx-records for a specific zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/mx/custom/ endpoint.

Changes in "updates srv-records for a specific zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/srv/ endpoint.

Changes in "updates txt-records for a specific zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordTXTComponent]/settings/ttl/oneOf[#/components/schemas/de.mittwald.v1.dns.TtlSeconds]/seconds' request property's min was decreased from '300.00' to '60.00'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/txt/ endpoint.

Changes in "Update a contact of a Domain"​

• added the new optional request property 'avoidEmailConfirmation'

For details, refer to the PATCH/v2/domains/{domainId}/contacts/{contact}/ endpoint.

Changes in "Get a license"​

• endpoint added

For details, refer to the GET/v2/licenses/{licenseId}/ endpoint.

Changes in "rotate a License's key, i.e. revoke the old and generate a new one"​

• endpoint added

For details, refer to the POST/v2/licenses/{licenseId}/actions/rotate-key/ endpoint.

Changes in "Return the Contract for the given License"​

• endpoint added

For details, refer to the GET/v2/licenses/{licenseId}/contract/ endpoint.

Changes in "Preview Order"​

• added the new 'license' enum value to the request property 'orderType'

• added '#/components/schemas/de.mittwald.v1.order.LicenseOrderPreview' to the 'orderData' request property 'oneOf' list

• added '#/components/schemas/de.mittwald.v1.order.LicenseOrderPreviewResponse' to the response body 'anyOf' list for the response status '200'

For details, refer to the POST/v2/order-previews/ endpoint.

Changes in "Create an Order"​

• added the new 'license' enum value to the request property 'orderType'

• added '#/components/schemas/de.mittwald.v1.order.LicenseOrder' to the 'orderData' request property 'oneOf' list

For details, refer to the POST/v2/orders/ endpoint.

Changes in "Validate a License's key for a project"​

• endpoint added

For details, refer to the POST/v2/projects/{projectId}/actions/validate-license-key/ endpoint.

Changes in "List Licenses belonging to a Project"​

• endpoint added

For details, refer to the GET/v2/projects/{projectId}/licenses/ endpoint.

Changes in "List Stacks belonging to a Project"​

• added the optional property '/items/updateSchedule' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/stacks/ endpoint.

Changes in "Get a Stack"​

• added the optional property 'updateSchedule' to the response with the '200' status

For details, refer to the GET/v2/stacks/{stackId}/ endpoint.

Changes in "Create, update or delete Services or Volumes belonging to a Stack"​

• added the optional property 'updateSchedule' to the response with the '200' status

For details, refer to the PATCH/v2/stacks/{stackId}/ endpoint.

Changes in "Declaratively create, update or delete Services or Volumes belonging to a Stack"​

• added the optional property 'updateSchedule' to the response with the '200' status

For details, refer to the PUT/v2/stacks/{stackId}/ endpoint.

Changes in "Set an update schedule for a Stack"​

• endpoint added

For details, refer to the PUT/v2/stacks/{stackId}/update-schedule/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.192​

The latest release of the mittwald PHP SDK, version 2.1.192, introduces several new features and improvements. A key addition is the new API endpoint for setting an update schedule for a stack, allowing users to define cron-based schedules for updates. This release also includes enhanced descriptions in API request and response schemas, providing better clarity on command, entrypoint, environment variables, and resource specifications such as CPU and memory limits.

Documentation has been improved to offer clearer guidance on expected formats and examples, aiding developers in API integration. New methods, such as setStackUpdateSchedule, have been added to the ContainerClient interface, and various response classes have been created for error handling in this method.

Schema updates include detailed descriptions for resource specifications and new fields in the StackResponse schema to support scheduling updates. Additionally, consistency improvements have been made in request schemas for better semantic understanding.

For more details, visit the release page.

mittwald PHP SDK v2.1.191 Release Summary​

The latest release of the mittwald PHP SDK, version v2.1.191, introduces a comprehensive License API, enhancing the SDK's capabilities in license management. This update includes:

• LicenseClient Implementation: New functionalities for managing licenses, such as fetching a single license, listing licenses for a project, rotating license keys, and validating license keys for a project.

• Response Classes: Introduction of various response classes for operations like GetLicense, ListLicensesForProject, and RotateLicenseKey, providing detailed response handling for different scenarios.

• Data Models: Addition of data models for licenses, keys, and related entities, along with enums and request/response classes to support these operations.

• Enhancements: New schema definitions for input validation and response handling, along with improved functionality for processing license keys.

• License Order Support: Integration for managing TYPO3 ELTS license orders, including key management and version handling.

This release significantly enhances the SDK's ability to manage licenses effectively, ensuring robust API interactions for various license-related operations.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.190​

The latest release of the mittwald PHP SDK, version 2.1.190, introduces several significant updates.

Breaking Changes​

• The deprecated method deprecatedCronjobAbortExecution has been removed from the CronjobClient interface, along with its related classes and functionality.

Features​

• A new boolean property avoidEmailConfirmation has been added to the UpdateDomainContactRequest and UpdateDomainContactRequestBody classes. This property allows users to bypass email confirmation during updates, which may lead to a 60-day transfer lock on the domain.

Improvements​

• Enhancements have been made to the UpdateDomainContactRequestBody class, including methods to set and unset the avoidEmailConfirmation parameter, with added validation during input processing.

No specific bug fixes were mentioned in this release.

For more details, visit the release page.

mittwald JavaScript SDK Release 4.311.0​

The mittwald JavaScript SDK has been updated to version 4.311.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.311.0.

mittwald JavaScript SDK Release 4.310.1​

The mittwald JavaScript SDK version 4.310.1 has been released. This update primarily addresses a bug fix related to compatibility with Axios versions greater than 1.13.2. For more details on the changes, you can view the release notes.

mittwald JavaScript SDK Release 4.310.0​

The mittwald JavaScript SDK has been updated to version 4.310.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.310.0.

mittwald JavaScript SDK Release 4.309.0​

The mittwald JavaScript SDK has been updated to version 4.309.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.309.0.

mittwald JavaScript SDK Release 4.308.0​

The mittwald JavaScript SDK has been updated to version 4.308.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 Release 4.307.0​

The mittwald JavaScript SDK has been updated to version 4.307.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.307.0.

mittwald JavaScript SDK Release 4.306.0​

The mittwald JavaScript SDK has been updated to version 4.306.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.

Summary​

• The required property name has been removed from the response schema with the 409 status for the DELETE operation on the path /v2/users/self. This is now compliant to the common Error type that was already returned.
• The optional property info has been removed from the response with the 409 status for the DELETE operation on the path /v2/users/self.
• The required property type has been added to the response with the 409 status for the DELETE operation on the path /v2/users/self.
• The new migrating enum value has been added to the /items/status response property for the 200 status in the GET operation on the path /v2/servers.
• The new migrating enum value has also been added to the status response property for the 200 status in the GET operation on the path /v2/servers/{serverId}.
• A non-success response with the status 400 has been added for the POST operation on the path /v2/actions/verify-address.
• The non-success response with the status 500 has been removed for the POST operation on the path /v2/actions/verify-address.
• The non-success response with the status 500 has also been removed for the POST operation on the path /v2/actions/verify-company.
• The optional property /items/lastError has been added to the response with the 200 status for the GET operation on the path /v2/app-installations.
• The optional property lastError has been added to the response with the 200 status for the GET operation on the path /v2/app-installations/{appInstallationId}.
• A non-success response with the status 403 has been added for the GET operation on the path /v2/contributors/{contributorId}/dashboard.
• The optional property /items/lastError has been added to the response with the 200 status for the GET operation on the path /v2/projects/{projectId}/app-installations.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Delete your account and all your personal data"​

• removed the required property 'name' from the response with the '409' status, which was never actually returned

• removed the optional property 'info' from the response with the '409' status

• added the required property 'type' to the response with the '409' status

For details, refer to the DELETE/v2/users/self/ endpoint.

Changes in "List Servers belonging to the executing user"​

• added the new 'migrating' enum value to the '/items/status' response property for the response status '200'

For details, refer to the GET/v2/servers/ endpoint.

Changes in "Get a Server"​

• added the new 'migrating' enum value to the 'status' response property for the response status '200'

For details, refer to the GET/v2/servers/{serverId}/ endpoint.

Changes in "Check if an address exists"​

• added the non-success response with the status '400'

• removed the non-success response with the status '500'

For details, refer to the POST/v2/actions/verify-address/ endpoint.

Changes in "Check if a company exists"​

• removed the non-success response with the status '500'

For details, refer to the POST/v2/actions/verify-company/ endpoint.

Changes in "List app installations that a user has access to"​

• added the optional property '/items/lastError' to the response with the '200' status

For details, refer to the GET/v2/app-installations/ endpoint.

Changes in "Get an app installation"​

• added the optional property 'lastError' to the response with the '200' status

For details, refer to the GET/v2/app-installations/{appInstallationId}/ endpoint.

Changes in "Get the Stripe Dashboard Link for a contributor"​

• added the non-success response with the status '403'

For details, refer to the GET/v2/contributors/{contributorId}/dashboard/ endpoint.

Changes in "List app installations belonging to a Project"​

• added the optional property '/items/lastError' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/app-installations/ endpoint.

Client package releases​

Release Summary: mittwald PHP SDK v2.1.185​

The mittwald PHP SDK has been updated to version v2.1.185. This release introduces several enhancements and schema updates aimed at improving the clarity and functionality of the SDK.

Enhancements​

• DatabaseClient Interface and Implementation: The Create a MySQLDatabase with a MySQLUser method now includes detailed descriptions emphasizing its asynchronous nature and guidance on checking the database status post-creation.
• New Response Class: A ContributorGetLoginLinkForbiddenResponse class has been added to handle 403 Forbidden responses during the login link process.

Schema Updates​

• CharacterSettings: Descriptions and examples for characterSet and collation properties have been added to clarify valid values and sources.
• CreateMySqlDatabase: The schema now includes descriptions for description and version properties, providing users with contextual information.
• CreateMySqlUser: Detailed descriptions and examples for accessIpMask, accessLevel, and externalAccess have been added.
• CreateMySqlUserWithDatabase: The schema has been updated with detailed descriptions for accessLevel and externalAccess, clarifying user permissions and external connectivity scenarios.
• MySqlDatabase: Enhanced descriptions for properties like description, externalHostname, hostname, name, and version to provide more context.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.184​

The mittwald PHP SDK has been updated to version v2.1.184. This release introduces several enhancements and updates to improve error tracking and management within the AppInstallation class.

Added​

• lastError Property: A new lastError property has been added to the AppInstallation class. This property records the last error encountered during an update and resets upon a successful update, aiding in better issue tracking.

Enhanced​

• Getter and Setter for lastError: New methods getLastError(), withLastError(string $lastError), and withoutLastError() have been introduced to facilitate the management of the lastError property.

Updated​

• Input Processing: The input processing for the AppInstallation class now includes the lastError property, allowing it to be set and retrieved as part of the installation state.
• Output Serialization: The output serialization method has been updated to include the lastError, enabling external clients to view any errors that occurred during the last update.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.183​

The latest release of the mittwald PHP SDK, version 2.1.183, introduces significant improvements in response handling, particularly for address verification and user deletion processes.

Key Updates:​

• New Additions:

  • A new class, VerificationVerifyAddressBadRequestResponse, has been added to enhance error handling for invalid address verification requests.

• Changes:

  • The UnexpectedResponseException in MiscClientImpl now properly handles HTTP status code 400 for bad requests, utilizing the new VerificationVerifyAddressBadRequestResponse.
  • The DeleteUserConflictResponse has been updated to adopt a more generalized error response structure based on the Error schema, replacing the previous DeleteUserConflictResponseBody.
  • The obsolete DeleteUserConflictResponseBody and its associated properties, including the DeleteUserConflictResponseBodyName enumeration, have been removed.
  • Documentation in the UserClient and UserClientImpl interfaces has been corrected to fix typos in the authentication method descriptions.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.182​

The latest release of the mittwald PHP SDK, version v2.1.182, introduces several changes aimed at simplifying the address verification response structure:

• Removed Confidence Property: The confidence property has been removed from the VerificationVerifyAddressOKResponse and VerificationVerifyAddressOKResponseBody classes. The response now focuses solely on the exists boolean value to indicate address existence.

• Updated Constructor: The constructor for VerificationVerifyAddressOKResponseBody has been updated to remove the confidence parameter, now only requiring the exists boolean flag.

• Removed Getter and Setter for Confidence: Methods for accessing and modifying the confidence property have been eliminated, streamlining the class to focus on the exists property.

These updates are designed to enhance the clarity and usability of the API's address verification response. For more details, visit the release page.

mittwald PHP SDK Release v2.1.181​

The mittwald PHP SDK has been updated to version v2.1.181. This release introduces new features and changes aimed at enhancing the functionality of the SDK.

Added Features​

• Verification of Address Response: The VerificationVerifyAddressOKResponse class now includes a confidence property, providing a measure of confidence in the address verification results.

• Server Status Enumeration: The ServerStatus enum has been expanded with a new case, migrating, to indicate an ongoing migration process.

Changes​

• VerificationVerifyAddressOKResponse: The confidence property is now a required part of the response body, alongside exists.

• VerificationVerifyAddressOKResponseBody:

  • The constructor now accepts a confidence parameter.
  • A getConfidence() method has been added to retrieve the confidence level.
  • A withConfidence() method is available for validating and setting the confidence level.
  • JSON serialization now includes the confidence level.

• ServerStatus Enum: A new case migrating has been added to reflect an additional server status.

For more details, visit the release page.

mittwald JavaScript SDK Release 4.301.0​

The mittwald JavaScript SDK has been updated to version 4.301.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 Release 4.300.0​

The mittwald JavaScript SDK has been updated to version 4.300.0. This release includes the following feature:

• Updated generated client (commit 9da879a).

For more details, visit the release page.

mittwald JavaScript SDK Release 4.299.0​

The mittwald JavaScript SDK has been updated to version 4.299.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.299.0.

mittwald JavaScript SDK Release 4.298.0​

The mittwald JavaScript SDK version 4.298.0 has been released. This update includes the following feature:

• Updated the generated client to enhance functionality and performance (commit 07dd179).

For more details, visit the release page.

mittwald JavaScript SDK Release 4.297.0​

The mittwald JavaScript SDK has been updated to version 4.297.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.

Summary​

• The POST operation at the path /v2/actions/list-ingresses-compatible-with-certificate now has an alternative request body containing only a certificateId.
• The POST operation at the path /v2/certificate-requests now has an alternative request body for the creation of 'DNS' certificates.
• Several required response properties have become optional for the status '200' in the GET operations at the paths /v2/certificates and /v2/certificates/{certificateId}:
  • certificate
  • isExpired
  • lastExpirationThresholdHit
  • validFrom
  • validTo
• A new value '3' (representing 'DNS') has been added to the enum certificateType of component certificate-request.
• The optional property dnsCertSpec has been added to the certificate-request component.
• The response property contact has become optional for the status '201' in the POST operation at the path /v2/certificate-requests.
• Non-success responses of the status '409' and '412' have been added for the POST operation at the path /v2/certificate-requests.
• The optional property /items/information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/customer-invites.
• The optional property information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/customer-invites/{customerInviteId}.
• The optional property information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/customer-token-invite.
• The optional property /items/information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/customers/{customerId}/invites.
• The optional property information/userId has been removed from the response with the '201' status in the POST operation at the path /v2/customers/{customerId}/invites.
• The optional property /items/information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/project-invites.
• The optional property information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/project-invites/{projectInviteId}.
• The optional property information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/project-token-invite.
• The optional property /items/information/userId has been removed from the response with the '200' status in the GET operation at the path /v2/projects/{projectId}/invites.
• The optional property information/userId has been removed from the response with the '201' status in the POST operation at the path /v2/projects/{projectId}/invites.
• The optional property /items/isMailAddressInvalid has been added to the response with the '200' status in the GET operation at the path /v2/customers.
• The optional property isMailAddressInvalid has been added to the response with the '200' status in the GET operation at the path /v2/customers/{customerId}.
• A default value of '10000' has been added for the query request parameter limit in the GET operation at the path /v2/domains.
• A new optional request parameter skip has been added in the GET operation at the path /v2/domains.
• The intended functionality of parameters page and limit of the GET operation at the path /v2/domains has been fixed, it previously did not work.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "List Ingresses compatible with a certificate"​

• changed the request body to a 'oneOf' list

• moved the previous alternative-less request body into '#/components/schemas/de.mittwald.v1.ingress.ListIngressesCompatibleWithCertificateRequest'

• added the alternative '#/components/schemas/de.mittwald.v1.ingress.ListIngressesCompatibleWithCertificateIDRequest'

For details, refer to the POST/v2/actions/list-ingresses-compatible-with-certificate/ endpoint.

Changes in "Create a CertificateRequest"​

• the response property 'contact' became optional for the status '201', since the new certificate requests of type '3' (DNS), do not have a contact

• added '#/components/schemas/de.mittwald.v1.ssl.CertificateRequestCreateWithDNSRequest' to the request body 'oneOf' list

• added the non-success response with the status '409'

• added the non-success response with the status '412'

For details, refer to the POST/v2/certificate-requests/ endpoint.

Changes in component "Certificate"​

• added the optional property 'dnsCertSpec'

• added the new '3' (DNS) enum value to the 'certificateType' property.

• such DNS certificates do not contain previously required properties, which therefore became optional:

  • 'certificate'
  • 'isExpired'
  • 'lastExpirationThresholdHit'
  • 'validFrom'
  • 'validTo'

For details, refer to the GET/v2/certificates/{certificateId}/ endpoint.

Changes in "List Domains"​

• for the 'query' request parameter 'limit', default value '10000' was added

• added the new optional 'query' request parameter 'skip'

• the intended functionality of parameters page and limit has been fixed, it previously did not work.

For details, refer to the GET/v2/domains/ endpoint.

Changes in "List customer invites belonging to the executing user"​

• removed the optional property '/items/information/userId' from the response with the '200' status

For details, refer to the GET/v2/customer-invites/ endpoint.

Changes in "Get a customer invite"​

• removed the optional property 'information/userId' from the response with the '200' status

For details, refer to the GET/v2/customer-invites/{customerInviteId}/ endpoint.

Changes in "Get a customer invite by token"​

• removed the optional property 'information/userId' from the response with the '200' status

For details, refer to the GET/v2/customer-token-invite/ endpoint.

Changes in "List Invites belonging to a Customer"​

• removed the optional property '/items/information/userId' from the response with the '200' status

For details, refer to the GET/v2/customers/{customerId}/invites/ endpoint.

Changes in "Create a customer invite"​

• removed the optional property 'information/userId' from the response with the '201' status

For details, refer to the POST/v2/customers/{customerId}/invites/ endpoint.

Changes in "List ProjectInvites belonging to the executing user"​

• removed the optional property '/items/information/userId' from the response with the '200' status

For details, refer to the GET/v2/project-invites/ endpoint.

Changes in "Get a ProjectInvite"​

• removed the optional property 'information/userId' from the response with the '200' status

For details, refer to the GET/v2/project-invites/{projectInviteId}/ endpoint.

Changes in "Get a ProjectInvite by token"​

• removed the optional property 'information/userId' from the response with the '200' status

For details, refer to the GET/v2/project-token-invite/ endpoint.

Changes in "List Invites belonging to a Project"​

• removed the optional property '/items/information/userId' from the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/invites/ endpoint.

Changes in "Create a ProjectInvite"​

• removed the optional property 'information/userId' from the response with the '201' status

For details, refer to the POST/v2/projects/{projectId}/invites/ endpoint.

Changes in "Get all customer profiles the authenticated user has access to"​

• added the optional property '/items/isMailAddressInvalid' to the response with the '200' status

For details, refer to the GET/v2/customers/ endpoint.

Changes in "Get a customer profile"​

• added the optional property 'isMailAddressInvalid' to the response with the '200' status

For details, refer to the GET/v2/customers/{customerId}/ endpoint.

Client package releases​

mittwald PHP SDK v2.1.180 Release Summary​

The latest release of the mittwald PHP SDK, version v2.1.180, introduces several enhancements and new features focused on improving SSL certificate management and API interaction. Key updates include:

• Features:

  • Support for conflict and precondition failed responses in SSL certificate creation requests.
  • New request schemas for listing ingresses compatible with certificates.
  • Enhanced SSL certificate schema with new DNS certificate specifications and detailed statuses.

• Additions:

  • New response classes: SslCreateCertificateRequestConflictResponse and SslCreateCertificateRequestPreconditionFailedResponse.
  • New schemas: ListIngressesCompatibleWithCertificateIDRequest, CertificateRequestCreateWithDNSRequest, DNSCertStatus, and ProjectCertificateStatus.
  • Updates to existing classes to support new request types and enhance flexibility in SSL certificate requests.

• Changes:

  • Refactoring of existing classes for improved clarity and structure.
  • Nullable class properties for compatibility with optional parameters.
  • Adjusted validation schemas to prevent invalid attributes in requests.

These updates aim to enhance error handling and expand capabilities in defining requests and responses related to SSL certificates.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.179​

The mittwald PHP SDK has been updated to version v2.1.179. This release includes several enhancements and bug fixes aimed at improving functionality and code clarity.

Features​

• MySQL Database Retrieval Enhancement: The getMySQLDatabase function in DatabaseClient and DatabaseClientImpl now includes detailed comments. These comments clarify that the method returns a MySQLDatabase resource along with its current status, and emphasize that the linked user must have a status of "ready" for a successful connection.

Bug Fixes and Improvements​

• Customer Invite Schema Adjustment: The description for the avatarRefId field in the CustomerInvite class has been updated for clarity, changing from "Reference to the Project's avatar" to "Reference to the Customer's avatar."
• Invite Information Schema Simplification: The userId field, along with its associated methods and validations, has been removed from the InviteInformation class to streamline the invite process and enhance the data model.
• Code Cleanup: Deprecated properties and methods related to userId in the InviteInformation class have been removed to ensure cleaner and more maintainable code.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.178​

The mittwald PHP SDK has been updated to version v2.1.178. This release introduces several enhancements and changes aimed at improving functionality and user experience.

Features​

• ListDomainsRequest Enhancements: The ListDomainsRequest class now supports enhanced pagination and filtering with the addition of a skip property and a default limit set to 10,000. The handling of domain search and contact hash has been restructured for better efficiency.

• Customer Schema Updates: A new boolean property, isMailAddressInvalid, has been added to the Customer class to track the validity of a customer's email address.

Changes​

• ListDomainsRequest Class: The structure of the ListDomainsRequest has been refactored, introducing a skip property for improved pagination control and removing default handling for page and limit to allow for more user-defined flexibility.

• UserClient Interface and Implementation: Documentation updates include a revised description for the method of creating an API token, changing from "Store a new ApiToken." to "Create a new ApiToken."

• Customer Class: The isMailAddressInvalid property has been integrated with corresponding getter and setter methods, and the constructor and methods have been updated to include validation logic for this new property.

For more details, please visit the release page.

mittwald JavaScript SDK Release 4.296.0​

The mittwald JavaScript SDK version 4.296.0 has been released on February 5, 2026. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub.

mittwald JavaScript SDK Release 4.295.0​

The mittwald JavaScript SDK has been updated to version 4.295.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.

mittwald JavaScript SDK Release 4.294.0​

The mittwald JavaScript SDK has been updated to version 4.294.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.294.0.

mittwald JavaScript SDK Release 4.293.0​

The mittwald JavaScript SDK has been updated to version 4.293.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.293.0.

mittwald JavaScript SDK Release 4.292.0​

The mittwald JavaScript SDK has been updated to version 4.292.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.

mittwald JavaScript SDK Release 4.291.0​

The mittwald JavaScript SDK has been updated to version 4.291.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.291.0.

Summary​

• The schema 'de.mittwald.v1.backup.RestorePathPhase' has been removed from the API components.
• The API operation ID 'cronjob-update-cronjob-app-id' has been removed and replaced with 'cronjob-update-cronjob-app-id-deprecated' for the PATCH operation at the path /v2/cronjobs/{cronjobId}/app-installation-id.
• A new endpoint has been added to update a Cronjob's app installation ID with the PUT operation at the path /v2/cronjobs/{cronjobId}/app-installation-id.
• A new endpoint has been added to check if an Extension is unchargable for a specific context with the GET operation at the path /v2/extensions/{extensionId}/contexts/{contextId}/chargability.
• The optional property 'restore' has been added to the response with the '200' status for the GET operation at the path /v2/project-backups/{projectBackupId}.
• A new endpoint has been added to list database dumps for a ProjectBackup with the GET operation at the path /v2/project-backups/{projectBackupId}/database-dumps.
• A new endpoint has been added to restore a ProjectBackup with the POST operation at the path /v2/project-backups/{projectBackupId}/restore.
• The API operation ID 'backup-request-project-backup-restore-path' has been removed and replaced with 'backup-request-project-backup-restore-path-deprecated' for the POST operation at the path /v2/project-backups/{projectBackupId}/restore-path.
• A new optional request parameter 'runningRestoresOnly' has been added to the GET operation for listing backups belonging to a Project at the path /v2/projects/{projectId}/backups.
• The optional property '/items/restore' has been added to the response with the '200' status for the GET operation at the path /v2/projects/{projectId}/backups.
• The optional property 'restore' has been added to the response with the '201' status for the POST operation at the path /v2/projects/{projectId}/backups.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in ""​

• removed the schema 'de.mittwald.v1.backup.RestorePathPhase'

For details, refer to the unknown operation endpoint.

Changes in "cronjob-update-cronjob-app-id"​

• api operation id 'cronjob-update-cronjob-app-id' removed and replaced with 'cronjob-update-cronjob-app-id-deprecated'

For details, refer to the unknown operation cronjob-update-cronjob-app-id endpoint.

Changes in "Update a cronjob's app installation id"​

• endpoint added

For details, refer to the PUT/v2/cronjobs/{cronjobId}/app-installation-id/ endpoint.

Changes in "Check if an Extension is unchargable for this specific context or if it must be charged"​

• endpoint added

For details, refer to the GET/v2/extensions/{extensionId}/contexts/{contextId}/chargability/ endpoint.

Changes in "Get a project backup"​

• added the optional property 'restore' to the response with the '200' status

For details, refer to the GET/v2/project-backups/{projectBackupId}/ endpoint.

Changes in "List database dump's for a project backup"​

• endpoint added

For details, refer to the GET/v2/project-backups/{projectBackupId}/database-dumps/ endpoint.

Changes in "Restore a project backup"​

• endpoint added

For details, refer to the POST/v2/project-backups/{projectBackupId}/restore/ endpoint.

Changes in "backup-request-project-backup-restore-path"​

• api operation id 'backup-request-project-backup-restore-path' removed and replaced with 'backup-request-project-backup-restore-path-deprecated'

For details, refer to the unknown operation backup-request-project-backup-restore-path endpoint.

Changes in "List Backups belonging to a Project"​

• added the new optional 'query' request parameter 'runningRestoresOnly'

• added the optional property '/items/restore' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/backups/ endpoint.

Changes in "Create a Backup of a Project"​

• added the optional property 'restore' to the response with the '201' status

For details, refer to the POST/v2/projects/{projectId}/backups/ endpoint.

Client package releases​

Release Summary: mittwald PHP SDK v2.1.177​

The mittwald PHP SDK has been updated to version 2.1.177. This release introduces several new features and improvements:

• Features:

  • Added functionality to list database dumps for a Project Backup.
  • Introduced a new API endpoint for restoring a Project Backup.
  • Deprecated the old restore path request in favor of a new structure.

• Changes:

  • New Endpoints:
    • getProjectBackupDatabaseDumpsV2Experimental: Lists database dumps associated with a specific Project Backup.
  • Renamed and Deprecated Endpoints:
    • requestProjectBackupRestorePath is deprecated in favor of requestProjectBackupRestoreV2Experimental.
  • New Data Structures:
    • ProjectBackupRestore and ProjectBackupRestorePath have been enhanced for better functionality.
  • Architecture Changes:
    • Added new response handling classes for error management.
    • Refactored validation schemas for improved error handling and data integrity.

• Miscellaneous:

  • Enhanced validation and error handling across APIs.
  • Added documentation links and examples for clarity.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.176​

The latest release of the mittwald PHP SDK, version v2.1.176, introduces several enhancements and new features to the Cronjob and Marketplace APIs.

Features​

• Cronjob API Updates: A new method, replaceCronjobAppInstallationId, has been added to enhance the Cronjob API by allowing the replacement of a Cronjob's app installation ID. This update includes improved request validation and handling.

• Marketplace API Enhancements: New functionality has been introduced to check if an extension is chargeable for specific contexts. This includes two new types of responses to manage success and error scenarios effectively.

Changes​

• Cronjob API Enhancements:

  • The replaceCronjobAppInstallationId method has been added to the CronjobClient interface.
  • The updateCronjobAppId method is now deprecated in favor of the new method.

• Marketplace API Enhancements:

  • A new method, extensionCheckExtensionIsChargable, has been added to the MarketplaceClient interface.
  • New response classes have been introduced to handle default, not found, and too many requests scenarios.

• Response Handling: Enhanced handling for new response classes to manage various states and errors in both Cronjob and Marketplace APIs.

• Request and Response Models: New classes have been added in the ExtensionCheckExtensionIsChargable namespace to support the new functionalities.

• Validation Improvements: Improved validation schemas ensure more robust and reliable API input handling.

These updates enhance the SDK's capabilities, providing more versatile interactions with Cronjobs and Marketplace extensions.

mittwald JavaScript SDK Release 4.290.0​

The mittwald JavaScript SDK has been updated to version 4.290.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.290.0.

mittwald JavaScript SDK Release 4.289.0​

The mittwald JavaScript SDK version 4.289.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.

mittwald JavaScript SDK Release 4.288.0​

The mittwald JavaScript SDK has been updated to version 4.288.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.

Summary​

• The API path /v2/cronjobs/{cronjobId}/app-id has been deprecated by /v2/cronjobs/{cronjobId}/app-installation-id for the PATCH operation cronjob-update-cronjob-app-id.
• An endpoint has been added at /v2/cronjobs/{cronjobId}/app-installation-id for the PATCH operation cronjob-update-cronjob-app-id.
• The optional property appInstallationId has been added to the response with the 200 status for the GET operation cronjob-get-cronjob.
• The optional property expirationDate has been added to the response with the 201 status for the POST operation domain-create-domain-auth-code.
• The optional property /items/appInstallationId has been added to the response with the 200 status for the GET operation cronjob-list-cronjobs.
• A new optional request property appInstallationId has been added for the POST operation cronjob-create-cronjob.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Update a cronjob's app installation id"​

• endpoint deprecated

• endpoint added

For details, refer to the unknown operation cronjob-update-cronjob-app-id endpoint.

Changes in "Get a cronjob"​

• added the optional property 'appInstallationId' to the response with the '200' status

For details, refer to the GET/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "Create an auth code for a Domains transfer-out process"​

• added the optional property 'expirationDate' to the response with the '201' status

For details, refer to the POST/v2/domains/{domainId}/actions/auth-code/ endpoint.

Changes in "List cronjobs belonging to a Project"​

• added the optional property '/items/appInstallationId' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/cronjobs/ endpoint.

Changes in "Create a cronjob"​

• added the new optional request property 'appInstallationId'

For details, refer to the POST/v2/projects/{projectId}/cronjobs/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.175​

The mittwald PHP SDK has released version v2.1.175, which introduces significant updates and deprecations.

Deprecation Notice​

• The appId field is now deprecated and will be replaced by appInstallationId. Future versions will remove appId entirely.

Key Changes​

API Updates:

• Documentation and schemas have been updated to reflect the transition from appId to appInstallationId.

Code Modifications:

• Fields related to appId in classes such as UpdateCronjobAppIdRequest, Cronjob, and CronjobRequest are marked as deprecated.
• New field appInstallationId has been introduced in these classes.
• New methods have been added to handle appInstallationId, while methods related to appId are deprecated.

Validation Schema Updates:

• Validation schemas now include appInstallationId and mark appId as deprecated, with clarifications provided.

This release aims to enhance the API's clarity and facilitate a smoother transition for developers. For more details, visit the release page.

mittwald PHP SDK Release v2.1.174​

The latest release of the mittwald PHP SDK, v2.1.174, introduces a significant enhancement to the Create Domain Authentication Code endpoint. This update adds an expiration date to the response data, providing users with critical information about the validity period of the authentication code.

Key Updates:​

• Expiration Date for Auth Code:
  • The CreateDomainAuthCodeCreatedResponse now includes an expirationDate field formatted as a date-time string.
  • The response body class has been updated to incorporate methods for setting and retrieving the expiration date.

Enhancements:​

• The structure of response objects has been updated to include the new expirationDate attribute.
• New methods withExpirationDate and withoutExpirationDate have been added to the CreateDomainAuthCodeCreatedResponseBody class for improved management of the expiration date field.

For more details, visit the release page.

mittwald JavaScript SDK Release 4.287.0​

The mittwald JavaScript SDK has been updated to version 4.287.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 Release 4.286.0​

The mittwald JavaScript SDK has been updated to version 4.286.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 SDK 4.286.0.

mittwald JavaScript SDK Release 4.285.0​

The mittwald JavaScript SDK has been updated to version 4.285.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.285.0.

Summary​

• The following experimental API paths have been replaced by stable ai-hosting endpoints, resulting in breaking changes:

  • GET /v2/llm-models (Operation ID: misc-get-llm-models-experimental)
  • GET /v2/projects/{projectId}/llm-licences (Operation ID: project-get-llm-licences-experimental)
  • POST /v2/projects/{projectId}/llm-licences (Operation ID: project-create-llm-beta-licence-experimental)
  • GET /v2/projects/{projectId}/llm-licences/{licenceId} (Operation ID: project-get-llm-licence-experimental)
  • PUT /v2/projects/{projectId}/llm-licences/{licenceId} (Operation ID: project-update-llm-licence-experimental)

• A new endpoint has been added to retrieve a list of currently active models:

  • GET /v2/ai-hosting-models (Operation ID: ai-hosting-get-models)

• New endpoints have been added for AI hosting customer management:

  • GET /v2/customers/{customerId}/ai-hosting (Operation ID: ai-hosting-customer-get-usage)
  • GET /v2/customers/{customerId}/ai-hosting-keys (Operation ID: ai-hosting-customer-get-keys)
  • POST /v2/customers/{customerId}/ai-hosting-keys (Operation ID: ai-hosting-customer-create-key)
  • DELETE /v2/customers/{customerId}/ai-hosting-keys/{keyId} (Operation ID: ai-hosting-customer-delete-key)
  • GET /v2/customers/{customerId}/ai-hosting-keys/{keyId} (Operation ID: ai-hosting-customer-get-key)
  • PUT /v2/customers/{customerId}/ai-hosting-keys/{keyId} (Operation ID: ai-hosting-customer-update-key)

• New endpoints have been added for AI hosting project management:

  • GET /v2/projects/{projectId}/ai-hosting (Operation ID: ai-hosting-project-get-usage)
  • GET /v2/projects/{projectId}/ai-hosting-keys (Operation ID: ai-hosting-project-get-keys)
  • POST /v2/projects/{projectId}/ai-hosting-keys (Operation ID: ai-hosting-project-create-key)
  • DELETE /v2/projects/{projectId}/ai-hosting-keys/{keyId} (Operation ID: ai-hosting-project-delete-key)
  • GET /v2/projects/{projectId}/ai-hosting-keys/{keyId} (Operation ID: ai-hosting-project-get-key)
  • PUT /v2/projects/{projectId}/ai-hosting-keys/{keyId} (Operation ID: ai-hosting-project-update-key)

• Order endpoints have been adjust for AI hosting:

  • The POST /v2/order-previews operation has received several updates:

    • Added the new aiHosting enum value to the orderType request property.
    • Added #/components/schemas/de.mittwald.v1.order.AIHostingOrderPreview to the orderData request property oneOf list.
    • Added #/components/schemas/de.mittwald.v1.order.AIHostingOrderPreviewResponse to the response body anyOf list for the response status 200.

  • The POST /v2/orders operation has received similar updates:

    • Added the new aiHosting enum value to the orderType request property.
    • Added #/components/schemas/de.mittwald.v1.order.AIHostingOrder to the orderData request property oneOf list.

  • The POST /v2/tariff-change-previews operation has received updates:

    • Added the new aiHosting enum value to the tariffChangeType request property.
    • Added #/components/schemas/de.mittwald.v1.order.AIHostingTariffChange to the tariffChangeData request property oneOf list.

  • The POST /v2/tariff-changes operation has similar updates:

    • Added the new aiHosting enum value to the tariffChangeType request property.
    • Added #/components/schemas/de.mittwald.v1.order.AIHostingTariffChange to the tariffChangeData request property oneOf list.

• The GET /v2/conversations operation has new optional request parameters:

  • fullTextSearch
  • limit
  • page
  • skip
  • status

• The POST /v2/projects/{projectId}/straces operation has a new non-success response with the status 412.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Experimental endpoints misc-llm-* and project-llm-* removed​

The following experimental endpoints and schemas were replaced by stable parts:

• api endpoint "misc-get-llm-models-experimental"
• api endpoint "project-get-llm-licences-experimental"
• api endpoint "project-create-llm-beta-licence-experimental"
• api endpoint "project-get-llm-licence-experimental"
• api endpoint "project-update-llm-licence-experimental"
• schema "de.mittwald.v1.aihosting.Licence"

Refer to (New AI-Hosting API)[#new-ai-hosting-api] for details

New AI hosting API​

General routes​

Endpoints added:

• GET/v2/ai-hosting-models/

AI hosting customer endpoints​

Endpoints added:

• GET/v2/customers/{customerId}/ai-hosting/
• GET/v2/customers/{customerId}/ai-hosting-keys/
• POST/v2/customers/{customerId}/ai-hosting-keys/
• DELETE/v2/customers/{customerId}/ai-hosting-keys/{keyId}/
• GET/v2/customers/{customerId}/ai-hosting-keys/{keyId}/
• PUT/v2/customers/{customerId}/ai-hosting-keys/{keyId}/

AI hosting project endpoints​

Endpoints added:

• GET/v2/projects/{projectId}/ai-hosting/
• GET/v2/projects/{projectId}/ai-hosting-keys/
• POST/v2/projects/{projectId}/ai-hosting-keys/
• DELETE/v2/projects/{projectId}/ai-hosting-keys/{keyId}/
• GET/v2/projects/{projectId}/ai-hosting-keys/{keyId}/
• PUT/v2/projects/{projectId}/ai-hosting-keys/{keyId}/

AI hosting orders​

Changes in "Preview Order"​

• added the new 'aiHosting' enum value to the request property 'orderType'

• added '#/components/schemas/de.mittwald.v1.order.AIHostingOrderPreview' to the 'orderData' request property 'oneOf' list

• added '#/components/schemas/de.mittwald.v1.order.AIHostingOrderPreviewResponse' to the response body 'anyOf' list for the response status '200'

For details, refer to the POST/v2/order-previews/ endpoint.

Changes in "Create an Order"​

• added the new 'aiHosting' enum value to the request property 'orderType'

• added '#/components/schemas/de.mittwald.v1.order.AIHostingOrder' to the 'orderData' request property 'oneOf' list

For details, refer to the POST/v2/orders/ endpoint.

Changes in "Preview TariffChange"​

• added the new 'aiHosting' enum value to the request property 'tariffChangeType'

• added '#/components/schemas/de.mittwald.v1.order.AIHostingTariffChange' to the 'tariffChangeData' request property 'oneOf' list

For details, refer to the POST/v2/tariff-change-previews/ endpoint.

Changes in "Create TariffChange Order"​

• added the new 'aiHosting' enum value to the request property 'tariffChangeType'

• added '#/components/schemas/de.mittwald.v1.order.AIHostingTariffChange' to the 'tariffChangeData' request property 'oneOf' list

For details, refer to the POST/v2/tariff-changes/ endpoint.

Changes in "Get all conversation the authenticated user has created or has access to"​

• added the new optional 'query' request parameter 'fullTextSearch'

• added the new optional 'query' request parameter 'limit'

• added the new optional 'query' request parameter 'page'

• added the new optional 'query' request parameter 'skip'

• added the new optional 'query' request parameter 'status'

For details, refer to the GET/v2/conversations/ endpoint.

Changes in "Schedule a strace measurement for a single http request"​

• added the non-success response with the status '412'

For details, refer to the POST/v2/projects/{projectId}/straces/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.173​

The mittwald PHP SDK has been updated to version v2.1.173. This release includes a change in the method naming conventions within the Client interface and its implementation. Specifically, the method aIHosting has been renamed to aiHosting to enhance consistency and clarity in the codebase.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.172​

The latest release of the mittwald PHP SDK, version v2.1.172, introduces several new features and improvements:

Features​

• A new AIHostingClient interface and its implementation have been added to manage AI hosting API functionalities. This includes managing customer and project keys, retrieving usage, and accessing models.
• Methods for creating, deleting, and updating keys for customers and projects have been introduced, along with error handling for various error responses.
• Enhanced handling of requests and responses related to customer usage and project creation, improving interaction with the AI hosting service.

Breaking Changes​

• The naming convention for imported classes has been standardized from AIhosting to AIHosting, affecting both interface definitions and client implementation files.
• Method names within the Client interface have been updated to match the new naming convention, changing aIhosting() to aIHosting().

New Classes​

• AIHostingClient: Interface for AI hosting operations.
• AIHostingClientImpl: Implementation of the AIHostingClient interface.
• New response classes for key operations, such as CustomerCreateKeyCreatedResponse, CustomerDeleteKeyBadRequestResponse, and others.

Changes to Existing Functionality​

• Existing request and response classes have been renamed and refactored within the CustomerGetKeys, CustomerGetUsage, and ProjectCreateKey namespaces to align with the new naming scheme, ensuring clearer semantics and consistency.

This release enhances the API client's structure and usability for developers working with AI hosting features, while maintaining backward compatibility where possible.

mittwald PHP SDK Release v2.1.171​

The latest release of the mittwald PHP SDK, version v2.1.171, introduces several updates and improvements:

Added Features​

• AI Hosting Terminology Updates: The term "tariff" has been replaced with "plan" throughout the codebase to align with industry standards.

Changes​

• AI Hosting Client Updates: Method comments in AIhostingClient.php and AIhostingClientImpl.php have been updated to reflect the terminology change from "tariff" to "plan" for functions like aiHostingCustomerGetUsage and aiHostingProjectGetUsage.

• Response Class Adjustments: The response classes AiHostingCustomerGetUsageOKResponse.php and AiHostingProjectGetUsageOKResponse.php now use PlanOptions and PlanUsage instead of TariffOptions and TariffUsage.

• New Properties and Methods in ListConversationsRequest: New properties have been introduced to support full text search, filtering by conversation status, and pagination controls. Corresponding getter and setter methods have been added.

• Schema Renaming and Updates: Related schema files have been renamed for consistency, and a planLimit parameter has been added to the PlanUsage and PlanUsageBig classes, with a deprecation notice for tariffLimit.

These updates enhance clarity and improve functionality in managing AI hosting plans.

mittwald PHP SDK v2.1.170 Release​

The mittwald PHP SDK has been updated to version v2.1.170. This release introduces significant enhancements, particularly in the management of AI hosting services. The new features include a dedicated client for handling AI hosting keys, allowing operations such as creating, retrieving, updating, and deleting keys. This addition enhances the API's capability to manage customer-specific keys for AI hosting.

New Features​

• AI Hosting Client:

  • Implemented AIhostingClient and AIhostingClientImpl for managing AI hosting keys.

• AI Hosting Customer Keys:

  • Introduced several request and response classes for key management, including:
    • AiHostingCustomerCreateKeyRequest
    • AiHostingCustomerCreateKeyCreatedResponse
    • AiHostingCustomerDeleteKeyRequest
    • AiHostingCustomerGetKeyRequest
    • AiHostingCustomerGetKeysRequest
    • AiHostingCustomerGetUsageRequest
  • Enhanced error handling for operations with responses for BadRequest, NotFound, Forbidden, and TooManyRequests.

Updated Interfaces​

• The Client interface now includes the aIhosting() method to access AI hosting functionalities.

Detailed Changes​

• New files added for AI hosting client and customer key management.
• The ClientImpl has been updated to incorporate the new AI hosting methods.
• Improved error handling for AI hosting operations.

For more details, please visit the release page.

mittwald PHP SDK Release v2.1.169​

The latest release of the mittwald PHP SDK, version 2.1.169, introduces new features and changes aimed at improving error handling and response management.

New Features​

• Precondition Failed Response Handling: A new response class, PageinsightsScheduleStracePreconditionFailedResponse, has been added to handle HTTP 412 status codes specifically for the Page Insights API. This enhancement allows for better management of client-side conditions that fail during requests.

Changes​

• Added Precondition Failed Response: The PageInsightsClientImpl class now includes handling for the 412 HTTP status code, utilizing the new PageinsightsScheduleStracePreconditionFailedResponse for more detailed error context.

For more details, visit the release page.

mittwald JavaScript SDK Release 4.284.0​

The mittwald JavaScript SDK version 4.284.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.

mittwald JavaScript SDK Release 4.283.0​

The mittwald JavaScript SDK version 4.283.0 has been released on January 15, 2026. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.283.0.

mittwald JavaScript SDK Release 4.282.0​

The mittwald JavaScript SDK has been updated to version 4.282.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.

mittwald JavaScript SDK Release 4.281.0​

The mittwald JavaScript SDK has been updated to version 4.281.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub here.

mittwald JavaScript SDK Release 4.280.0​

The mittwald JavaScript SDK has been updated to version 4.280.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub here.

Summary​

• The enum value 'readonly' has been removed from the request property 'user/accessLevel' for both the POST operations: database-copy-mysql-database and database-create-mysql-database. This is a breaking change.
• The GET operation cronjob-get-cronjob has had several optional properties added to its response with a '200' status: 'concurrencyPolicy', 'latestExecution/exitCode', and 'timeZone'.
• The PATCH operation cronjob-update-cronjob now includes two new optional request properties: 'concurrencyPolicy' and 'timeZone'.
• The GET operation cronjob-list-executions has had the optional property '/items/exitCode' added to its response with a '200' status.
• The GET operation cronjob-get-execution has had the optional property 'exitCode' added to its response with a '200' status.
• The POST operation cronjob-abort-execution has been removed and replaced with the deprecated operation id 'deprecated-cronjob-abort-execution'.
• The GET operation cronjob-list-cronjobs has had several optional properties added to its response with a '200' status: '/items/concurrencyPolicy', '/items/latestExecution/exitCode', and '/items/timeZone'.
• The POST operation cronjob-create-cronjob now includes two new optional request properties: 'concurrencyPolicy' and 'timeZone'.
• A new endpoint has been added for the GET operation miscellaneous-list-time-zones at the path '/v2/time-zones', which lists valid time zones.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Copy a MySQL database with a MySQL user"​

• ⚠️ Breaking: removed the enum value 'readonly' of the request property 'user/accessLevel'

For details, refer to the POST/v2/mysql-databases/{mysqlDatabaseId}/actions/copy/ endpoint.

Changes in "Create a MySQL database with a MySQL user"​

• ⚠️ Breaking: removed the enum value 'readonly' of the request property 'user/accessLevel'

For details, refer to the POST/v2/projects/{projectId}/mysql-databases/ endpoint.

Changes in "Get a cronjob"​

• added the optional property 'concurrencyPolicy' to the response with the '200' status

• added the optional property 'latestExecution/exitCode' to the response with the '200' status

• added the optional property 'timeZone' to the response with the '200' status

For details, refer to the GET/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "Update a cronjob"​

• added the new optional request property 'concurrencyPolicy'

• added the new optional request property 'timeZone'

For details, refer to the PATCH/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "List cronjob executions belonging to a cronjob"​

• added the optional property '/items/exitCode' to the response with the '200' status

For details, refer to the GET/v2/cronjobs/{cronjobId}/executions/ endpoint.

Changes in "Get a cronjob execution"​

• added the optional property 'exitCode' to the response with the '200' status

For details, refer to the GET/v2/cronjobs/{cronjobId}/executions/{executionId}/ endpoint.

Changes in "cronjob-abort-execution"​

• api operation id 'cronjob-abort-execution' removed and replaced with 'deprecated-cronjob-abort-execution'

For details, refer to the unknown operation cronjob-abort-execution endpoint.

Changes in "List cronjobs belonging to a Project"​

• added the optional property '/items/concurrencyPolicy' to the response with the '200' status

• added the optional property '/items/latestExecution/exitCode' to the response with the '200' status

• added the optional property '/items/timeZone' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/cronjobs/ endpoint.

Changes in "Create a cronjob"​

• added the new optional request property 'concurrencyPolicy'

• added the new optional request property 'timeZone'

For details, refer to the POST/v2/projects/{projectId}/cronjobs/ endpoint.

Changes in "List valid time zones"​

• endpoint added

For details, refer to the GET/v2/time-zones/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.168​

The latest release of the mittwald PHP SDK, v2.1.168, introduces several new features and improvements:

New Features​

• Time Zone Support: An endpoint to list valid time zones has been added, enhancing scheduling capabilities. Time zone and concurrency policy parameters are now available in cron job creation and update methods.
• Concurrency Policy Enhancements: A ConcurrencyPolicy enum has been introduced to manage concurrent executions of cron jobs, with updates to cron job schemas to include these settings.

Deprecated Features​

• The abortExecution method for cron jobs is deprecated and replaced with deprecatedCronjobAbortExecution, maintaining compatibility with previous calls.

API Client Changes​

• CronjobClient Modifications: The abortExecution method has been removed, and the CronjobClientImpl has been updated accordingly.
• MiscellaneousClient Modifications: A new method, miscellaneousListTimeZones, has been added to list time zones, with adjustments to response handling.

Structural Changes​

• New request and response classes have been added for managing time zone-related operations.
• Existing schemas for cron jobs have been updated to include new properties for concurrency policies and time zones.
• Redundant code related to the deprecated abort execution functionality has been removed, streamlining the project.

This release enhances cron job management by supporting time zones and task execution policies while organizing deprecated features to minimize disruption.

mittwald JavaScript SDK Release 4.279.0​

The mittwald JavaScript SDK has been updated to version 4.279.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.

Summary​

• The GET /v2/contributors/{contributorId}/extensions operation now includes a required property isDeletionScheduled and an optional property deletionDeadline in the response with a 200 status.
• The GET /v2/contributors/{contributorId}/extensions/{extensionId} operation has been updated to include a required property isDeletionScheduled and an optional property deletionDeadline in the response with a 200 status.
• The PATCH /v2/contributors/{contributorId}/extensions/{extensionId} operation now includes a required property isDeletionScheduled and an optional property deletionDeadline in the response with a 200 status.
• The PUT /v2/contributors/{contributorId}/extensions/{extensionId}/pricing operation has been updated to include two new optional request properties: deletionDeadline and isDeletionScheduled, as well as an optional response property deletionDeadline.
• The GET /v2/contributors/{contributorId}/invoices/incoming operation now includes an optional property invoiceType in the response with a 200 status.
• A new endpoint GET /v2/customers/{customerId}/ai-hosting/contract has been added to return the AI Hosting Contract for the given Customer.
• The GET /v2/domain-suggestions operation has had the endpoint scheme security de.mittwald.v1.commons.AccessToken removed.
• The POST /v2/domains/{domainId}/scheduled-deletion operation now includes a new optional request property deleteIngresses.
• The GET /v2/extensions operation has been updated to include a required property isDeletionScheduled and an optional property deletionDeadline in the response with a 200 status.
• The GET /v2/extensions/{extensionId} operation now includes two required properties: isDeletionScheduled and an optional property deletionDeadline in the response with a 200 status.
• The GET /v2/projects/{projectId}/jwt operation has had a non-success response with the status 401 added.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "List Extensions of own contributor"​

• added the optional property '/items/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/deletionDeadline' to the response with the '200' status

• added the required property '/items/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/isDeletionScheduled' to the response with the '200' status

For details, refer to the GET/v2/contributors/{contributorId}/extensions/ endpoint.

Changes in "Get Extension of own contributor"​

• added the optional property 'pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/deletionDeadline' to the response with the '200' status

• added the required property 'pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/isDeletionScheduled' to the response with the '200' status

For details, refer to the GET/v2/contributors/{contributorId}/extensions/{extensionId}/ endpoint.

Changes in "Patch Extension"​

• added the optional property 'pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/deletionDeadline' to the response with the '200' status

• added the required property 'pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/isDeletionScheduled' to the response with the '200' status

For details, refer to the PATCH/v2/contributors/{contributorId}/extensions/{extensionId}/ endpoint.

Changes in "Creates or Updates Pricing for an Extension"​

• added the new optional request property '/oneOf[subschema #2]/pricePlan/variants/items/deletionDeadline'

• added the new optional request property '/oneOf[subschema #2]/pricePlan/variants/items/isDeletionScheduled'

• added the optional property 'priceChangeConsequence/variantConsequences/items/deletionDeadline' to the response with the '200' status

For details, refer to the PUT/v2/contributors/{contributorId}/extensions/{extensionId}/pricing/ endpoint.

Changes in "List incoming Invoices of a contributor"​

• added the optional property '/items/invoiceType' to the response with the '200' status

For details, refer to the GET/v2/contributors/{contributorId}/invoices/incoming/ endpoint.

Changes in "Return the AI Hosting Contract for the given Customer"​

• endpoint added

For details, refer to the GET/v2/customers/{customerId}/ai-hosting/contract/ endpoint.

Changes in "Suggest a list of domains based on a prompt using AI"​

• the endpoint scheme security 'de.mittwald.v1.commons.AccessToken' was removed from the API

For details, refer to the GET/v2/domain-suggestions/ endpoint.

Changes in "Create a scheduled deletion of a Domain"​

• added the new optional request property 'deleteIngresses'

For details, refer to the POST/v2/domains/{domainId}/scheduled-deletion/ endpoint.

Changes in "List Extensions"​

• added the optional property '/items/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/deletionDeadline' to the response with the '200' status

• added the required property '/items/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/isDeletionScheduled' to the response with the '200' status

For details, refer to the GET/v2/extensions/ endpoint.

Changes in "Get an Extension"​

• added the optional property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.Extension]/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/deletionDeadline' to the response with the '200' status

• added the optional property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.UnpublishedExtension]/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/deletionDeadline' to the response with the '200' status

• added the required property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.Extension]/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/isDeletionScheduled' to the response with the '200' status

• added the required property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.UnpublishedExtension]/pricing/oneOf[#/components/schemas/de.mittwald.v1.marketplace.MonthlyPricePlanStrategy]/items/isDeletionScheduled' to the response with the '200' status

For details, refer to the GET/v2/extensions/{extensionId}/ endpoint.

Changes in "Get a Project's file/filesystem authorization token"​

• added the non-success response with the status '401'

For details, refer to the GET/v2/projects/{projectId}/jwt/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.167​

The latest release of the mittwald PHP SDK, version 2.1.167, introduces several new features and enhancements:

Features Added​

• A new invoiceType field has been added to the ContributorListIncomingInvoicesOKResponse and ContributorListIncomingInvoicesOKResponseBodyItem classes.
• An enumeration, ContributorListIncomingInvoicesOKResponseBodyItemInvoiceType, has been introduced to define possible invoice types: REGULAR, CORRECTION, REISSUE, and CANCELLATION.

Enhancements​

• The getInvoiceType method in the ContributorListIncomingInvoicesOKResponseBodyItem class now returns the invoice type if it is set.
• New methods, withInvoiceType and withoutInvoiceType, have been added to manage the invoiceType property more effectively.
• Constructor logic has been extended to accommodate the invoiceType when creating instances of ContributorListIncomingInvoicesOKResponseBodyItem.
• The serialization process in the toJson method has been improved to include the invoiceType in the output if it is set.

For more details, visit the release page.

Release Summary: mittwald PHP SDK v2.1.166​

The mittwald PHP SDK has been updated to version 2.1.166. This release introduces several enhancements and changes, primarily focusing on the addition of a new field, deletionDeadline, across various components in the Marketplace and ProjectFileSystem clients. This feature allows users to track the scheduled deletion date for variants and items, improving lifecycle management of extension pricing and project files.

Key Features:​

• New Field: deletionDeadline added to manage and track scheduled deletion dates.
• Marketplace Extensions: Updates to several classes, including ExtensionUpdateExtensionPricingOKResponse.php and Variant.php, to incorporate the deletionDeadline and isDeletionScheduled properties.
• ProjectFileSystem: Enhanced handling of unauthorized responses with the introduction of ProjectFileSystemGetJwtUnauthorizedResponse.
• Marketplace Pricing Plans: MonthlyPricePlanStrategyItem.php now includes deletionDeadline and isDeletionScheduled for better management of pricing plans.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.165​

The latest release of the mittwald PHP SDK, version v2.1.165, introduces several new features and improvements:

Added Features​

• A new method getDetailOfContractByAiHosting has been added to the ContractClient and its implementation in ContractClientImpl. This method allows retrieval of AI Hosting Contract details for a specific customer using their customer ID.

New API Requests and Responses​

• Request Class:

  • GetDetailOfContractByAiHostingRequest: Encapsulates request parameters for retrieving AI Hosting Contracts, requiring a customerId.

• Response Classes:

  • GetDetailOfContractByAiHostingOKResponse: For successful contract detail retrieval.
  • GetDetailOfContractByAiHostingBadRequestResponse: Handles 400 Bad Request errors.
  • GetDetailOfContractByAiHostingNotFoundResponse: For 404 Not Found errors.
  • GetDetailOfContractByAiHostingTooManyRequestsResponse: Manages 429 Too Many Requests errors.
  • GetDetailOfContractByAiHostingDefaultResponse: Captures other response errors.

• Response Body Class:

  • GetDetailOfContractByAiHostingTooManyRequestsResponseBody: Models the body content for too many requests responses, including message and type fields.

Changes in Interfaces and Implementations​

• The ContractClient interface now includes the new method for AI Hosting Contracts.
• ContractClientImpl has been extended to implement the new method, handling requests and HTTP responses.
• Validation schemas have been added to ensure data integrity and manage errors effectively.

This release enhances the API client's functionality by providing a dedicated method for accessing AI Hosting Contract details, improving service interaction and error handling.

mittwald PHP SDK Release v2.1.164​

The latest release of the mittwald PHP SDK, version 2.1.164, introduces new features and enhancements focused on improving the scheduled deletion process.

New Features​

• Added support for the deleteIngresses parameter in scheduled deletion requests, allowing users to decide whether to delete corresponding Ingress and subdomain Ingresses.

Enhancements​

• Introduced the deleteIngresses property in the CreateScheduledDeletionRequestBody class to manage the deletion of Ingress objects.
• Updated JSON serialization for CreateScheduledDeletionRequestBody to include the deleteIngresses property when set.
• Added withDeleteIngresses() method for setting the deleteIngresses property with validation.
• Added withoutDeleteIngresses() method for unsetting the deleteIngresses property.
• Improved input validation in the fromJson() method to support the new deleteIngresses parameter.

For more details, visit the release page.

mittwald JavaScript SDK Release 4.278.0​

The mittwald JavaScript SDK has been updated to version 4.278.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.278.0.

mittwald JavaScript SDK Release 4.277.0​

The mittwald JavaScript SDK has been updated to version 4.277.0. This release includes a feature update where the generated client has been updated. For more details, you can view the release on GitHub.

mittwald JavaScript SDK Release 4.276.0​

The mittwald JavaScript SDK has been updated to version 4.276.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.276.0.

mittwald JavaScript SDK Release 4.275.0​

The mittwald JavaScript SDK has been updated to version 4.275.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.

mittwald JavaScript SDK Release 4.274.0​

The mittwald JavaScript SDK has been updated to version 4.274.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub.

Summary​

• The default value of '1000.00' for the 'query' request parameter 'limit' has been removed for the following operations:
  • GET /v2/app-installations (List AppInstallations that a user has access to.)
  • GET /v2/projects/{projectId}/app-installations (List AppInstallations belonging to a Project.)
  • GET /v2/system-softwares (List SystemSoftwares.)
  Note: This change is a breaking change.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "List app installations that a user has access to"​

• ⚠️ Breaking: for the 'query' request parameter 'limit', default value '1000.00' was removed

For details, refer to the GET/v2/app-installations/ endpoint.

Changes in "List app installations belonging to a Project"​

• ⚠️ Breaking: for the 'query' request parameter 'limit', default value '1000.00' was removed

For details, refer to the GET/v2/projects/{projectId}/app-installations/ endpoint.

Changes in "List system softwares"​

• ⚠️ Breaking: for the 'query' request parameter 'limit', default value '1000.00' was removed

For details, refer to the GET/v2/system-softwares/ endpoint.

Client package releases​

Release Summary: mittwald PHP SDK v2.1.163​

The latest release of the mittwald PHP SDK, version v2.1.163, introduces significant updates to request limit handling and serialization processes.

Key Changes:​

• Request Limit Handling:

  • The limit attribute in request classes such as ListAppinstallationsRequest, ListAppinstallationsForUserRequest, and ListSystemsoftwaresRequest is now optional. It has been changed from an int with a default of 1000 to a nullable int without a default value.
  • A new method, withoutLimit(), has been added to these request classes, allowing users to configure requests without a limit, thus providing greater flexibility.

• Serialization Adjustments:

  • The serialization logic has been updated to include the limit in the output only if it is set, avoiding the unnecessary inclusion of a default value.

These enhancements improve the adaptability and flexibility of the API, allowing for better management of request parameters and accommodating various use cases without imposing a rigid structure on the limit parameter.

mittwald JavaScript SDK Release 4.273.0​

The mittwald JavaScript SDK has been updated to version 4.273.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.273.0.

Summary​

• A new optional request parameter named 'deleteIngresses' has been added to the DELETE operation for the domain deletion endpoint (/v2/domains/{domainId}).
• A new endpoint has been added for the GET operation to list mail addresses (/v2/mail-addresses/).

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Delete a Domain"​

• added the new optional 'query' request parameter 'deleteIngresses'

For details, refer to the DELETE/v2/domains/{domainId}/ endpoint.

Changes in "List mail addresses"​

• endpoint added

For details, refer to the GET/v2/mail-addresses// endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.162​

The latest release of the mittwald PHP SDK, version v2.1.162, introduces several new features and updates aimed at enhancing usability and consistency across the API.

Features​

• Default Limit for Requests: The ListAppinstallationsRequest, ListAppinstallationsForUserRequest, and ListSystemsoftwaresRequest now include a default limit of 1000, improving usability by automatically applying this limit if none is specified.
• Backup Client Enhancements: New methods getProjectBackupDirectories and requestProjectBackupRestorePath have been added to the BackupClient interface, allowing for better management of project backups.
• Improved Error Handling: New response classes have been introduced to manage various error scenarios, enhancing the robustness of error handling across services like Mail and Marketplace.
• Mail API Changes: The MailClient now includes new requests and responses for listing mail addresses, offering improved access to user-specific mail functionalities.

Updates​

• API Changes: The ListMailAddressesForUserRequest now supports comprehensive query parameters, including pagination and filtering options.
• Error Response Classes: New classes have been added to handle specific error responses for mail address requests, such as bad requests and service unavailability.
• Code Refactoring: Several classes have been renamed and restructured for improved clarity, including updates to mail setting enums.

This release focuses on enhancing the developer experience by providing clearer error management, maintaining consistency in default settings, and improving the overall usability of the API. For more details, visit the release page.

mittwald JavaScript SDK Release 4.272.0​

The mittwald JavaScript SDK has been updated to version 4.272.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.

mittwald JavaScript SDK Release 4.271.0​

The mittwald JavaScript SDK has been updated to version 4.271.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub here.

Summary​

• For the GET operations app-list-appinstallations-for-user, app-list-appinstallations, and app-list-systemsoftwares, a default value of 1000.00 was added for the query request parameter limit. This is a breaking change.
• Two new optional request properties, isDowngradeAllowed and isUpgradeAllowed, were added to the PUT operation extension-update-extension-pricing at the path /v2/contributors/{contributorId}/extensions/{extensionId}/pricing.
• The GET operation extension-get-extension-instance-contract now includes two optional properties in the response with a 200 status: contractPeriodEndDate and pendingVariantChange.
• A new endpoint was added for the DELETE operation extension-cancel-extension-variant-change at the path /v2/extension-instances/{extensionInstanceId}/contract/variant-change.
• A new endpoint was added for the POST operation extension-schedule-extension-variant-change at the path /v2/extension-instances/{extensionInstanceId}/contract/variant-change.
• The GET operation extension-get-extension now includes an optional property in the response with a 200 status: pricingDetails.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "List app installations that a user has access to"​

• ⚠️ Breaking: for the 'query' request parameter 'limit', default value '1000.00' was added

For details, refer to the GET/v2/app-installations/ endpoint.

Changes in "List app installations belonging to a Project"​

• ⚠️ Breaking: for the 'query' request parameter 'limit', default value '1000.00' was added

For details, refer to the GET/v2/projects/{projectId}/app-installations/ endpoint.

Changes in "List system softwares"​

• ⚠️ Breaking: for the 'query' request parameter 'limit', default value '1000.00' was added

For details, refer to the GET/v2/system-softwares/ endpoint.

Changes in "Creates or Updates Pricing for an Extension"​

• added the new optional request property '/oneOf[subschema #2]/pricePlan/isDowngradeAllowed'

• added the new optional request property '/oneOf[subschema #2]/pricePlan/isUpgradeAllowed'

For details, refer to the PUT/v2/contributors/{contributorId}/extensions/{extensionId}/pricing/ endpoint.

Changes in "Get the Contract Strategy of an Extension Instance"​

• added the optional property '/oneOf[#/components/schemas/de.mittwald.v1.extension.SubscriptionBasedContract]/contractPeriodEndDate' to the response with the '200' status

• added the optional property '/oneOf[#/components/schemas/de.mittwald.v1.extension.SubscriptionBasedContract]/pendingVariantChange' to the response with the '200' status

For details, refer to the GET/v2/extension-instances/{extensionInstanceId}/contract/ endpoint.

Changes in "Cancel an Extension Instance Variant Change"​

• endpoint added

For details, refer to the DELETE/v2/extension-instances/{extensionInstanceId}/contract/variant-change/ endpoint.

Changes in "Schedule an Extension Instance Variant change for the next possible date"​

• endpoint added

For details, refer to the POST/v2/extension-instances/{extensionInstanceId}/contract/variant-change/ endpoint.

Changes in "Get an Extension"​

• added the optional property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.UnpublishedExtension]/pricingDetails' to the response with the '200' status

For details, refer to the GET/v2/extensions/{extensionId}/ endpoint.

Client package releases​

mittwald JavaScript SDK Release 4.270.0​

The mittwald JavaScript SDK has been updated to version 4.270.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 Release 4.269.0​

The mittwald JavaScript SDK has been updated to version 4.269.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 Release 4.268.0​

The mittwald JavaScript SDK has been updated to version 4.268.0. This release includes the following feature:

• Updated generated client (commit 1217aab)

For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.268.0.

mittwald JavaScript SDK Release 4.267.0​

The mittwald JavaScript SDK has been updated to version 4.267.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 Release 4.266.0​

The mittwald JavaScript SDK has been updated to version 4.266.0. This release includes the following feature:

• Updated the generated client to enhance functionality and performance (commit 317abf4).

For more details, you can view the full release notes on GitHub.

mittwald JavaScript SDK Release 4.265.0​

The mittwald JavaScript SDK has been updated to version 4.265.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.

mittwald JavaScript SDK Release 4.264.0​

The mittwald JavaScript SDK has been updated to version 4.264.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.

Summary​

• The maximum length of the response property recordSet/mx/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/records/items/fqdn was increased from 50 to 255 for the 200 response status in the GET /v2/dns-zones/{dnsZoneId} and GET /v2/projects/{projectId}/dns-zones operations. This is a breaking change.
• The maximum length of the response property recordSet/srv/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/records/items/fqdn was increased from 50 to 255 for the 200 response status in the GET /v2/dns-zones/{dnsZoneId} and GET /v2/projects/{projectId}/dns-zones operations. This is a breaking change.
• The minimum length of the request property /oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/fqdn was increased from 0 to 1 in the PUT /v2/dns-zones/{dnsZoneId}/record-sets/{recordSet} and PUT /v2/dns/zones/{zoneId}/recordset/cname operations. This is a breaking change.
• The maximum length of the request property /oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/fqdn was set to 255 in the PUT /v2/dns-zones/{dnsZoneId}/record-sets/{recordSet} and PUT /v2/dns/zones/{zoneId}/recordset/cname operations.
• The optional property /items/pricingDetails was added to the response with the 200 status in the GET /v2/contributors/{contributorId}/extensions and GET /v2/extensions operations.
• The optional property pricingDetails was added to the response with the 200 status in the GET /v2/contributors/{contributorId}/extensions/{extensionId} and PATCH /v2/contributors/{contributorId}/extensions/{extensionId} operations.
• The optional property /items/deletionProhibitedBy was added to the response with the 200 status in the GET /v2/customers operation.
• The optional property deletionProhibitedBy was added to the response with the 200 status in the GET /v2/customers/{customerId} operation.
• A non-success response with the status 400 was added in the GET /v2/customers/{customerId}/leads and GET /v2/customers/{customerId}/unlocked-leads operations.
• A non-success response with the status 409 was added in the POST /v2/ingresses operation.
• A non-success response with the status 404 was removed from the DELETE /v2/extension-instances/{extensionInstanceId} operation.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Get a DNS Zone"​

• ⚠️ Breaking: the 'recordSet/mx/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/records/items/fqdn' response property's maxLength was increased from '50' to '255' for the response status '200'

• ⚠️ Breaking: the 'recordSet/srv/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/records/items/fqdn' response property's maxLength was increased from '50' to '255' for the response status '200'

For details, refer to the GET/v2/dns-zones/{dnsZoneId}/ endpoint.

Changes in "Update a record set on a DNS Zone"​

• ⚠️ Breaking: the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/fqdn' request property's minLength was increased from '0' to '1'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/fqdn' request property's maxLength was set to '255'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/records/items/fqdn' request property's maxLength was increased from '50' to '255'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/records/items/fqdn' request property's maxLength was increased from '50' to '255'

For details, refer to the PUT/v2/dns-zones/{dnsZoneId}/record-sets/{recordSet}/ endpoint.

Changes in "updates cname-record for a specific zone"​

• ⚠️ Breaking: the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/fqdn' request property's minLength was increased from '0' to '1'

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordCNAMEComponent]/fqdn' request property's maxLength was set to '255'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/cname/ endpoint.

Changes in "List DNS Zones belonging to a Project"​

• ⚠️ Breaking: the '/items/recordSet/mx/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/records/items/fqdn' response property's maxLength was increased from '50' to '255' for the response status '200'

• ⚠️ Breaking: the '/items/recordSet/srv/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/records/items/fqdn' response property's maxLength was increased from '50' to '255' for the response status '200'

For details, refer to the GET/v2/projects/{projectId}/dns-zones/ endpoint.

Changes in "List Extensions of own contributor"​

• added the optional property '/items/pricingDetails' to the response with the '200' status

For details, refer to the GET/v2/contributors/{contributorId}/extensions/ endpoint.

Changes in "Get Extension of own contributor"​

• added the optional property 'pricingDetails' to the response with the '200' status

For details, refer to the GET/v2/contributors/{contributorId}/extensions/{extensionId}/ endpoint.

Changes in "Patch Extension"​

• added the optional property 'pricingDetails' to the response with the '200' status

For details, refer to the PATCH/v2/contributors/{contributorId}/extensions/{extensionId}/ endpoint.

Changes in "Get all customer profiles the authenticated user has access to"​

• added the optional property '/items/deletionProhibitedBy' to the response with the '200' status

For details, refer to the GET/v2/customers/ endpoint.

Changes in "Get a customer profile"​

• added the optional property 'deletionProhibitedBy' to the response with the '200' status

For details, refer to the GET/v2/customers/{customerId}/ endpoint.

Changes in "Get all leads. Use the unlocked routes for more lead details"​

• added the non-success response with the status '400'

For details, refer to the GET/v2/customers/{customerId}/leads/ endpoint.

Changes in "Get all unlocked leads. Organisation can unlock leads"​

• added the non-success response with the status '400'

For details, refer to the GET/v2/customers/{customerId}/unlocked-leads/ endpoint.

Changes in "updates mx-records for a specific zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordMXCustom]/records/items/fqdn' request property's maxLength was increased from '50' to '255'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/mx/custom/ endpoint.

Changes in "updates srv-records for a specific zone"​

• the '/oneOf[#/components/schemas/de.mittwald.v1.dns.RecordSRVComponent]/records/items/fqdn' request property's maxLength was increased from '50' to '255'

For details, refer to the PUT/v2/dns/zones/{zoneId}/recordset/srv/ endpoint.

Changes in "Delete a free extension instance. If the Extension is chargable the contract must be terminated instead"​

• removed the non-success response with the status '404'

For details, refer to the DELETE/v2/extension-instances/{extensionInstanceId}/ endpoint.

Changes in "List Extensions"​

• added the optional property '/items/pricingDetails' to the response with the '200' status

For details, refer to the GET/v2/extensions/ endpoint.

Changes in "Get an Extension"​

• added the optional property '/anyOf[#/components/schemas/de.mittwald.v1.marketplace.Extension]/pricingDetails' to the response with the '200' status

For details, refer to the GET/v2/extensions/{extensionId}/ endpoint.

Changes in "Create an Ingress"​

• added the non-success response with the status '409'

For details, refer to the POST/v2/ingresses/ endpoint.

Client package releases​

mittwald JavaScript SDK Release 4.263.0​

The mittwald JavaScript SDK has been updated to version 4.263.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 Release 4.262.0​

The mittwald JavaScript SDK has been updated to version 4.262.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 Release 4.261.0​

The mittwald JavaScript SDK has been updated to version 4.261.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.261.0.

mittwald JavaScript SDK Release 4.260.0​

The mittwald JavaScript SDK has been updated to version 4.260.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.

Summary​

• The response property '/items/webLink' became optional for the status '200' in the operation to list all invoices on behalf of a contributor. This is a breaking change.
• A required property '/items/invoiceType' was added to the response with the '200' status in the operation to list all invoices on behalf of a contributor.
• Multiple optional properties were added to the response with the '200' status in the operation to get all conversations the authenticated user has created or has access to:
  • '/items/createdBy/atlasGroup'
  • '/items/createdBy/group'
  • '/items/lastMessage/createdBy/atlasGroup'
  • '/items/lastMessage/createdBy/group'
  • '/items/lastMessageBy/atlasGroup'
  • '/items/lastMessageBy/group'
  • '/items/mainUser/atlasGroup'
  • '/items/mainUser/group'
• Multiple optional properties were added to the response with the '200' status in the operation to get a support conversation:
  • 'createdBy/atlasGroup'
  • 'createdBy/group'
  • 'lastMessage/createdBy/atlasGroup'
  • 'lastMessage/createdBy/group'
  • 'lastMessageBy/atlasGroup'
  • 'lastMessageBy/group'
  • 'mainUser/atlasGroup'
  • 'mainUser/group'
• Multiple optional properties were added to the response with the '200' status in the operation to get members of a support conversation:
  • '/items/allOf[#/components/schemas/de.mittwald.v1.conversation.User]/atlasGroup'
  • '/items/allOf[#/components/schemas/de.mittwald.v1.conversation.User]/group'
• Multiple optional properties were added to the response with the '200' status in the operation to get all messages of the conversation:
  • '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.Message]/createdBy/atlasGroup'
  • '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.Message]/createdBy/group'
  • '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/meta/user/atlasGroup'
  • '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/meta/user/group'

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "List all invoices on behalf of a contributor"​

• ⚠️ Breaking: the response property '/items/webLink' became optional for the status '200'

• added the required property '/items/invoiceType' to the response with the '200' status

For details, refer to the GET/v2/contributors/{contributorId}/invoices/outgoing/ endpoint.

Changes in "Get all conversation the authenticated user has created or has access to"​

• added the optional property '/items/createdBy/atlasGroup' to the response with the '200' status

• added the optional property '/items/createdBy/group' to the response with the '200' status

• added the optional property '/items/lastMessage/createdBy/atlasGroup' to the response with the '200' status

• added the optional property '/items/lastMessage/createdBy/group' to the response with the '200' status

• added the optional property '/items/lastMessageBy/atlasGroup' to the response with the '200' status

• added the optional property '/items/lastMessageBy/group' to the response with the '200' status

• added the optional property '/items/mainUser/atlasGroup' to the response with the '200' status

• added the optional property '/items/mainUser/group' to the response with the '200' status

For details, refer to the GET/v2/conversations/ endpoint.

Changes in "Get a support conversation"​

• added the optional property 'createdBy/atlasGroup' to the response with the '200' status

• added the optional property 'createdBy/group' to the response with the '200' status

• added the optional property 'lastMessage/createdBy/atlasGroup' to the response with the '200' status

• added the optional property 'lastMessage/createdBy/group' to the response with the '200' status

• added the optional property 'lastMessageBy/atlasGroup' to the response with the '200' status

• added the optional property 'lastMessageBy/group' to the response with the '200' status

• added the optional property 'mainUser/atlasGroup' to the response with the '200' status

• added the optional property 'mainUser/group' to the response with the '200' status

For details, refer to the GET/v2/conversations/{conversationId}/ endpoint.

Changes in "Get members of a support conversation"​

• added the optional property '/items/allOf[#/components/schemas/de.mittwald.v1.conversation.User]/atlasGroup' to the response with the '200' status

• added the optional property '/items/allOf[#/components/schemas/de.mittwald.v1.conversation.User]/group' to the response with the '200' status

For details, refer to the GET/v2/conversations/{conversationId}/members/ endpoint.

Changes in "Get all message of the conversation"​

• added the optional property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.Message]/createdBy/atlasGroup' to the response with the '200' status

• added the optional property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.Message]/createdBy/group' to the response with the '200' status

• added the optional property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/meta/user/atlasGroup' to the response with the '200' status

• added the optional property '/items/oneOf[#/components/schemas/de.mittwald.v1.conversation.StatusUpdate]/meta/user/group' to the response with the '200' status

For details, refer to the GET/v2/conversations/{conversationId}/messages/ endpoint.

Client package releases​

mittwald JavaScript SDK Release 4.259.0​

The mittwald JavaScript SDK has been updated to version 4.259.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: Release 4.259.0.

mittwald JavaScript SDK Release 4.258.0​

The mittwald JavaScript SDK has been updated to version 4.258.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.

mittwald JavaScript SDK Release 4.257.0​

The mittwald JavaScript SDK has been updated to version 4.257.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.

Summary​

• The minimum length of the 'token' request property for the POST /v2/users/self/credentials/password/confirm-reset operation has been increased from 6 to 20 characters. This is a breaking change.
• The maximum length of the 'token' request property for the POST /v2/users/self/credentials/password/confirm-reset operation has also been increased from 6 to 20 characters.
• New optional query request parameters 'limit', 'page', and 'skip' have been added to the POST /v2/actions/list-ingresses-compatible-with-certificate operation.
• A new optional request property '/oneOf[subschema #2]/pricePlan/variants/items/isBookingStopped' has been added to the PUT /v2/contributors/{contributorId}/extensions/{extensionId}/pricing operation.
• An optional property 'restorePath' has been added to the response with the '200' status for the GET /v2/project-backups/{projectBackupId} operation.
• A new endpoint GET /v2/project-backups/{projectBackupId}/path has been added to get the table of contents for a ProjectBackup.
• A new endpoint POST /v2/project-backups/{projectBackupId}/restore-path has been added to restore a ProjectBackup's path.
• An optional property '/items/restorePath' has been added to the response with the '200' status for the GET /v2/projects/{projectId}/backups operation.
• An optional property 'restorePath' has been added to the response with the '201' status for the POST /v2/projects/{projectId}/backups operation.
• A new endpoint PUT /v2/projects/{projectId}/mail-settings/{mailSetting} has been added to update a mail setting of a Project.
• A new endpoint PATCH /v2/projects/{projectId}/mail-settings/{setting} has been added to update a mail setting of a Project.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Confirm password reset"​

• ⚠️ Breaking: the 'token' request property's minLength was increased from '6' to '20'

• the 'token' request property's maxLength was increased from '6' to '20'

For details, refer to the POST/v2/users/self/credentials/password/confirm-reset/ endpoint.

Changes in "List Ingresses compatible with a certificate"​

• added the new optional 'query' request parameter 'limit'

• added the new optional 'query' request parameter 'page'

• added the new optional 'query' request parameter 'skip'

For details, refer to the POST/v2/actions/list-ingresses-compatible-with-certificate/ endpoint.

Changes in "Creates or Updates Pricing for an Extension"​

• added the new optional request property '/oneOf[subschema #2]/pricePlan/variants/items/isBookingStopped'

For details, refer to the PUT/v2/contributors/{contributorId}/extensions/{extensionId}/pricing/ endpoint.

Changes in "Get a project backup"​

• added the optional property 'restorePath' to the response with the '200' status

For details, refer to the GET/v2/project-backups/{projectBackupId}/ endpoint.

Changes in "Get table of contents for a project backup"​

• endpoint added

For details, refer to the GET/v2/project-backups/{projectBackupId}/path/ endpoint.

Changes in "Restore a project backup's path"​

• endpoint added

For details, refer to the unknown operation backup-request-project-backup-restore-path endpoint.

Changes in "List Backups belonging to a Project"​

• added the optional property '/items/restorePath' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/backups/ endpoint.

Changes in "Create a Backup of a Project"​

• added the optional property 'restorePath' to the response with the '201' status

For details, refer to the POST/v2/projects/{projectId}/backups/ endpoint.

Changes in "Update a mail setting of a Project"​

• endpoint added

For details, refer to the PUT/v2/projects/{projectId}/mail-settings/{mailSetting}/ endpoint.

Changes in "Update a mail setting of a Project"​

• endpoint added

For details, refer to the PATCH/v2/projects/{projectId}/mail-settings/{mailSetting}/ endpoint.

Client package releases​

mittwald JavaScript SDK Release 4.256.0​

The mittwald JavaScript SDK has been updated to version 4.256.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.256.0.

mittwald JavaScript SDK Release 4.255.0​

The mittwald JavaScript SDK has been updated to version 4.255.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 Release 4.254.0​

The mittwald JavaScript SDK has been updated to version 4.254.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 Release 4.253.0​

The mittwald JavaScript SDK has been updated to version 4.253.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.

mittwald JavaScript SDK Release 4.252.0​

The mittwald JavaScript SDK has been updated to version 4.252.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.

mittwald JavaScript SDK Release 4.251.1​

The mittwald JavaScript SDK version 4.251.1 has been released. This update includes a bug fix for the ConsistencyHandlingInterceptor. Specifically, the fix ensures that the if-event-reached header is only set if it is not already present. For more details, you can view the release on GitHub.

Summary​

• The response body type for the POST operation at /v2/authenticate has changed from 'object' to an unspecified type for the '400' status. Additionally, the required properties 'message' and 'type' have been removed from the response for the same status. This constitutes a breaking change.
• For the GET operation at /v2/customers/{customerId}/leads and /v2/customers/{customerId}/unlocked-leads, the type of the 'technologies' query parameter's '/items/' property has changed from 'string' to an unspecified type.
• The GET operation at /v2/customers/{customerId}/unlocked-leads has had several optional properties removed from the response with the '200' status, including 'leads/items/contact/address/address_prefix', 'leads/items/contact/address/country_code', and 'leads/items/contact/address/house_number'.
• The GET operation at /v2/customers/{customerId}/unlocked-leads/{leadId} has also had optional properties removed from the response with the '200' status, specifically 'contact/address/address_prefix', 'contact/address/country_code', and 'contact/address/house_number'.
• The POST operation at /v2/authenticate has added '#/components/schemas/de.mittwald.v1.commons.ValidationErrors' and '#/components/schemas/de.mittwald.v1.commons.Error' to the response body 'anyOf' list for the '400' status.
• A new non-success response with the status '412' has been added to the DELETE operation at /v2/contributors/{contributorId}/extensions/{extensionId}.
• A new endpoint has been added for the GET operation at /v2/cronjobs/{cronjobId}/executions/{executionId}/analysis.
• The GET operation at /v2/customers/{customerId}/unlocked-leads has added optional properties to the response with the '200' status, including 'leads/items/contact/address/addressPrefix', 'leads/items/contact/address/countryCode', and 'leads/items/contact/address/houseNumber'.
• The GET operation at /v2/customers/{customerId}/unlocked-leads/{leadId} has added optional properties to the response with the '200' status, including 'contact/address/addressPrefix', 'contact/address/countryCode', and 'contact/address/houseNumber'.
• The GET operation at /v2/projects/{projectId}/services has added the optional property '/items/deploy' to the response with the '200' status.
• The GET operation at /v2/projects/{projectId}/stacks has added the optional property '/items/services/items/deploy' to the response with the '200' status.
• The GET operation at /v2/stacks/{stackId} has added the optional property 'services/items/deploy' to the response with the '200' status.
• The PATCH operation at /v2/stacks/{stackId} has added the optional property 'services/items/deploy' to the response with the '200' status.
• The PUT operation at /v2/stacks/{stackId} has added the optional property 'services/items/deploy' to the response with the '200' status.
• The GET operation at /v2/stacks/{stackId}/services/{serviceId} has added the optional property 'deploy' to the response with the '200' status.

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Authenticate yourself to get an access token"​

• ⚠️ Breaking: the response's body type/format changed from 'object'/'' to ''/'' for status '400'

• ⚠️ Breaking: removed the required property 'message' from the response with the '400' status

• ⚠️ Breaking: removed the required property 'type' 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/authenticate/ endpoint.

Changes in "Get all leads. Use the unlocked routes for more lead details"​

• for the 'query' request parameter 'technologies', the type/format of property '/items/' was changed from 'string'/'' to ''/''

For details, refer to the GET/v2/customers/{customerId}/leads/ endpoint.

Changes in "Get all unlocked leads. Organisation can unlock leads"​

• for the 'query' request parameter 'technologies', the type/format of property '/items/' was changed from 'string'/'' to ''/''

• removed the optional property 'leads/items/contact/address/address_prefix' from the response with the '200' status

• removed the optional property 'leads/items/contact/address/country_code' from the response with the '200' status

• removed the optional property 'leads/items/contact/address/house_number' from the response with the '200' status

• added the optional property 'leads/items/contact/address/addressPrefix' to the response with the '200' status

• added the optional property 'leads/items/contact/address/countryCode' to the response with the '200' status

• added the optional property 'leads/items/contact/address/houseNumber' to the response with the '200' status

For details, refer to the GET/v2/customers/{customerId}/unlocked-leads/ endpoint.

Changes in "Get a detail of a unlocked lead. Organisation can unlock leads"​

• removed the optional property 'contact/address/address_prefix' from the response with the '200' status

• removed the optional property 'contact/address/country_code' from the response with the '200' status

• removed the optional property 'contact/address/house_number' from the response with the '200' status

• added the optional property 'contact/address/addressPrefix' to the response with the '200' status

• added the optional property 'contact/address/countryCode' to the response with the '200' status

• added the optional property 'contact/address/houseNumber' to the response with the '200' status

For details, refer to the GET/v2/customers/{customerId}/unlocked-leads/{leadId}/ endpoint.

Changes in "Delete an extension"​

• added the non-success response with the status '412'

For details, refer to the DELETE/v2/contributors/{contributorId}/extensions/{extensionId}/ endpoint.

Changes in "Get a cronjob execution analysis for failed executions"​

• endpoint added

For details, refer to the GET/v2/cronjobs/{cronjobId}/executions/{executionId}/analysis/ endpoint.

Changes in "List Services belonging to a Project"​

• added the optional property '/items/deploy' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/services/ endpoint.

Changes in "List Stacks belonging to a Project"​

• added the optional property '/items/services/items/deploy' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/stacks/ endpoint.

Changes in "Get a Stack"​

• added the optional property 'services/items/deploy' to the response with the '200' status

For details, refer to the GET/v2/stacks/{stackId}/ endpoint.

Changes in "Create, update or delete Services or Volumes belonging to a Stack"​

• added the optional property 'services/items/deploy' to the response with the '200' status

For details, refer to the PATCH/v2/stacks/{stackId}/ endpoint.

Changes in "Declaratively create, update or delete Services or Volumes belonging to a Stack"​

• added the optional property 'services/items/deploy' to the response with the '200' status

For details, refer to the PUT/v2/stacks/{stackId}/ endpoint.

Changes in "Get a Service belonging to a Stack"​

• added the optional property 'deploy' to the response with the '200' status

For details, refer to the GET/v2/stacks/{stackId}/services/{serviceId}/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.161​

The latest release of the mittwald PHP SDK, version v2.1.161, introduces new features and updates to enhance functionality and documentation clarity.

New Features​

• A new class, ExtensionDeleteExtensionPreconditionFailedResponse, has been introduced to handle specific HTTP responses for delete extension operations when preconditions fail.

Changes​

• Documentation updates in MarketplaceClient.php and MarketplaceClientImpl.php to provide clearer guidance on the extension deletion process.
• A new case has been added in MarketplaceClientImpl to handle 412 status code responses with the ExtensionDeleteExtensionPreconditionFailedResponse.

For more details, visit the release page.

mittwald PHP SDK Release v2.1.160​

The latest release of the mittwald PHP SDK, version v2.1.160, introduces several changes and removals to streamline and simplify the codebase.

Removed​

• The AuthenticateBadRequestResponse class has been removed. This class previously managed responses for bad authentication requests, including its associated methods and validation schema.

Changes​

• UserClientImpl Updates: The reference to AuthenticateBadRequestResponse has been removed. Handling for status code 400 now utilizes an UntypedResponse.
• CronjobExecutionAnalysis Updates: The class has been simplified by removing properties and methods related to issues and recommendation. It now focuses solely on handling a message, which reduces its complexity. The buildFromInput method and toJson output have been updated accordingly.

For more details, please visit the release page.

mittwald PHP SDK Release v2.1.159​

The mittwald PHP SDK has been updated to version v2.1.159. This release introduces several new features and API changes, primarily focusing on cronjob execution analysis.

Features​

• Cronjob Execution Analysis: A new feature has been added to retrieve detailed analyses of cronjob executions, particularly for failed executions. This includes messages about possible causes and recommendations for resolution.

API Changes​

• New Methods:

  • getExecutionAnalysis: This method allows users to obtain an analysis of failed cronjob executions by accepting a GetExecutionAnalysisRequest object and returning a GetExecutionAnalysisOKResponse.

• New Responses:

  • Various response classes have been introduced for the getExecutionAnalysis method, including:
    • GetExecutionAnalysisBadRequestResponse
    • GetExecutionAnalysisDefaultResponse
    • GetExecutionAnalysisForbiddenResponse
    • GetExecutionAnalysisInternalServerErrorResponse
    • GetExecutionAnalysisNotFoundResponse
    • GetExecutionAnalysisTooManyRequestsResponse
    • GetExecutionAnalysisOKResponse

• New Request Class:

  • GetExecutionAnalysisRequest: This new request class is used to fetch execution analysis, requiring an executionId and a cronjobId.

• New Schema Classes:

  • CronjobExecutionAnalysis: A schema class that outlines the structure of the cronjob execution analysis response.

• Updated Existing Schemas:

  • Adjustments have been made to existing schema classes under the Leadfyndr namespace, changing field names from snake_case to camelCase, such as:
    • address_prefix to addressPrefix
    • country_code to countryCode
    • house_number to houseNumber

For more details, visit the release page.

mittwald PHP SDK Release v2.1.158​

The latest release of the mittwald PHP SDK, version 2.1.158, introduces several enhancements and new features aimed at improving container management and resource allocation capabilities.

Added Features​

• New classes for container management, including Deploy, ResourceSpec, and Resources, have been introduced. These classes enhance the API's ability to manage container deployment specifications and resource allocation.

Updated Requests​

• ListLeadsRequest and ListUnlockedLeadsRequest have been updated to modify the technologies field. It now supports an array structure that can include a string type or the value 'none'. The type hint for technologies has been updated from string[]|null to mixed[]|null.

New Classes​

• Deploy: Defines the deployment schema for containers, including methods for managing resources, input validation, and JSON serialization.
• ResourceSpec: Represents resource specifications for containers, including CPU and memory constraints, with validation and serialization features.
• Resources: Provides a schema to define limits on resources for container deployments, wrapping around ResourceSpec and including methods for validation and input handling.

Updated Service Management​

• ServiceDeclareRequest and ServiceRequest: Both classes now include a deploy field referencing the new Deploy schema, with updated methods and input handling to support deployment specifications.
• ServiceResponse: Expanded to include a reference to the Deploy class for handling deployment information in responses.

These updates collectively enhance the API's flexibility and usability in managing container deployments and associated resources. For more details, visit the release page.

mittwald PHP SDK Release v2.1.157​

The mittwald PHP SDK has been updated to version v2.1.157. This release introduces new features and improvements:

Added​

• CheckMigrationIsPossibleErrorActiveMailArchiveForAddress Class: A new class designed to handle errors related to active mail archives during migration. It includes methods for validation, input processing, and JSON serialization.
• Array activeMailArchiveForAddress in PossibleCheckErrors: The PossibleCheckErrors schema now supports an array of CheckMigrationIsPossibleErrorActiveMailArchiveForAddress, enabling the reporting of multiple active mail archive errors simultaneously.

Changed​

• PossibleCheckErrors Constructor: Updated to accept and initialize the activeMailArchiveForAddress parameter.
• buildFromInput Method: Now creates instances of CheckMigrationIsPossibleErrorActiveMailArchiveForAddress from input data for the activeMailArchiveForAddress property.
• toJson Method: Enhanced to include serialization of the new activeMailArchiveForAddress property alongside existing error types.
• withActiveMailArchiveForAddress Method: Introduced to allow fluent modification of the activeMailArchiveForAddress property within PossibleCheckErrors.

For more details, visit the release page.

mittwald JavaScript SDK Release 4.251.0​

The mittwald JavaScript SDK has been updated to version 4.251.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.

mittwald JavaScript SDK Release 4.250.0​

The mittwald JavaScript SDK has been updated to version 4.250.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.

mittwald JavaScript SDK Release 4.249.0​

The mittwald JavaScript SDK has been updated to version 4.249.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.249.0.

mittwald JavaScript SDK Release 4.248.0​

The mittwald JavaScript SDK has been updated to version 4.248.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 Release 4.247.0​

The mittwald JavaScript SDK has been updated to version 4.247.0. This release introduces a new feature:

• Models: Added a contributor model to enhance the SDK's functionality (commit ff1d76e).

For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.247.0.

mittwald JavaScript SDK Release 4.246.0​

The mittwald JavaScript SDK has been updated to version 4.246.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.246.0.

mittwald JavaScript SDK Release 4.245.0​

The mittwald JavaScript SDK has been updated to version 4.245.0. This release includes a feature update to the generated client. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.245.0.

Summary​

• The type/format of the appInstallationId, cronjobId, customerId, fileId and projectId request parameters have changed from 'string'/'uuid' to 'string' for all operations. On a specification level, this might be considered a breaking change; however, this change only reflects the actual behavior of the API, and does not affect the generated client libraries.

• The response property 'chargeability' has become required for the status '200' in the following operations:

  • GET /v2/customers/{customerId}/extensions/{extensionId} (extension-get-extension-instance-for-customer)
  • GET /v2/extension-instances/{extensionInstanceId} (extension-get-extension-instance)
  • GET /v2/projects/{projectId}/extensions/{extensionId} (extension-get-extension-instance-for-project)

• The required property 'chargeability/reasons/isNonChargeableCustomer' has been added to the response with the '200' status in the following operations:

  • GET /v2/customers/{customerId}/extensions/{extensionId} (extension-get-extension-instance-for-customer)
  • GET /v2/extension-instances/{extensionInstanceId} (extension-get-extension-instance)
  • GET /v2/projects/{projectId}/extensions/{extensionId} (extension-get-extension-instance-for-project)
  • GET /v2/extension-instances (extension-list-extension-instances)

• The optional property '/items/scheduledDeletionDate' has been added to the response with the '200' status in the following operations:

  • GET /v2/domains (domain-list-domains)
  • GET /v2/domains/{domainId} (domain-get-domain)
  • GET /v2/projects/{projectId}/domains (deprecated-domain-list-domains)

• The following endpoints have been added:

  • DELETE /v2/domains/{domainId}/scheduled-deletion (domain-cancel-scheduled-deletion)
  • POST /v2/domains/{domainId}/scheduled-deletion (domain-create-scheduled-deletion)

Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.

Detailed changes​

Changes in "Trigger an uninstallation process for an app installation"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the DELETE/v2/app-installations/{appInstallationId}/ endpoint.

Changes in "Get an app installation"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/app-installations/{appInstallationId}/ endpoint.

Changes in "Update properties belonging to an app installation"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the PATCH/v2/app-installations/{appInstallationId}/ endpoint.

Changes in "Create linkage between an app installation and a MySQL database"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the PATCH/v2/app-installations/{appInstallationId}/database/ endpoint.

Changes in "Replace a MySQL Database with another MySQL Database"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the PATCH/v2/app-installations/{appInstallationId}/database/replace/ endpoint.

Changes in "Remove linkage between an app installation and a Database"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the DELETE/v2/app-installations/{appInstallationId}/databases/{databaseId}/ endpoint.

Changes in "Create linkage between an app installation and database users"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the PUT/v2/app-installations/{appInstallationId}/databases/{databaseId}/users/ endpoint.

Changes in "Get the missing requirements of an appInstallation for a specific target app version"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/app-installations/{appInstallationId}/missing-dependencies/ endpoint.

Changes in "Get the installed system software' for a specific app installation`"​

• ⚠️ Breaking: for the 'path' request parameter 'appInstallationId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/app-installations/{appInstallationId}/systemSoftware/ endpoint.

Changes in "Delete a cronjob"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the DELETE/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "Get a cronjob"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "Update a cronjob"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the PATCH/v2/cronjobs/{cronjobId}/ endpoint.

Changes in "Update a cronjob's app id"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the unknown operation cronjob-update-cronjob-app-id endpoint.

Changes in "List cronjob executions belonging to a cronjob"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/cronjobs/{cronjobId}/executions/ endpoint.

Changes in "Trigger a cronjob"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the POST/v2/cronjobs/{cronjobId}/executions/ endpoint.

Changes in "Get a cronjob execution"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/cronjobs/{cronjobId}/executions/{executionId}/ endpoint.

Changes in "Abort a cronjob execution"​

• ⚠️ Breaking: for the 'path' request parameter 'cronjobId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the unknown operation cronjob-abort-execution endpoint.

Changes in "Leave a Customer"​

• ⚠️ Breaking: for the 'path' request parameter 'customerId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the POST/v2/customers/{customerId}/actions/leave/ endpoint.

Changes in "Create a customer invite"​

• ⚠️ Breaking: for the 'path' request parameter 'customerId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the POST/v2/customers/{customerId}/invites/ endpoint.

Changes in "Get a File"​

• ⚠️ Breaking: for the 'path' request parameter 'fileId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/files/{fileId}/ endpoint.

Changes in "Get a File's meta"​

• ⚠️ Breaking: for the 'path' request parameter 'fileId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/files/{fileId}/meta/ endpoint.

Changes in "Get a File with user-friendly url"​

• ⚠️ Breaking: for the 'path' request parameter 'fileId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/files/{fileId}/{fileName}/ endpoint.

Changes in "List app installations belonging to a Project"​

• ⚠️ Breaking: for the 'path' request parameter 'projectId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/projects/{projectId}/app-installations/ endpoint.

Changes in "Request an app installation"​

• ⚠️ Breaking: for the 'path' request parameter 'projectId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the POST/v2/projects/{projectId}/app-installations/ endpoint.

Changes in "List cronjobs belonging to a Project"​

• ⚠️ Breaking: for the 'path' request parameter 'projectId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the GET/v2/projects/{projectId}/cronjobs/ endpoint.

Changes in "Create a cronjob"​

• ⚠️ Breaking: for the 'path' request parameter 'projectId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the POST/v2/projects/{projectId}/cronjobs/ endpoint.

Changes in "Create a ProjectInvite"​

• ⚠️ Breaking: for the 'path' request parameter 'projectId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the POST/v2/projects/{projectId}/invites/ endpoint.

Changes in "Leave a Project"​

• ⚠️ Breaking: for the 'path' request parameter 'projectId', the type/format was changed from 'string'/'uuid' to 'string'/''

For details, refer to the POST/v2/projects/{projectId}/leave/ endpoint.

Changes in "Get the extension instance of a specific customer and extension, if existing"​

• the response property 'chargeability' became required for the status '200'

• added the required property 'chargeability/reasons/isNonChargeableCustomer' to the response with the '200' status

For details, refer to the GET/v2/customers/{customerId}/extensions/{extensionId}/ endpoint.

Changes in "List Domains"​

• added the optional property '/items/scheduledDeletionDate' to the response with the '200' status

For details, refer to the GET/v2/domains/ endpoint.

Changes in "Get a Domain"​

• added the optional property 'scheduledDeletionDate' to the response with the '200' status

For details, refer to the GET/v2/domains/{domainId}/ endpoint.

Changes in "Cancel a scheduled deletion of a Domain"​

• endpoint added

For details, refer to the DELETE/v2/domains/{domainId}/scheduled-deletion/ endpoint.

Changes in "Create a scheduled deletion of a Domain"​

• endpoint added

For details, refer to the POST/v2/domains/{domainId}/scheduled-deletion/ endpoint.

Changes in "List extension instances"​

• the response property '/items/chargeability' became required for the status '200'

• added the required property '/items/chargeability/reasons/isNonChargeableCustomer' to the response with the '200' status

For details, refer to the GET/v2/extension-instances/ endpoint.

Changes in "Get an extension instance"​

• the response property 'chargeability' became required for the status '200'

• added the required property 'chargeability/reasons/isNonChargeableCustomer' to the response with the '200' status

For details, refer to the GET/v2/extension-instances/{extensionInstanceId}/ endpoint.

Changes in "List Domains belonging to a Project"​

• added the optional property '/items/scheduledDeletionDate' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/domains/ endpoint.

Changes in "Get the extension instance of a specific project and extension, if existing"​

• the response property 'chargeability' became required for the status '200'

• added the required property 'chargeability/reasons/isNonChargeableCustomer' to the response with the '200' status

For details, refer to the GET/v2/projects/{projectId}/extensions/{extensionId}/ endpoint.

Client package releases​

mittwald PHP SDK Release v2.1.156​

The mittwald PHP SDK has released version v2.1.156, introducing several new features and improvements. This release focuses on enhancing domain management capabilities and improving request and response handling.

New Features​

• Domain Scheduled Deletion Management:
  • Introduced the ability to create and cancel scheduled deletions for domains using CreateScheduledDeletion and CancelScheduledDeletion requests.
  • Enhanced domain schema with scheduledDeletionDate for improved lifecycle management.

Fixes and Improvements​

• Request and Response Models:
  • Removed format: "uuid" from certain request models for better validation.
  • Improved validation response handling to ensure proper error types are returned for bad or excessive requests.

New Response Types​

• Implemented new response types for error handling in scheduled deletion operations, including:
  • CancelScheduledDeletionBadRequestResponse
  • CancelScheduledDeletionTooManyRequestsResponse
  • CreateScheduledDeletionBadRequestResponse
• Enhanced default response handling for these operations.

Updates in Domain and Marketplace Schemas​

• Enhanced Domain schema with scheduledDeletionDate.
• Added Chargeability handling in ExtensionInstance schema for better data integrity.

These updates aim to streamline domain management and improve the overall API experience with enhanced validation and error handling. For more details, visit the release page.

mittwald JavaScript SDK Release 4.244.0​

The mittwald JavaScript SDK has been updated to version 4.244.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.

mittwald JavaScript SDK Release 4.243.0​

The mittwald JavaScript SDK version 4.243.0 has been released on October 21, 2025. This update includes a feature enhancement with an updated generated client. For more details, you can view the release on GitHub.

mittwald JavaScript SDK Release 4.242.3​

The mittwald JavaScript SDK has been updated to version 4.242.3. This release includes a version bump for the package root. For more details, you can view the release on GitHub: mittwald/api-client-js/releases/tag/4.242.3.

mittwald JavaScript SDK Release 4.242.2​

The mittwald JavaScript SDK has been updated to version 4.242.2. This release includes a version bump for the package root. For more details, you can view the release on GitHub: mittwald JavaScript SDK 4.242.2.

mittwald JavaScript SDK Release 4.242.1​

The mittwald JavaScript SDK has been updated to version 4.242.1. This release includes a version bump for the package root. For more details, you can view the release on GitHub here.