Overview
The Future Weather API gives developers a programmatic way to generate climate-adjusted EPW and DDY weather files for technical workflows. Instead of using the web interface manually, your applications can submit jobs, monitor processing status, and retrieve future weather outputs directly through authenticated API calls.
The API follows the same core methodology as the Future Weather platform: start with a historical EPW, apply CMIP6 climate projection signals for a selected future year and scenario, and produce future EPW outputs, with DDY generation available when requested for supported workflows.
This public page is meant to help developers understand what is available and whether the API fits their workflow. Full interactive reference documentation, personal access tokens, and webhook management remain available inside the authenticated application.
What you can build
Automated simulation pipelines
Generate future EPW and DDY files automatically as part of internal modeling, QA, or scenario comparison workflows.
Batch climate studies
Run multiple future years and emissions scenarios across portfolios, research studies, or productized workflows.
Weather analytics
Retrieve comparison analytics between historical and future weather conditions for reporting and downstream applications.
Building performance tools
Embed climate-adjusted weather generation into building performance, HVAC sizing, and resilience analysis products.
Webhook-driven systems
Trigger downstream jobs when weather generation completes instead of relying only on client-side polling.
Optional DDY workflows
Request DDY generation alongside EPW output when your design or compliance workflow requires it.
How it works
1. Upload a historical EPW
Submit a historical EPW and choose a target future year, scenario, plus any optional DDY or advanced parameters needed for your workflow.
2. Process the job asynchronously
Future Weather applies CMIP6-driven morphing logic to generate future-ready outputs while preserving realistic hourly structure.
3. Download results or trigger follow-on work
Poll for status or receive a webhook, then download the generated EPW, optional DDY, and any related analytics for automation pipelines.
Authentication
Bearer-token authentication
Authenticated API requests use a Bearer token. Signed-in users can create and manage personal access tokens inside the Future Weather application.
Example request
A typical first integration sends a job request with a historical EPW file and a target future year. Additional parameters like scenario, models, and DDY-related inputs can be added when you need both EPW and DDY outputs.
curl -X POST https://app.futureweather.co/jobs \
-H "Authorization: Bearer fw_your_personal_access_token" \
-H "Idempotency-Key: <a-stable-random-uuid>" \
-F "future_year=2080" \
-F "epw_file=@/path/to/file.epw"
# Optional fields:
# -F "scenario=ssp245"
# -F "models=BCC-CSM2-MR"
# -F "outputs=DDY"
# -F "ddy_file=@/path/to/historical.ddy"The full API reference includes more detail on request fields, response structure, job polling, webhook signatures, analytics endpoints, and rate limits.
What you get back
Future EPW output
Every successful job produces a future EPW file suitable for simulation workflows and technical analysis.
Optional DDY generation
When requested with the right inputs, jobs can also produce future DDY outputs aligned with the morphed weather file.
Job status and downloads
Use status and download endpoints to monitor progress and retrieve results cleanly from automated clients.
Comparison analytics
Completed jobs can expose analytics comparing historical and future weather conditions for reporting or decision support.
Ready to integrate?
Sign in to access the full API reference, create personal access tokens, configure webhooks, and explore more detailed EPW and DDY request examples. This public page is intended as a starting point, while the authenticated app provides the full developer toolkit.
Full API documentation is available to authorized users inside the Future Weather application.