Breaking (!) API changes for v2 API, July 29, 2024
This document contains a machine-generated summary of the API changes for July 29, 2024. The API changes are based on the diff between the OpenAPI schemas of the two versions.
Summary
- A
429 Too Many Requests
status code has been added to the specification of every API endpoint. This status code is returned when the rate limit is exceeded. The rate limiting feature is not new, but the documentation has been updated to reflect this behavior. See the section on API ratelimiting for more information. - Changed the way the request body of the PATCH
/
endpoint is defined (might potentially cause breaking changes in generated client code).v2/ ingresses/ {ingressId}/ tls/
Detailed changes
Changes in "Update the tls settings of an Ingress"
- ⚠️ Breaking: replaced '#/components/schemas/de.mittwald.v1.ingress.TlsAcme, #/components/schemas/de.mittwald.v1.ingress.TlsCertificate' from the request body 'oneOf' list, and substituted inline schemas. Note that this is not a breaking change when you are using the API directly, but it might cause breaking changes in code generated from the OpenAPI schema.
For details, refer to the PATCH/
endpoint.
Changes to all API endpoints
- added the non-success response with the status '429'
Changes in "Create an Order"
- removed the non-success response with the status '403'
For details, refer to the POST/
endpoint.
Changes in "Register with email and password"
- removed the non-success response with the status '403'
For details, refer to the POST/
endpoint.
Changes in "Resend the mail address verification email"
- removed the non-success response with the status '403'
For details, refer to the POST/
endpoint.
Changes in "Initialize password reset process"
- removed the non-success response with the status '403'
For details, refer to the POST/
endpoint.
Changes in "Initialize password reset process"
- removed the non-success response with the status '403'
For details, refer to the POST/
endpoint.