Hyperline · Rate Limits

Hyperline Rate Limits

Hyperline's REST API is authenticated per API key and follows REST conventions over HTTPS. Hyperline does not publish specific numeric request-per-minute or per-day rate limits in its public API reference; callers should handle HTTP 429 responses with exponential backoff. High-volume event ingestion is handled through the dedicated ingest endpoint and batch operations (billable-events batch, customers batch, invoices batch). Specific per-endpoint limit values are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests and events.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Billing, Subscriptions, Usage-Based, Metering, and Rate Limiting.

2 Limits Throttle: 429
BillingSubscriptionsUsage-BasedMeteringRate LimitingQuotasThrottling

Limits

API Requests api_key
requests
see provider documentation
No published numeric limit; expect HTTP 429 under sustained load.
Event Ingestion api_key
events
see provider documentation
High-volume events are ingested via the ingest endpoint and batch ingestion.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Batch Operations
Use batch endpoints (billable-events, customers, invoices) to reduce request volume for bulk workloads.

Sources