<?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 Clarification Regarding API Call Response Timing in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/clarification-regarding-api-call-response-timing/m-p/5428471#M4709</link>
    <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Hi Community,&lt;/P&gt;&lt;P&gt;I need some clarification:&lt;/P&gt;&lt;P&gt;When I make an API call to "/organizations/{organizationId}/uplinks/statuses," and receive a status like "active," "ready," or "failed," is that status representative of the device's current state at the time of the API call, or does the data returned reflect historical information? For example, if I make an API call at 1 pm, will the status of the device returned be based on its state at that time, or from a different time?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;Example payload:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;{&lt;/DIV&gt;&lt;DIV&gt;"networkId": "N_80",&lt;/DIV&gt;&lt;DIV&gt;"serial": "Q2CZ-S6JR",&lt;/DIV&gt;&lt;DIV&gt;"model": "VMX-L",&lt;/DIV&gt;&lt;DIV&gt;"highAvailability": {&lt;/DIV&gt;&lt;DIV&gt;"enabled": false,&lt;/DIV&gt;&lt;DIV&gt;"role": "primary"&lt;/DIV&gt;&lt;DIV&gt;},&lt;/DIV&gt;&lt;DIV&gt;"lastReportedAt": "2024-04-30T02:45:23Z",&lt;/DIV&gt;&lt;DIV&gt;"uplinks": [&lt;/DIV&gt;&lt;DIV&gt;{&lt;/DIV&gt;&lt;DIV&gt;"interface": "wan1",&lt;/DIV&gt;&lt;DIV&gt;"status": "active",&lt;/DIV&gt;&lt;DIV&gt;"ip": "10.11.7.12",&lt;/DIV&gt;&lt;DIV&gt;"gateway": "10.11.79.97",&lt;/DIV&gt;&lt;DIV&gt;"publicIp": "103.X.X.231",&lt;/DIV&gt;&lt;DIV&gt;"primaryDns": "10.11.7.2",&lt;/DIV&gt;&lt;DIV&gt;"secondaryDns": "0.0.0.0",&lt;/DIV&gt;&lt;DIV&gt;"ipAssignedBy": "dhcp"&lt;/DIV&gt;&lt;DIV&gt;}&lt;/DIV&gt;&lt;DIV&gt;]&lt;/DIV&gt;&lt;DIV&gt;},&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Apr 2024 02:55:36 GMT</pubDate>
    <dc:creator>SuperM</dc:creator>
    <dc:date>2024-04-30T02:55:36Z</dc:date>
    <item>
      <title>Clarification Regarding API Call Response Timing</title>
      <link>https://community.cisco.com/t5/network-platform-api/clarification-regarding-api-call-response-timing/m-p/5428471#M4709</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Hi Community,&lt;/P&gt;&lt;P&gt;I need some clarification:&lt;/P&gt;&lt;P&gt;When I make an API call to "/organizations/{organizationId}/uplinks/statuses," and receive a status like "active," "ready," or "failed," is that status representative of the device's current state at the time of the API call, or does the data returned reflect historical information? For example, if I make an API call at 1 pm, will the status of the device returned be based on its state at that time, or from a different time?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;Example payload:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;{&lt;/DIV&gt;&lt;DIV&gt;"networkId": "N_80",&lt;/DIV&gt;&lt;DIV&gt;"serial": "Q2CZ-S6JR",&lt;/DIV&gt;&lt;DIV&gt;"model": "VMX-L",&lt;/DIV&gt;&lt;DIV&gt;"highAvailability": {&lt;/DIV&gt;&lt;DIV&gt;"enabled": false,&lt;/DIV&gt;&lt;DIV&gt;"role": "primary"&lt;/DIV&gt;&lt;DIV&gt;},&lt;/DIV&gt;&lt;DIV&gt;"lastReportedAt": "2024-04-30T02:45:23Z",&lt;/DIV&gt;&lt;DIV&gt;"uplinks": [&lt;/DIV&gt;&lt;DIV&gt;{&lt;/DIV&gt;&lt;DIV&gt;"interface": "wan1",&lt;/DIV&gt;&lt;DIV&gt;"status": "active",&lt;/DIV&gt;&lt;DIV&gt;"ip": "10.11.7.12",&lt;/DIV&gt;&lt;DIV&gt;"gateway": "10.11.79.97",&lt;/DIV&gt;&lt;DIV&gt;"publicIp": "103.X.X.231",&lt;/DIV&gt;&lt;DIV&gt;"primaryDns": "10.11.7.2",&lt;/DIV&gt;&lt;DIV&gt;"secondaryDns": "0.0.0.0",&lt;/DIV&gt;&lt;DIV&gt;"ipAssignedBy": "dhcp"&lt;/DIV&gt;&lt;DIV&gt;}&lt;/DIV&gt;&lt;DIV&gt;]&lt;/DIV&gt;&lt;DIV&gt;},&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2024 02:55:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/clarification-regarding-api-call-response-timing/m-p/5428471#M4709</guid>
      <dc:creator>SuperM</dc:creator>
      <dc:date>2024-04-30T02:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification Regarding API Call Response Timing</title>
      <link>https://community.cisco.com/t5/network-platform-api/clarification-regarding-api-call-response-timing/m-p/5428472#M4710</link>
      <description>&lt;P&gt;If you don't use any extra parameters (startingAfter or endingBefore) it would be a return of the current status at time of the request&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2024 03:10:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/clarification-regarding-api-call-response-timing/m-p/5428472#M4710</guid>
      <dc:creator>Ryan_Miles</dc:creator>
      <dc:date>2024-04-30T03:10:03Z</dc:date>
    </item>
  </channel>
</rss>

