API rate limits

Follow

John Harrold

• August 23, 2026 17:07

Hello,

I'm building some tools to help me analyze my firewalla data. I signed up to the MSP program and started using API access. I noticed that my data collection stopped collecting ;) and I realized I was getting 529 responses. Sorry about that. Can you folks tell me what the caps are for API calls? I cannot seem to find it documented anywhere.

Thank you

0

• 

  Firewalla

  • August 23, 2026 17:47

  It is pretty rare that people hitting the 529, unless your API call is too frequent. (the API limit is not simple, so I can't really say, it is 100000 or 100 ... depend on the API)  May I know how often and API's are you calling? Do you do any type of throttling?

  0

  Comment actions Permalink
• 

  John Harrold

  • August 23, 2026 18:39

  I'm building a tool to visualize my flows using claude code. I asked it and this was the summary it produced:
  
  

  We call 4 documented endpoints, all GET, read-only, base https://<msp-domain>/v2:

  - Get Devices — GET /v2/devices
    - Polling, every 120 s → 30 calls/hour
  - Get Alarms — GET /v2/alarms?query=status:active&limit=25
    - Polling, every 120 s → 30 calls/hour
  - Get Flows (bandwidth sample) — GET /v2/flows?query=ts:<now-600>-<now>&groupBy=device&sortBy=total:desc&limit=60
    - Polling, every 120 s → 30 calls/hour
  - Get Flows (top talkers) — GET /v2/flows?query=ts:<now-3600>-<now>&groupBy=device&sortBy=total:desc&limit=60
    - Polling, every ~10 min → 6 calls/hour
  - Get Boxes — GET /v2/boxes
    - Polling, every ~10 min → 6 calls/hour
  - Get Flows (per-destination map) — GET /v2/flows?query=ts:<start>-<now>&groupBy=device&sortBy=total:desc&limit=60 and GET /v2/flows?query=ts:<start>-<now>&groupBy=device,destination&sortBy=total:desc&limit=400
    - On demand only, while a user has the Flows page open; response cached 180 s → up to ~40 calls/hour

  Per-endpoint totals (current):

  - /flows — ~36/hour idle, up to ~76/hour when the Flows page is open
  - /devices — 30/hour
  - /alarms — 30/hour
  - /boxes — 6/hour

  What we were doing when we hit HTTP 429 (now fixed):

  - /flows was running much hotter — bandwidth sample (30/hr) + top-talkers every 120 s instead of every 10 min (30/hr) + the per-destination map cached only 30 s against a 15 s UI auto-refresh (up to ~240/hr) = ~300 /flows calls/hour
  - The other endpoints were unchanged (~30/hr each)
  - This matches your note that limits are per-endpoint — we believe we tripped a low limit specific to /flows, not a global one

  0

  Comment actions Permalink

Please sign in to leave a comment.