diff --git a/documentation/API proposals/APIproposal_IoT_Data_Transfer_Activation_TIM.md b/documentation/API proposals/APIproposal_IoT_Data_Transfer_Activation_TIM.md
new file mode 100644
index 0000000..1e68386
--- /dev/null
+++ b/documentation/API proposals/APIproposal_IoT_Data_Transfer_Activation_TIM.md	
@@ -0,0 +1,12 @@
+| **Field** | Description | 
+| ---- | ----- |
+| API family name | IoT Data Transfer Activation |
+| API family owner | TIM |
+| API summary | A Service Provider has requested the Telco Platform to instantiate an Application in different Edge Data Centers. These application instances, altogether, provide a Service offered to End User via a mobile network. The Service Provider wants to reserve network capacity in a specific time window for a fleet of IoT devices, to schedule background data transfers for non-urgent updates or downloads during off-peak hours. A system from the Service Provider invokes the IoT Data Transfer Activation API to ask for the reservation.|
+| Technical viability | This API can leverage on Rel 18 Nnef_BDTPNegotiation and the Npcf_PolicyAuthorization_Create API as defined in 3GPP TS 23.502 (Procedures for the 5G System)</em>. 
+| Commercial viability | Under development in IPCEI (www.ipcei-cis.eu). </em>|
+| YAML code available? | YES. |
+| Validated in lab/productive environments? | NO. |
+| Validated with real customers? | NO. |
+| Validated with operators? | NO. |
+| Supporters in API Backlog Working Group | List of supporters. <br><em> NOTE: That shall be added by the Working Group. </em> |
\ No newline at end of file