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: Nomba
providerId: nomba
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: false
tags:
  - Rate Limiting
  - Payments
  - Fintech
  - Nigeria
notes: Nomba does not publish HTTP rate limits on its marketing site, and the API documentation host
  (docs.api.nomba.com) was unreachable at reconciliation time. Reconcile against the live developer
  documentation when accessible. Listed limits are scaffold placeholders.
description: Nomba's public-facing rate-limit policy is not currently documented on accessible web surfaces.
  Production limits are most likely enforced per merchant API key with idempotency-key support consistent
  with most Nigerian payment processors. Verify against the current Nomba API reference.
sources:
  - https://nomba.com/
  - https://docs.api.nomba.com/
responseCodes:
  throttled: 429
limits:
  - name: Nomba API
    scope: api_key
    metric: varies
    limit: see Nomba API documentation
    notes: Public docs were unreachable at reconciliation; per-merchant limits typically configured at
      onboarding.
policies:
  - name: Idempotency
    description: Use idempotency keys on payment-creation calls to safely retry on transient errors —
      standard practice for Nigerian payment processors; verify with current Nomba docs.
  - name: Webhooks
    description: Nomba issues webhooks for payment / transfer state changes; consumers should ack within
      the webhook timeout to avoid retries.
  - name: Sandbox vs production
    description: Use Nomba sandbox keys for development to avoid production-quota consumption.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com