API Catalog
Skill109 starsChanged 10 months agoMITView on GitHub
Reference guide for connecting popular APIs to Home Assistant via Node-RED, YAML, or custom integrations. Covers authentication, endpoints, and complete working examples for: energy APIs (Tibber, Nordpool), weather (SMHI, OpenWeatherMap, yr.no), transport (SL, Trafikverket, Resrobot), smart home clouds (Shelly, Tuya, Philips Hue, IKEA), and global APIs (OpenAI, Spotify, Google Calendar, Telegram, GitHub). Use this skill whenever the user mentions a specific external service, API, or data source they want to connect to Home Assistant - even if they don't say "API".
- Reads credentials
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- auroraSkill
- ESPHomeSkill
- HA Dashboard DesignSkill
- HA Integration DevSkill
- Home Assistant YAMLSkill
- Node-REDSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Never paste real tokens into chat, flows that get exported, or YAML committed to git.
- Distinctive: line 39
Read the relevant reference file for auth setup and endpoints
- Very specific: line 70
Full integration: Use ha-integration skill with the polling-integration template
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
API Catalog for Home Assistant
Reference skill for connecting external APIs and services to Home Assistant.
Overview
This skill covers authentication patterns and working code examples for connecting popular APIs to Home Assistant via three methods:
- Node-RED - HTTP request node flows (fastest to get running)
- HA YAML -
restsensor andrest_command(good for simple polling) - Custom integration - Full HACS-publishable Python component (use
ha-integrationskill)
The Iron Law
CREDENTIALS IN SECRETS - NEVER HARDCODED IN FLOWS OR YAMLAPI keys belong in Node-RED credentials, ESPHome secrets.yaml, or HA secrets.yaml.
Never paste real tokens into chat, flows that get exported, or YAML committed to git.
How to Use This Skill
- User mentions an API or service by name
- Read the relevant reference file for auth setup and endpoints
- Generate working code for the user's chosen method (Node-RED / YAML / integration)
- Include credential setup instructions
Reference Files
| Category | File | APIs Covered |
| Energy & electricity | references/energy-apis.md | Tibber, Nordpool, Energi Data Service |
| Weather | references/weather-apis.md | SMHI, OpenWeatherMap, yr.no, Tomorrow.io |
| Transport | references/transport-apis.md | SL, Trafikverket, Resrobot, Entur (NO) |
| Smart home clouds | references/smarthome-apis.md | Shelly Cloud, Tuya IoT, Philips Hue, IKEA Dirigera |
| Global / other | references/global-apis.md | OpenAI, Spotify, Google Calendar, Telegram, GitHub |
Authentication Patterns at a Glance
| Pattern | How it works | Examples |
| API key in header | Authorization: Bearer {key} or X-API-Key: {key} | Tibber, OpenAI |
| API key in URL | ?appid={key} appended to URL | OpenWeatherMap |
| OAuth2 | Get access token first, refresh periodically | Spotify, Google |
| Local token | One-time press-button auth on device | Philips Hue |
| No auth | Public API, no credentials needed | SMHI, yr.no, Nordpool |
| Basic auth | Username + password Base64-encoded | Some local devices |
Output Methods
For each API, generate code for the method the user needs:
Node-RED: http request node + function node to parse + api-call-service to push to HA
HA YAML: rest sensor platform or rest_command under configuration.yaml
Full integration: Use ha-integration skill with the polling-integration template
Common Patterns
Node-RED: API key in header
{
"type": "http request",
"method": "GET",
"url": "https://api.example.com/data",
"headers": {"Authorization": "Bearer {{env.API_KEY}}"},
"ret": "obj"
}Node-RED: GraphQL (Tibber-style)
{
"type": "http request",
"method": "POST",
"url": "https://api.tibber.com/v1-beta/gql",
"headers": {
"Authorization": "Bearer {{env.TIBBER_TOKEN}}",
"Content-Type": "application/json"
},
"payload": "{\"query\": \"{ viewer { homes { currentSubscription { priceInfo { current { total } } } } } }\"}",
"ret": "obj"
}HA YAML: REST sensor
rest:
- scan_interval: 300
resource: https://api.example.com/current
headers:
Authorization: !secret example_api_key
sensor:
- name: "Example Value"
value_template: "{{ value_json.data.value }}"
unit_of_measurement: "°C"Pre-Output Checklist
- Credentials use
!secret(YAML), Node-RED credentials, or env vars - never hardcoded - Rate limits respected (include
scan_intervalor flow timer accordingly) - Error handling included (Node-RED catch node or YAML timeout)
- For OAuth2: refresh token flow explained
- Attribution: which API endpoint, what data it returns
Integration
Pairs with:
node-redskill - for flow JSON implementationha-yamlskill - for YAML sensor and automation using the fetched dataha-integrationskill - for building a full HACS-publishable Python integration
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

