Blend · Rate Limits

Blend Mortgage Rate Limits

Blend does not publish fixed numeric rate limits for the Public API in its open developer documentation. Blend's security documentation states that rate limiting is applied (notably for non-authenticated traffic) and that requests are gated by API Secret Keys exchanged for short-lived, request-scoped JWTs at the API Gateway, plus optional customer-provided IP allowlisting. Effective throughput is therefore governed by the customer/partner agreement and the API Gateway policy for a given tenant rather than by a publicly stated per-minute cap.

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

It captures 3 rate-limit definitions, measuring requests and tokens.

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

Tagged areas include Digital Lending, Mortgage, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Digital LendingMortgageRate LimitingQuotas

Limits

Public API Requests tenant
requests
not published
No fixed numeric request-rate limit is documented publicly; governed per tenant at the API Gateway.
Unauthenticated Requests ip
requests
rate-limited
Blend applies rate limiting to non-authenticated traffic per its security documentation.
Token Scope request
tokens
short-lived per-request JWT
API Secret Keys are exchanged for short-lived, request-scoped JWTs at the API Gateway.

Policies

IP Allowlisting
Customers can provide an IP allowlist so only approved source addresses may call the API.
Version Pinning
Every call should send the blend-api-version header to pin behavior to a specific API version.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources