specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Augmentt
providerId: augmentt
generated: '2026-09-14'
method: searched
source: https://support.augmentt.com/kb/en/augmentt-api-548051
created: '2026-05-04'
modified: '2026-09-14'
# 2026-09-14: this file previously held a bulk-sweep SCAFFOLD asserting X-RateLimit-* headers, 429
# responses and free/professional/enterprise tiers of 10/100/1000 rpm. Augmentt publishes none of
# that. The scaffold has been replaced with the measured absence.
tags:
  - MSP
  - Microsoft 365
  - SaaS Management
  - Rate Limiting
description: >-
  Augmentt publishes no rate limits for its API. The full API reference — availability, key issuance,
  authentication, the endpoint table, the response-code table and the troubleshooting FAQ — names no
  quota, no per-minute or per-day ceiling, no burst allowance, no 429 status and no rate-limit
  response header. An integrator cannot tell from the documentation how often they may poll.
limit_count: 0
headers_documented: false
headers: {}
responseCodes:
  throttled: null
  documented_statuses: [200, 400, 401, 403, 404, 500]
limits: []
policies: []
findings:
  - >-
    No 429 appears in the documented response-code table. The only documented failure statuses are
    400, 401, 403, 404 and 500.
  - >-
    No X-RateLimit-*, RateLimit-* or Retry-After header is documented anywhere in the reference.
  - >-
    The API is fronted by AWS API Gateway (an anonymous GET to https://api.augmentt.com/ returns
    {"message":"Missing Authentication Token"}, observed 2026-09-14), which carries account-level
    throttling defaults. Augmentt does not publish what those are set to, so nothing can be asserted
    about the effective ceiling.
  - >-
    Because every endpoint is a full-report GET with no pagination and no date filtering, polling
    cost is driven by tenant count and report size rather than by a published call budget.
recommendation_to_provider: >-
  Publish the per-key call ceiling and emit RateLimit-Limit / RateLimit-Remaining / RateLimit-Reset
  (RFC 9331 style) plus Retry-After on exhaustion. An agent or a scheduled BI sync currently has no
  runtime signal to back off against.
evidence:
  - url: https://support.augmentt.com/kb/en/augmentt-api-548051
    status: 200
    note: Full API reference read 2026-09-14; no rate-limit content present.
  - url: https://api.augmentt.com/
    status: 403
    note: Anonymous probe; AWS API Gateway edge response, no rate-limit headers returned.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com