> For the complete documentation index, see [llms.txt](https://docs.alphageo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphageo.ai/for-developers/alphageo-data-api/global-adaptation-layers-risk-api.md).

# Global Adaptation Layers Risk API

The risk data API endpoint allows you to retrieve detailed climate risk data under the Global Adaptation Layers data product for any location globally.

## Endpoint

```rest
GET https://app.alphageo.ai/api/public/v1/risk_data
```

## Parameters

<table><thead><tr><th>Parameters</th><th data-type="checkbox">Required</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>asset_id</td><td>false</td><td>string (UUID)</td><td>The unique identifier of an asset uploaded to your institution's account.</td></tr><tr><td>address</td><td>false</td><td>string</td><td>Full address of the location.</td></tr><tr><td>period</td><td>true</td><td>string</td><td><p>Time period.</p><p><em>Available values</em> : 2025, 2035, 2050, 2100</p></td></tr><tr><td>scenario</td><td>true</td><td>string</td><td><p>Identifier for CMIP6 Emission Scenarios.</p><p><em>Available values</em> : SSP245, SSP370, SSP585</p></td></tr><tr><td>longitude</td><td>false</td><td>number</td><td>Longitude of the location that being queried.</td></tr><tr><td>latitude</td><td>false</td><td>number</td><td>Latitude of the location that being queried.</td></tr></tbody></table>

### The 2025 baseline

Continue to supply `scenario=SSP245`, `SSP370` or `SSP585` when requesting `period=2025`. The 2025 physical baseline inputs are shared across these requests, and the response identifies the requested scenario. Climate indicators primarily use ERA5-Land reanalysis averaged over 2020–2025, with coverage fallbacks; other hazards retain their own source-specific baseline periods. The 2035, 2050 and 2100 horizons use scenario-specific inputs. See the [source and baseline FAQ](/climate-resilience-suite/data-products-faq.md).

### Query Validation Priority

When calling these endpoints, you must provide **at least one** way to identify the location. If multiple parameters are supplied, the API resolves the query using the following precedence:

1. **`asset_id`**: If provided, the API looks up the asset under your institution's profile.
2. **`latitude` & `longitude`**: If `asset_id` is not provided, the API looks up data by coordinates.
3. **`address`**: If neither of the above are provided, the API performs geocoding to resolve coordinates.

If none of these parameters are supplied, the API returns a `400 Bad Request` with an error message.

## Example requests

#### cURL

```bash
$ curl --location 'https://app.alphageo.ai/api/public/v1/risk_data?longitude=-97.2805288&latitude=32.7376509&period=2035&scenario=SSP245' \
--header 'Authorization: YOUR_API_TOKEN'
```

#### Python

```python
import requests

url = "https://app.alphageo.ai/api/public/v1/risk_data?longitude=-97.2805288&latitude=32.7376509&period=2035&scenario=SSP245"

payload = {}
headers = {
  'Authorization': 'YOUR_API_TOKEN'
}

response = requests.request("GET", url, headers=headers, data=payload)

print(response.text)

```

## Example response

The response below illustrates the field structure. Values are illustrative and do not represent a current assessment of the requested location or portfolio. `<current data version>` is a placeholder for the service’s configured `data_version` label.

A successful response containing physical climate risk data of the given location.

```json
{
  "identifiers": {
    "SCENARIO": "SSP245",
    "PERIOD": "2035"
  },
  "heat_stress": {
    "CDD": 1921.39,
    "HOTDAYS_ABV90P": 66.64
  },
  "inland_flooding": {
    "HEAVY_PR_DAYS": 17.44,
    "R_INUN_RP0100": 0,
    "R_INUN_RP1000": 0
  },
  "coastal_flooding": {
    "C_INUN_RP0100": 0,
    "C_INUN_RP1000": 0,
    "SUBSIDENCE": 0,
    "COASTAL_EROSION": 0
  },
  "drought": {
    "MAX_CONS_DRYDAYS_1MM": 32.62,
    "HOTDAYS40C": 21.76,
    "WS": 1.1
  },
  "hurricane_wind": {
    "HU_WS_RP0010": 0,
    "HU_WS_RP0025": 0,
    "HU_WS_RP0050": 0,
    "HU_WS_RP0100": 0,
    "HU_WS_RP0250": 0,
    "HU_WS_RP1000": 0,
    "HU_CAT_RP1000": 0
  },
  "wildfire": {
    "MAX_CONS_DRYDAYS_1MM": 32.62,
    "HOTDAYS40C": 21.76,
    "AVG_VC": 0
  },
  "hail": {
    "HAILDAYS": 7.16,
    "PR_DAYS_10MM": 28.5,
    "MAXTEMP": 43.71
  },
  "landslide": {
    "P_LANDSLIDE": 0.01,
    "HEAVY_PR_DAYS": 17.44
  },
  "earthquake": {
    "PGA": 0.05
  },
  "data_version": "<current data version>"
}
```

### Hurricane and flood fields

The six `HU_WS_RP*` fields report modelled median wind speeds in m/s for 10-, 25-, 50-, 100-, 250- and 1,000-year return periods. `HU_CAT_RP1000` is the category derived from the 1,000-year wind speed. Zero is the delivered value when there is no modelled exceedance; it is not evidence that data is missing.

This public endpoint exposes 100- and 1,000-year riverine and coastal flood depths. The wider download contract also includes `R_INUN_RP0250`, `R_INUN_RP0500`, `C_INUN_RP0250`, `C_INUN_RP0500`, `SLR_CHG` and `BURNABILITY_INDEX`; these are not returned by this endpoint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alphageo.ai/for-developers/alphageo-data-api/global-adaptation-layers-risk-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.