API changes for v2 API, October 2 to October 9
This week, the mittwald API introduces a new endpoint for rotating keys, adds optional properties to various invoice responses, and includes non-success status responses for specific operations.
This week, the mittwald API introduces a new endpoint for rotating keys, adds optional properties to various invoice responses, and includes non-success status responses for specific operations.
This week, the mittwald API introduces several enhancements, including the addition of optional properties to existing responses, new endpoints for managing DNS zone-file imports, and expanded activity log schemas for project activities.
This week, the mittwald API introduces several changes, including the addition of new optional request parameters and properties, the requirement of request bodies for specific endpoints, and updates to response properties, enhancing the overall functionality and flexibility of the API.
This week's update to the mittwald API includes the removal of the 'application/json' media type for '204' responses in several endpoints, the addition of new optional and required properties across various responses, and the introduction of new endpoints for managing app installations and extensions.
In the week of July 3 to July 10, 2026, the mittwald API introduced several changes, including the addition of new endpoints for mail rate limits and template statistics, the removal of optional properties from project activity responses, and the addition of required properties and new optional request parameters across various endpoints.
This week's changes are primarily spec cleanup and new endpoint additions. The conversation-related changes are technically breaking but have no practical impact on existing integrations — the actual API responses remain unchanged.
This week's update to the mittwald API includes a reduction of the minimum values for the 'limit' and 'page' query parameters to '0.00' across multiple endpoints, the addition of required properties to responses, and the introduction of a new optional request parameter, enhancing flexibility and usability for developers.
This week's update to the mittwald API includes significant changes such as modifications to the authentication response structure, the addition of new endpoints for contact verifications, and the introduction of optional properties across various responses.
This week's update to the mittwald API includes significant changes such as the removal of several required properties from the response of the conversation messages endpoint, the addition of new enum values, and the introduction of optional request parameters for listing extensions.
This week's changelog for the mittwald API includes significant updates such as changes to response property types, the removal of required properties, the addition of new optional parameters, and the introduction of new endpoints.