From 6c0dbd424967df21d56869c8887c78eab366b1e8 Mon Sep 17 00:00:00 2001
From: Qaunain Meghjee <65816071+QaunainM@users.noreply.github.com>
Date: Thu, 18 Apr 2024 09:58:33 +0100
Subject: [PATCH] Revert "Create APIproposal_Device_Volume.md"

---
 .../API proposals/APIproposal_Device_Volume.md         | 10 ----------
 1 file changed, 10 deletions(-)
 delete mode 100644 APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_Device_Volume.md

diff --git a/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_Device_Volume.md b/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_Device_Volume.md
deleted file mode 100644
index 2c696a0a..00000000
--- a/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_Device_Volume.md	
+++ /dev/null
@@ -1,10 +0,0 @@
-| **Field** | Description |
- | ---- | ----- |
- | API family name |Device Data Volume |
- | API family owner | Deutsche Telekom (Noel Wirzius)|
- | API summary | This API offers detailed insights into the customer's data usage status, including whether they have remaining data volume available and their current position within that volume allocation. It accurately determines whether the customer is nearing the beginning or the end of their allocated data volume, providing valuable information for managing data usage efficiently.|
- | Technical viability | The API should get information for a dedicated Sim-Card and also offer this in a subscription mode. The return value should not be a fixed value more an estimated indicator  (e.g. <200mb, <1Gb ...) |
- | Commercial viability | This API was requested by different content providers. It helps them to get more insights, how to deliver their traffic. | NO |
- | Validated in lab/productive environments? | Yes |
- | Validated with operators? | Yes |
- | Supporters in API Backlog Working Group | |