Apidog · Rate Limits

Apidog Rate Limits

Apidog has not published explicit per-second / per-minute / per-month rate limits for its public REST API at https://api.apidog.com. Documented controls are instead tied to plan-level seat counts, project counts, sprint-branch counts, and scheduled-task frequency. This file captures the shape of those plan-level limits along with the standard 429 / Retry-After signaling expected on the platform. Replace with provider-published per-key limits if and when Apidog publishes them.

Apidog Rate Limits is the machine-readable rate-limit profile for Apidog on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 7 rate-limit definitions, across the free, basic, professional, and enterprise tiers, measuring team_members, projects, branches, request_history_days, and scheduled_import_interval_minutes.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include API Design, API Lifecycle, API Testing, Collaboration, and Design-First.

7 Limits Throttle: 429 Quota: 429
API DesignAPI LifecycleAPI TestingCollaborationDesign-FirstDocumentationMockingPlatformRate LimitingThrottling

Limits

Free Plan Members organization
team_members · lifetime
4
Free Plan Projects organization
projects · lifetime
5
Free Plan Sprint Branches Per Project project
branches · lifetime
1
Basic Plan Projects organization
projects · lifetime
20
Basic Plan Request History organization
request_history_days · month
90
Professional Plan Scheduled Import Interval organization
scheduled_import_interval_minutes · minute
10
Enterprise Plan Scheduled Tasks organization
scheduled_tasks · month
-1

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor the Retry-After header when a 429 response is returned.
Quota Reset
Plan-level entitlements (projects, members, branches) are persistent and reset only on plan change. Scheduled-task and request-history windows reset on a rolling basis aligned to the documented timeFrame.
Fair Use
Sustained automation against the public Apidog REST API that materially impacts shared infrastructure may be subject to fair-use throttling even when no explicit per-key limit is published.
Versioning
Requests must send the X-Apidog-Api-Version header. Apidog supports previous versions for at least three months after a newer version is released.