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: Amberflo
providerId: amberflo
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: true
tags:
  - Rate Limiting
  - Usage-Based Billing
  - Metering
  - Amberflo
description: Amberflo does not publish per-second rate limits on its public site. The Metering API is
  designed for high-throughput event ingestion and supports batch ingestion to amortize request count.
  Plan-level event volumes (10K Startups, 500K Growth) act as monthly quotas rather than per-second throttles.
  Treat 429 / 503 responses as throttle signals and apply exponential backoff.
sources:
  - https://docs.amberflo.io/reference
  - https://www.amberflo.io/pricing
notes: Per-second rate limits not published; plan-level monthly meter-event pools function as quotas.
  Open a support ticket for high-volume sustained ingest.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Meter event ingestion (Startups plan)
    scope: account
    metric: events_per_month
    limit: 10000
    timeFrame: month
    notes: Plan-level monthly quota; overage moves the customer above the included pool.
  - name: Meter event ingestion (Growth plan)
    scope: account
    metric: events_per_month
    limit: 500000
    timeFrame: month
    notes: Plan-level monthly quota; overage at $5 per additional 10,000 events.
  - name: Per-second API throughput
    scope: account
    metric: varies
    limit: not publicly documented
    notes: Use batch ingestion endpoints; contact support for sustained high-volume ingest.
policies:
  - name: Batch ingestion
    description: Use the bulk meter-events endpoint to amortize request count over many records and reduce
      request-rate pressure.
  - name: Exponential backoff
    description: Retry 429 and 503 responses with exponential backoff and jitter; respect Retry-After when
      present.
  - name: Idempotency
    description: Each meter event should carry a unique transactionId to allow safe retries without double-counting.
  - name: Plan-level quotas
    description: Monthly event and billing-volume pools are quotas tied to the subscription plan; exceeding
      triggers overage line items rather than throttling.
maintainers:
  - name: Kin Lane
    email: kin@apievangelist.com
    url: https://apievangelist.com
  - name: Amberflo
    email: support@amberflo.io
    url: https://www.amberflo.io