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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-04.
Written by API Evangelist on 2026-07-04 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/reggora-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.