<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/72301/struggling-to-read-data-via-rest-api-with-thingy-91</link><description>Hello, 
 I&amp;#39;m trying to read data from the Thingy:91 via the REST-API. I can list the devices and query the state of the device, but I&amp;#39;m not sure how to progress. 
 So far I have used this to query the state of the device: 
 http api.nrfcloud.com/.../nrf</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Mar 2021 15:07:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/72301/struggling-to-read-data-via-rest-api-with-thingy-91" /><item><title>RE: Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/thread/298773?ContentTypeID=1</link><pubDate>Tue, 09 Mar 2021 15:07:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eaf619ac-57c4-40ad-9501-51274382c2fe</guid><dc:creator>franz_btu</dc:creator><description>&lt;p&gt;I figured it out, I had the wrong URL path. Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/thread/298752?ContentTypeID=1</link><pubDate>Tue, 09 Mar 2021 14:18:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:02600660-5865-471b-ac5c-84929c14e9af</guid><dc:creator>franz_btu</dc:creator><description>&lt;p&gt;Thanks, that also works for me. &lt;/p&gt;
&lt;p&gt;How do I interpret the bin file that is returned by curl?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/thread/298746?ContentTypeID=1</link><pubDate>Tue, 09 Mar 2021 14:15:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0af7f1a5-30b8-406c-9801-3fd9d9e0500a</guid><dc:creator>franz_btu</dc:creator><description>&lt;p&gt;So I tried the following:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;http POST &lt;a href="https://api.nrfcloud.com/v1/devices/nrf-.../messages"&gt;api.nrfcloud.com/.../messages&lt;/a&gt; \
  Authorization:&amp;quot;Bearer&lt;/code&gt; ...&amp;quot;&lt;/pre&gt;
&lt;p&gt;I only get the following answer:&lt;/p&gt;
&lt;p&gt;Result code: 404&lt;br /&gt;Not Found&lt;/p&gt;
&lt;p&gt;I also tried the nrf Pizza demo, everything works there.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/thread/298174?ContentTypeID=1</link><pubDate>Fri, 05 Mar 2021 16:31:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89512635-7789-4df6-a5e9-39d9063512ad</guid><dc:creator>Keith Leffler</dc:creator><description>&lt;p&gt;Apologies,&amp;nbsp; I think I missed your real question.&amp;nbsp; The /location/agps endpoint requires a device identifier as a parameter:&amp;nbsp;&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-sh"&gt;curl &lt;span class="token operator"&gt;-&lt;/span&gt;G $API_HOST&lt;span class="token operator"&gt;/&lt;/span&gt;location&lt;span class="token operator"&gt;/&lt;/span&gt;agps &lt;span class="token operator"&gt;-&lt;/span&gt;d &lt;span class="token string"&gt;&amp;quot;deviceIdentifier=$DEVICE_ID&amp;quot;&lt;/span&gt; &lt;span class="token operator"&gt;-&lt;/span&gt;H &lt;span class="token string"&gt;&amp;quot;Authorization: Bearer $API_KEY&amp;quot;&lt;/span&gt; &lt;span class="token operator"&gt;-&lt;/span&gt;H &lt;span class="token string"&gt;&amp;quot;Content-Type: application/octet-stream&amp;quot;&lt;/span&gt; &lt;span class="token operator"&gt;-&lt;/span&gt;H &lt;span class="token string"&gt;&amp;quot;Range: bytes=0-2200&amp;quot;&lt;/span&gt; &lt;span class="token operator"&gt;--&lt;/span&gt;output agps&lt;span class="token punctuation"&gt;.&lt;/span&gt;bin&lt;/code&gt;&lt;br /&gt;&lt;br /&gt;Please note: The just-released location services are designed to assist devices by providing additional &lt;br /&gt;information to the device about location. They do not provide a GPS location directly. That information is still&lt;br /&gt;found by GET &lt;a href="https://api.nrfcloud.com/v1/messages"&gt;https://api.nrfcloud.com/v1/messages&lt;/a&gt;, if GPS is enabled in the application.&lt;br /&gt;&lt;br /&gt;The single-cell endpoint (&lt;a href="https://api.nrfcloud.com/v1/location/single-cell"&gt;https://api.nrfcloud.com/v1/location/single-cell&lt;/a&gt;) provides the location of the &lt;br /&gt;cell tower matching the connection information passed in the parameters, along with an uncertainty radius.&lt;br /&gt;&lt;br /&gt;The agps endpoint (&lt;a href="https://api.nrfcloud.com/v1/location/agps"&gt;https://api.nrfcloud.com/v1/location/agps&lt;/a&gt;) provides a binary payload that &lt;br /&gt;&amp;quot;&lt;span&gt;Enables a faster time-to-first-fix (TTFF) for the GPS modem&amp;quot;. It basically provides information&lt;br /&gt;&lt;/span&gt;on satellite locations to help the GPS acquire a location fix faster.&lt;br /&gt;&lt;br /&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/thread/298155?ContentTypeID=1</link><pubDate>Fri, 05 Mar 2021 15:19:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47b112a6-3175-4f21-b106-1568108e6d90</guid><dc:creator>Keith Leffler</dc:creator><description>&lt;p&gt;Have you tried &amp;#39;https&amp;#39; instead of &amp;#39;http&amp;#39;&amp;nbsp; in your request?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/thread/298034?ContentTypeID=1</link><pubDate>Fri, 05 Mar 2021 11:36:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:604bce0c-8827-4c33-9cfe-95eacb0a89d6</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]I can list the devices and query the state of the device, but I&amp;#39;m not sure how to progress[/quote]
&lt;p&gt;This is good, means that the tokens etc. are in order.&lt;/p&gt;
[quote user=""]I&amp;#39;ve tried this path to access the GPS for example, but had no success:[/quote]
&lt;p&gt;&lt;a href="https://api.nrfcloud.com/v1#operation/FetchDevice"&gt;FetchDevice&lt;/a&gt; will give you the state of the device, however GPS data isn&amp;#39;t stored in the shadow, so you will need to query the messages:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://api.nrfcloud.com/v1#operation/ListMessages"&gt;https://api.nrfcloud.com/v1#operation/ListMessages&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Struggling to read data via REST-API with Thingy:91</title><link>https://devzone.nordicsemi.com/thread/297535?ContentTypeID=1</link><pubDate>Wed, 03 Mar 2021 13:38:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8cf00424-45ab-4274-8a71-8e108e85ee24</guid><dc:creator>franz_btu</dc:creator><description>&lt;p&gt;(I have replaced the real name and token with X and Y)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>