# Sample API review — Open-Meteo forecast endpoint

This is a public, reproducible sample of the evidence format offered by Shipshape/API. It is not a client case study and does not claim a relationship with Open-Meteo.

## Scope

- Endpoint: `GET https://api.open-meteo.com/v1/forecast`
- Query: `latitude=19.4326&longitude=-99.1332&current=temperature_2m,wind_speed_10m&timezone=UTC`
- Checks: response status, JSON content type, presence of the `current` object, and invalid-coordinate handling.

## Observed results

| Check | Result |
|---|---|
| Valid request | HTTP 200 |
| Content type | `application/json; charset=utf-8` |
| Expected payload | `current` object present |
| Invalid latitude (`200`) | HTTP 400 |

## Handoff notes

The happy path returns machine-readable JSON and the invalid coordinate is rejected with a client error. A production integration should still validate latitude/longitude ranges before sending the request, preserve the provider's error context, set a timeout, and test the exact fields used by downstream code.

## Reproduction

```powershell
Invoke-WebRequest `
  -Uri "https://api.open-meteo.com/v1/forecast?latitude=19.4326&longitude=-99.1332&current=temperature_2m,wind_speed_10m&timezone=UTC" `
  -UseBasicParsing
```

Captured on 2026-08-16 UTC. Public endpoint; no credentials or production access used.