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: HP providerId: hp 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 - Device Management - Printing description: HP does not publish numeric rate limits on its developer portal for the HP Workforce Solutions Analytics API or HP PrintOS Device API. Limits are enforced behind the scenes per OAuth2 client / tenant consistent with the underlying service contract; partners exceeding fair-use thresholds are contacted directly. The PrintOS Device API is provisioned per device and inherits per-device telemetry limits set by HP Indigo product-line policies. notes: Public per-RPS / per-RPM numbers are not published. Limits negotiated per contract / per partner. sources: - https://developers.hp.com/hp-proactive-insights/api/hp-workforce-solutions-analytics-api - https://developers.hp.com/printos-hp-indigo-sdks-and-apis/device-api limits: - name: HP Workforce Solutions Analytics API scope: oauth_client + tenant metric: requests_per_minute limit: not publicly published; fair-use enforcement notes: Tenant-scoped under OAuth2; pace polling consistent with documented data-refresh cadence (typically hourly / daily aggregations). - name: HP PrintOS Device API scope: device metric: requests_per_minute limit: not publicly published; per-device telemetry policy notes: Device-scoped status and operations calls; telemetry frequency governed by HP Indigo product policy. policies: - name: OAuth2 Authentication description: All API calls require an OAuth2 access token obtained against tenant credentials. Refresh tokens have provider-defined lifetime. - name: Fair-Use Enforcement description: Sustained traffic that materially exceeds expected polling cadence may trigger throttling or partner outreach. - name: Backoff Strategy description: Implement exponential backoff with jitter on 429 / 503 responses; honor Retry-After header when present. - name: Polling Cadence description: Aggregated analytics data is refreshed on hourly / daily cadences; polling more frequently yields no new data and risks throttling. - name: Contract-Bound Access description: Production credentials are issued only to tenants with an active HP Active Care / Proactive Insights / PrintOS contract. Limits scale with the contract size. maintainers: - FN: Kin Lane email: info@apievangelist.com