Reggora · Rate Limits

Reggora Rate Limits

Reggora does not publish fixed numeric rate limits for its Lender API or Vendor API in the public reference. Access is provisioned per contracted integration (JWT bearer token plus a per-integration API key), and throughput is governed by that integration agreement and Reggora's platform protections rather than by a published per-minute request cap. Asynchronous notifications are pushed as outbound HTTP POST webhooks (order created, order updated, loan deleted); consuming integrations should return 2xx promptly and process webhook payloads asynchronously.

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

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

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

Tagged areas include Appraisal Management, Mortgage, Lending, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Appraisal ManagementMortgageLendingRate LimitingQuotas

Limits

Lender API Requests integration
requests
not published
No fixed numeric request-rate limit is documented for the Lender API; governed per integration agreement.
Vendor API Requests integration
requests
not published
No fixed numeric request-rate limit is documented for the Vendor API.
Webhook Delivery integration
events
event-driven
Outbound HTTP POST callbacks per subscribed event; not a client request quota.

Policies

Authentication
Every request requires a valid JWT bearer token plus a per-integration API key; unauthorized requests are rejected.
Environment Separation
Sandbox (sandbox.reggora.io) and production (api.reggora.io) are separate; test against sandbox before production.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 or 5xx responses.
Webhook Acknowledgement
Return a 2xx quickly to acknowledge webhook receipt and process the payload asynchronously to avoid delivery retries.

Sources