Palantir API Limit and Concurrency Control

Overview

Protect Foundry and the caller from retry storms. Budget requests across the acting user, bound concurrent work, honor server responses, and distinguish retryable throttling from authorization, validation, or permanent resource errors.

Prerequisites

• Identify the acting user or service user, applications sharing it, endpoints, workload peaks, page/batch shape, and service objective.
• Capture response status, request identifiers, timestamps, server timing guidance, retry count, and current concurrency.
• Read references/official-docs.md immediately before setting numeric budgets because effective and endpoint-specific limits may change.
• Prepare load tests in an approved non-production scope.

Current Contract

• The current general API documentation lists global per-user rate and concurrency limits across Foundry API endpoints.
• Individual endpoints may impose stricter limits and return 429 or 503.
• Palantir recommends exponential backoff for throttled requests.
• Limits can vary in practice, and disruptive throttling may require Palantir Support rather than client-side limit evasion.