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: Truto
providerId: truto
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:
  - Unified API
  - Integrations
  - Rate Limiting
description: Truto markets "unlimited API calls" as part of both Expansion and Enterprise plans, but does
  not publish a public per-second / per-minute throttling number on its pricing or documentation pages.
  In practice, downstream rate limits flow from the third-party SaaS being integrated, and Truto's gateway
  acts as a passthrough subject to those upstream limits.
sources:
  - https://truto.one/pricing
  - https://truto.one/docs
notes: No public per-second or per-minute platform rate-limit numbers documented. Plans market unlimited
  API calls at the Truto layer; effective rate limits depend on the upstream connector (e.g. HubSpot,
  Salesforce) being unified.
limits:
  - name: Truto Platform API Calls
    scope: account
    metric: requests_per_year
    limit: -1
    timeFrame: year
    notes: Marketed as unlimited across both Expansion and Enterprise tiers.
  - name: Upstream Connector Limits
    scope: connector
    metric: varies
    limit: see upstream provider
    notes: Effective ceiling is set by the SaaS being unified (e.g. CRM, ATS, accounting); Truto inherits
      and surfaces those limits.
policies:
  - name: Upstream Passthrough
    description: Because Truto unifies third-party SaaS APIs, throttling behavior is largely defined by
      each upstream provider; Truto returns the upstream 429 / Retry-After signaling where available.
  - name: Active-Account Billing
    description: Billing is based on active accounts, not API call volume; this means rate-limit pressure
      is a connector-by-connector concern rather than a platform quota concern.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com