Evisort · Rate Limits

Evisort Rate Limits

Evisort's REST API enforces authentication via a short-lived JWT bearer token obtained from an Evisort API key, which implies token-expiry and re-auth behavior. Specific published request-per-minute / request-per-day rate-limit numbers are not available in Evisort's public materials; the detailed API reference is behind an authenticated developer portal. No rate-limit values below are reconciled.

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

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

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

Tagged areas include Contract Lifecycle Management, CLM, Contract Intelligence, Document AI, and Legal Tech.

2 Limits Throttle: 429
Contract Lifecycle ManagementCLMContract IntelligenceDocument AILegal TechRate LimitingQuotasThrottling

Limits

Request Rate account
requests
see provider documentation
Concrete RPM/RPD thresholds are not publicly documented.
JWT Token Lifetime account
token_ttl
see provider documentation
Tokens issued by POST /auth/token are short-lived; re-authenticate on expiry.

Policies

Token-Based Authentication
An Evisort API key is exchanged for a short-lived JWT bearer token used on each request.
Backoff Strategy
Clients should implement retry with exponential backoff and honor 429 responses.

Sources