1Forge · Rate Limits

1Forge Rate Limits

1Forge meters REST consumption against a per-API-key monthly quota set by the caller's subscription tier (Starter / Premium / Business / Business Plus). The /quota endpoint returns current consumption, the plan limit, remaining requests, and hours until the quota resets. WebSocket streaming is gated by plan rather than by raw request rate and is unavailable on the free tier. 1Forge does not publish per-second or per-minute throttling numbers; consumers should treat the quota window as the primary throttle and back off on 401 responses.

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

It captures 2 rate-limit definitions, measuring requests_per_month and concurrent_requests.

The profile also includes 5 backoff/retry policies defined and response codes documented for invalidApiKey and quotaExceeded.

Tagged areas include Rate Limiting, Forex Data, and Quota.

2 Limits Quota: 401
Rate LimitingForex DataQuota

Limits

Monthly REST request quota (per API key) key
requests_per_month · month
per-plan; observed example quota_limit 5000 / month; see https://1forge.com/pricing for current per-tier numbers
Inspect via GET /quota. quota_used, quota_limit, and hours_until_reset are returned per call.
WebSocket streaming session key
concurrent_requests
per-plan; not available on free tier
Streaming runs over a single WebSocket at wss://sockets.1forge.com/socket. Above the free tier, exact session caps are not publicly documented.

Policies

Quota inspection
Use GET /quota at any time to inspect quota_used, quota_limit, quota_remaining, and hours_until_reset for the calling key.
Quota-driven backoff
When the key is over quota, the API returns the standard "API Key Not Valid" error envelope. Consumers should treat quota exhaustion as a fail-closed condition until hours_until_reset elapses.
Reset cadence
Quota resets on a per-key basis; hours_until_reset reflects the current rolling window for the key.
WebSocket heartbeat
The server sends `heart` keep-alive frames; clients reply with `beat` to keep the stream open.
Server-initiated disconnect
A `force_close` frame from the server instructs the client to drop the connection. Clients should not auto-reconnect on `force_close` without a backoff window.

Sources