@opusdns/api 0.89.0 → 0.90.0

package/package.json

@@ -3,7 +3,7 @@
     "@opusdns/api-spec-ts-generator": "^0.9.1"
   },
   "name": "@opusdns/api",
-  "version": "0.89.0",
+  "version": "0.90.0",
   "description": "TypeScript types for the OpusDNS OpenAPI specification",
   "main": "./src/index.ts",
   "module": "./src/index.ts",

package/src/helpers/responses.d.ts

@@ -1676,11 +1676,30 @@ export type GET_DnsSummary_Response_200 = DnsZoneSummary
  * @path /v1/domain-forwards/{zone_name}/{request_protocol}
  * @param zone_name (path) - DNS zone name (trailing dot optional)
  *
+ * @see {@link DELETE_DomainForwardsByZoneNameByRequestProtocol_Response_404} - 404 response type
  * @see {@link DELETE_DomainForwardsByZoneNameByRequestProtocol_Response_422} - 422 response type
  *
 
  */
-export type DELETE_DomainForwardsByZoneNameByRequestProtocol_Response = DELETE_DomainForwardsByZoneNameByRequestProtocol_Response_422;
+export type DELETE_DomainForwardsByZoneNameByRequestProtocol_Response = DELETE_DomainForwardsByZoneNameByRequestProtocol_Response_404 | DELETE_DomainForwardsByZoneNameByRequestProtocol_Response_422;
+
+/**
+ * 404 response for DELETE DomainForwardsByZoneNameByRequestProtocol endpoint
+ *
+ * @remarks
+ * This type defines the response structure for the 404 status code
+ * of the DELETE DomainForwardsByZoneNameByRequestProtocol endpoint.
+ * It provides type safety for handling this specific response as defined in the OpenAPI specification.
+ *
+
+ *
+ * @path /v1/domain-forwards/{zone_name}/{request_protocol}
+ * @param zone_name (path) - DNS zone name (trailing dot optional)
+ *
+ * @see {@link DELETE_DomainForwardsByZoneNameByRequestProtocol_Response} - The main response type definition
+ * @see {@link Problem} - The actual schema type definition
+ */
+export type DELETE_DomainForwardsByZoneNameByRequestProtocol_Response_404 = Problem
 
 /**
  * 422 response for DELETE DomainForwardsByZoneNameByRequestProtocol endpoint
@@ -1851,12 +1870,12 @@ export type POST_DomainForwardsByZoneNameByRequestProtocol_Response_422 = HTTPVa
  * @param zone_name (path) - DNS zone name (trailing dot optional)
  *
  * @see {@link PUT_DomainForwardsByZoneNameByRequestProtocol_Response_200} - 200 response type
- * @see {@link PUT_DomainForwardsByZoneNameByRequestProtocol_Response_409} - 409 response type
+ * @see {@link PUT_DomainForwardsByZoneNameByRequestProtocol_Response_404} - 404 response type
  * @see {@link PUT_DomainForwardsByZoneNameByRequestProtocol_Response_422} - 422 response type
  *
 
  */
-export type PUT_DomainForwardsByZoneNameByRequestProtocol_Response = PUT_DomainForwardsByZoneNameByRequestProtocol_Response_200 | PUT_DomainForwardsByZoneNameByRequestProtocol_Response_409 | PUT_DomainForwardsByZoneNameByRequestProtocol_Response_422;
+export type PUT_DomainForwardsByZoneNameByRequestProtocol_Response = PUT_DomainForwardsByZoneNameByRequestProtocol_Response_200 | PUT_DomainForwardsByZoneNameByRequestProtocol_Response_404 | PUT_DomainForwardsByZoneNameByRequestProtocol_Response_422;
 
 /**
  * 200 response for PUT DomainForwardsByZoneNameByRequestProtocol endpoint
@@ -1877,10 +1896,10 @@ export type PUT_DomainForwardsByZoneNameByRequestProtocol_Response = PUT_DomainF
 export type PUT_DomainForwardsByZoneNameByRequestProtocol_Response_200 = DomainForward
 
 /**
- * 409 response for PUT DomainForwardsByZoneNameByRequestProtocol endpoint
+ * 404 response for PUT DomainForwardsByZoneNameByRequestProtocol endpoint
  *
  * @remarks
- * This type defines the response structure for the 409 status code
+ * This type defines the response structure for the 404 status code
  * of the PUT DomainForwardsByZoneNameByRequestProtocol endpoint.
  * It provides type safety for handling this specific response as defined in the OpenAPI specification.
  *
@@ -1892,7 +1911,7 @@ export type PUT_DomainForwardsByZoneNameByRequestProtocol_Response_200 = DomainF
  * @see {@link PUT_DomainForwardsByZoneNameByRequestProtocol_Response} - The main response type definition
  * @see {@link Problem} - The actual schema type definition
  */
-export type PUT_DomainForwardsByZoneNameByRequestProtocol_Response_409 = Problem
+export type PUT_DomainForwardsByZoneNameByRequestProtocol_Response_404 = Problem
 
 /**
  * 422 response for PUT DomainForwardsByZoneNameByRequestProtocol endpoint

package/src/openapi.yaml

@@ -5005,7 +5005,7 @@ info:
     '
   summary: OpusDNS - your gateway to a seamless domain management experience.
   title: OpusDNS API
-  version: 2025-10-29-093948
+  version: 2025-10-29-163217
   x-logo:
     altText: OpusDNS API Reference
     url: https://d24lr4zqs1tgqh.cloudfront.net/c9505a20-5ae1-406c-b060-d392569caebf.jpg
@@ -6562,6 +6562,18 @@ paths:
       responses:
         '204':
           description: Successful Response
+        '404':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_DOMAIN_FORWARD_NOT_EXISTS
+                detail: Domain forward not found
+                status: 404
+                title: Domain Forward Error
+                type: domain-forward-not-found
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Not Found
         '422':
           content:
             application/problem+json:
@@ -6640,12 +6652,11 @@ paths:
           content:
             application/problem+json:
               example:
-                code: ERROR_DOMAIN_FORWARD_REDIRECT_ALREADY_EXISTS
-                detail: Redirect already exists for A, d, d, i, t, i, o, n, a, l,  ,
-                  e, r, r, o, r,  , c, o, n, t, e, x, t, .
+                code: ERROR_DOMAIN_FORWARD_ALREADY_EXISTS
+                detail: Domain forward already exists
                 status: 409
                 title: Domain Forward Error
-                type: domain-forward-redirect-already-exists
+                type: domain-forward-already-exists
               schema:
                 $ref: '#/components/schemas/Problem'
           description: Conflict
@@ -6689,19 +6700,18 @@ paths:
               schema:
                 $ref: '#/components/schemas/DomainForward'
           description: Successful Response
-        '409':
+        '404':
           content:
             application/problem+json:
               example:
-                code: ERROR_DOMAIN_FORWARD_REDIRECT_NOT_EXISTS
-                detail: Redirect does not exist for A, d, d, i, t, i, o, n, a, l,  ,
-                  e, r, r, o, r,  , c, o, n, t, e, x, t, .
-                status: 409
+                code: ERROR_DOMAIN_FORWARD_NOT_EXISTS
+                detail: Domain forward not found
+                status: 404
                 title: Domain Forward Error
-                type: domain-forward-redirect-not-exists
+                type: domain-forward-not-found
               schema:
                 $ref: '#/components/schemas/Problem'
-          description: Conflict
+          description: Not Found
         '422':
           content:
             application/problem+json:

package/src/schema.d.ts

@@ -5903,18 +5903,18 @@ export interface operations {
                     "application/json": components["schemas"]["DomainForward"];
                 };
             };
-            /** @description Conflict */
-            409: {
+            /** @description Not Found */
+            404: {
                 headers: {
                     [name: string]: unknown;
                 };
                 content: {
                     /** @example {
-                     *       "code": "ERROR_DOMAIN_FORWARD_REDIRECT_NOT_EXISTS",
-                     *       "detail": "Redirect does not exist for A, d, d, i, t, i, o, n, a, l,  , e, r, r, o, r,  , c, o, n, t, e, x, t, .",
-                     *       "status": 409,
+                     *       "code": "ERROR_DOMAIN_FORWARD_NOT_EXISTS",
+                     *       "detail": "Domain forward not found",
+                     *       "status": 404,
                      *       "title": "Domain Forward Error",
-                     *       "type": "domain-forward-redirect-not-exists"
+                     *       "type": "domain-forward-not-found"
                      *     } */
                     "application/problem+json": components["schemas"]["Problem"];
                 };
@@ -5963,11 +5963,11 @@ export interface operations {
                 };
                 content: {
                     /** @example {
-                     *       "code": "ERROR_DOMAIN_FORWARD_REDIRECT_ALREADY_EXISTS",
-                     *       "detail": "Redirect already exists for A, d, d, i, t, i, o, n, a, l,  , e, r, r, o, r,  , c, o, n, t, e, x, t, .",
+                     *       "code": "ERROR_DOMAIN_FORWARD_ALREADY_EXISTS",
+                     *       "detail": "Domain forward already exists",
                      *       "status": 409,
                      *       "title": "Domain Forward Error",
-                     *       "type": "domain-forward-redirect-already-exists"
+                     *       "type": "domain-forward-already-exists"
                      *     } */
                     "application/problem+json": components["schemas"]["Problem"];
                 };
@@ -6003,6 +6003,22 @@ export interface operations {
                 };
                 content?: never;
             };
+            /** @description Not Found */
+            404: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    /** @example {
+                     *       "code": "ERROR_DOMAIN_FORWARD_NOT_EXISTS",
+                     *       "detail": "Domain forward not found",
+                     *       "status": 404,
+                     *       "title": "Domain Forward Error",
+                     *       "type": "domain-forward-not-found"
+                     *     } */
+                    "application/problem+json": components["schemas"]["Problem"];
+                };
+            };
             /** @description Validation Error */
             422: {
                 headers: {