<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Location Scanning API v3 missing expected data in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/location-scanning-api-v3-missing-expected-data/m-p/5397709#M59</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have the Location Scanning API v3 set up and are ingesting incoming events from it, but the data from it seems unexpectedly sparse. When I look at all clients seen in the last 2 hours, either via the online dashboard or the REST API, I see 5 clients. I would expect to see location events for all them. Only 2 of the 5, however, have location events coming in regularly. The rest have at most one event an hour, some even less than that.&lt;/P&gt;&lt;P&gt;Does anyone know if there is a setup step I am missing, or misunderstanding about the behavior of the API? If a client is connected to the network I would expect it to have an observation in each incoming location payload, with locations if it was seen by 3+ APs, or the latestRecord key if not.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;</description>
    <pubDate>Wed, 12 Feb 2025 23:04:58 GMT</pubDate>
    <dc:creator>JackReuter</dc:creator>
    <dc:date>2025-02-12T23:04:58Z</dc:date>
    <item>
      <title>Location Scanning API v3 missing expected data</title>
      <link>https://community.cisco.com/t5/network-platform-api/location-scanning-api-v3-missing-expected-data/m-p/5397709#M59</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have the Location Scanning API v3 set up and are ingesting incoming events from it, but the data from it seems unexpectedly sparse. When I look at all clients seen in the last 2 hours, either via the online dashboard or the REST API, I see 5 clients. I would expect to see location events for all them. Only 2 of the 5, however, have location events coming in regularly. The rest have at most one event an hour, some even less than that.&lt;/P&gt;&lt;P&gt;Does anyone know if there is a setup step I am missing, or misunderstanding about the behavior of the API? If a client is connected to the network I would expect it to have an observation in each incoming location payload, with locations if it was seen by 3+ APs, or the latestRecord key if not.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 23:04:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/location-scanning-api-v3-missing-expected-data/m-p/5397709#M59</guid>
      <dc:creator>JackReuter</dc:creator>
      <dc:date>2025-02-12T23:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: Location Scanning API v3 missing expected data</title>
      <link>https://community.cisco.com/t5/network-platform-api/location-scanning-api-v3-missing-expected-data/m-p/5397710#M60</link>
      <description>&lt;P&gt;According to v3 documentation, you should be getting an update for each network far more often (it says both once a minute and every 2-3 minutes).&lt;/P&gt;&lt;P&gt;Tbh I would be wary of expecting the client counts from UI/API to match the location API, especially with small numbers of clients.&lt;/P&gt;&lt;P&gt;As a next step, I'd try to physically verify the presence of active clients within range, and check if the location API is seeing them (and the UI/API too).&lt;/P&gt;&lt;P&gt;Then if there's a definite discrepancy that can't be explained, open a support case.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2025 10:22:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/location-scanning-api-v3-missing-expected-data/m-p/5397710#M60</guid>
      <dc:creator>sungod</dc:creator>
      <dc:date>2025-02-13T10:22:17Z</dc:date>
    </item>
  </channel>
</rss>

