fix: Fixed delete operation response handling (#180)

Author: vijayasingam-paddle

CHANGELOG.md

@@ -20,6 +20,14 @@ in a response, this weakens the Typescript type but does not cause existing usag
 This means when upgrading minor versions of the SDK, you may notice type errors. You can safely ignore these or fix by
 adding additional type guards.
 
+## 3.2.1 - 2025-08-26
+
+### Fixed
+
+- Fixed a bug where `delete` operations were not returning failures correctly.
+
+---
+
 ## 3.2.0 - 2025-08-01
 
 ### Added

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@paddle/paddle-node-sdk",
-  "version": "3.2.0",
+  "version": "3.2.1",
   "description": "A Node.js SDK that you can use to integrate Paddle Billing with applications written in server-side JavaScript.",
   "main": "dist/cjs/index.cjs.node.js",
   "module": "dist/esm/index.esm.node.js",

src/internal/api/client.ts

@@ -109,6 +109,12 @@ export class Client {
 
     Logger.logResponse('DELETE', logUrl, headers, rawResponse);
 
-    return rawResponse as unknown as ErrorResponse | undefined;
+    if (rawResponse.ok) {
+      // Return undefined for successful delete operations
+      return rawResponse as unknown as undefined;
+    } else {
+      // Return the error response for unsuccessful delete operations
+      return rawResponse.json() as Promise<ErrorResponse>;
+    }
   }
 }