
Developer documentation
CERA® API
Natural-catastrophe and weather hazard, delivered at the point of underwriting. One RESTful API returns the full exceedance curve (threshold, probability and return period) for any location on Earth, for every peril your key is licensed for.
Daily perils
12
plus expanding & lite modes
Per sync call
25
peril-event combinations
Per batch upload
100k
rows of scheduled risks
Coverage
Global
weather & NatCat models
Quickstart →
Make your first authenticated call in under five minutes.
Embedded map →
Drop the CERA® map into your own underwriting workbench: event overlays and your locations, geospatially.
API explorer →
Build a request and inspect the response. No code required.
Batch processing →
Run a full schedule of risks, up to 100,000 rows per upload.
Python SDK →
Idiomatic client for analysts and engineering teams.
What the API returns
Most hazard services return a single score or a lookup value. CERA® requests return the full hazard exceedance curve for the location: an array of thresholds, the probability of exceeding each threshold, and the equivalent return periods. That is the form a pricing actuary or exposure manager can build on: it feeds your own vulnerability curves and loss models rather than replacing them.
Two ways to work
| Mode | Endpoints | Latency | Limits | Use when |
|---|---|---|---|---|
| Synchronous | /v1/lite, /v2/in-depth |
Low (request/response) | ≤ 25 peril-event combinations per request | Single-risk lookups at point of underwriting; interactive tooling |
| Asynchronous | /v1/in-depth/batch |
Minutes, depending on size | Up to 100,000 rows per upload; key-tier dependent | Full schedules of risks, portfolio sweeps, renewal books |
Base URL
All endpoints are relative to this base URL. All requests must be made over HTTPS.