# Storage Integration V3 Access Problem **URL:** \ **Category:** V3 Integrations\ **Created:** [June 5, 2021, 4:15pm UTC](https://www.thethingsnetwork.org/forum/t/storage-integration-v3-access-problem/48484 "2021-06-05T16:15:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![PeterH61](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/peterh61/32/45413_2.png) [@PeterH61](https://www.thethingsnetwork.org/forum/u/PeterH61)\ **Post date:** [June 5, 2021, 4:15pm UTC](https://www.thethingsnetwork.org/forum/t/storage-integration-v3-access-problem/48484/1 "2021-06-05T16:15:35Z")
Dear TTN/TTS fans, I migrated my Greenhouse Climate Device from V2 to V3 successfully. Data are visible at the TTS application console as expected. The access to the V3 Storage Integration data by Curl unfortunately not successfully. I used this example, found in the TTS documentation: $ curl -G “[https://thethings.example.com/api/v3/as/applications/app1/devices/dev1/packages/storage/uplink\_message](https://thethings.example.com/api/v3/as/applications/app1/devices/dev1/packages/storage/uplink_message)” -H “Authorization: Bearer $API\_KEY” -H “Accept: text/event-stream” -d “limit=10” -d “after=2020-08-20T00:00:00Z” -d “field\_mask=up.uplink\_message.decoded\_payload” and from the storage integration page: “GET [https://eu1.cloud.thethings.network/api/v3/as/api/v3/as/applications/{application-id}/devices/{device\_id}/packages/storage/{type}”](https://eu1.cloud.thethings.network/api/v3/as/api/v3/as/applications/%7Bapplication-id%7D/devices/%7Bdevice_id%7D/packages/storage/%7Btype%7D%E2%80%9D) I generated the API\_KEY adapted the Curl command as follows: “-X GET ‘[https://eu1.cloud.thethings.network/api/v3/as/api/v3/as/applications/{application-id}/devices/{device-id}/packages/storage/uplink\_message](https://eu1.cloud.thethings.network/api/v3/as/api/v3/as/applications/%7Bapplication-id%7D/devices/%7Bdevice-id%7D/packages/storage/uplink_message)’ -H ‘Accept: text/event-stream’ -H ‘Authorization: Bearer NNSXS.xxx.xxx’ -d ‘limit=10’ -d ‘after=2021-06-01T00:00:00Z’”; The call was executed on an “HomeMatic” CCU3 by C++ script with following result: **{“code”:12,“message”:“Not Implemented”}** The available entries in the forum in this regard were unfortunately not helpful for me, and I found no additional information for this return code in the TTS documentation. What do I wrong? I tried also skipping the limit, after and field mask parameters… Thanks a lot for helping in advance, Peter p.s.: This was the V2 Curl command, which was running without any problems: “-X GET --header ‘Accept: application/json’ --header 'Authorization: key ttn-account-v2.xxx’ ‘https://{application-id}.data.thethingsnetwork.org/api/v2/query/{device-id}’”; ---
**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\ **Post date:** [June 6, 2021, 10:48am UTC](https://www.thethingsnetwork.org/forum/t/storage-integration-v3-access-problem/48484/2 "2021-06-06T10:48:19Z")
> [@PeterH61](#): > > ‘[https://eu1.cloud.thethings.network/api/v3/as/api/v3/as/applications/{application-id}/devices/{device-id}/packages/storage/uplink\_message](https://eu1.cloud.thethings.network/api/v3/as/api/v3/as/applications/%7Bapplication-id%7D/devices/%7Bdevice-id%7D/packages/storage/uplink_message)’ Did you replace the app-id and device-id ??? This works for me: ``` curl -G "https://eu1.cloud.thethings.network/api/v3/as/applications/myFunkyApplicationID/packages/storage/uplink_message" \ -H "Authorization: Bearer NNSXS.randomStuffHere" \ -H "Accept: text/event-stream" \ -d "limit=10" \ -d "after=2020-08-20T00:00:00Z" ``` I’m presuming you’ve turned on Data Storage as well … ---
**Author:** ![PeterH61](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/peterh61/32/45413_2.png) [@PeterH61](https://www.thethingsnetwork.org/forum/u/PeterH61)\ **Post date:** [June 6, 2021, 8:18pm UTC](https://www.thethingsnetwork.org/forum/t/storage-integration-v3-access-problem/48484/3 "2021-06-06T20:18:49Z")
Hi, thank you very much for your reply. Your example was the way to success. I double, triple checked my data, but finally it was not my fault. Pfhhhh. 😊 Please see the screen shot of the Storage Integration page. I remarked the “V3/as/” which is too much… After correcting the string the call worked as expected 😊. This should be corrected on the console page. What is the correct way for an documentation issue? Best Regards Peter ![Storage Integration](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/d/9/d95359bb8d304d8128f0c3e94c9774f3dff4aec5.jpeg) ---
**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\ **Post date:** [June 6, 2021, 8:24pm UTC](https://www.thethingsnetwork.org/forum/t/storage-integration-v3-access-problem/48484/4 "2021-06-06T20:24:30Z")
> [@PeterH61](#): > > What is the correct way for an documentation issue? Please open an issue on GitHub - but for the lorawan-stack not for the docs, the docs are correct and what’s appearing there is in the console. ---
**Author:** ![PeterH61](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/peterh61/32/45413_2.png) [@PeterH61](https://www.thethingsnetwork.org/forum/u/PeterH61)\ **Post date:** [June 10, 2021, 12:40pm UTC](https://www.thethingsnetwork.org/forum/t/storage-integration-v3-access-problem/48484/5 "2021-06-10T12:40:32Z")
According to the TTN software engeneer, the fix is merged and will be part of the 3.13.2 release. ---
**Author:** ![system](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/6/2/6250ea44fd2b0d6259489e1a92748df681e1f970.png) [@system](https://www.thethingsnetwork.org/forum/u/system)\ **Post date:** [June 11, 2021, 12:41pm UTC](https://www.thethingsnetwork.org/forum/t/storage-integration-v3-access-problem/48484/6 "2021-06-11T12:41:19Z")
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.