Use cases/No-code & smart displays
[UC 06]
How people wire esports and UFC data into n8n, Home Assistant and desk displays
Seen in our API traffic
n8n workflows, Home Assistant integrations and ESP32 devices all call Cito directly.
sensor:
- platform: rest
name: Next UFC card
resource: https://api.citoapi.com/api/v1/ufc/events/upcoming?limit=1
headers:
x-api-key: !secret cito_api_key
value_template: "{{ value_json.data[0].name }}"
scan_interval: 3600Challenge
Hobby projects need data that just works with a simple HTTP request: no SDK, no OAuth, no parsing a web page that changes every week.
Solution
Plain JSON over HTTPS with one header. Drop it into an n8n HTTP node, a Home Assistant REST sensor or an ESP32 sketch.
What you get
- Live score on a desk display or smart-home dashboard
- Fight-night and match-day automations
- Notifications through any n8n integration
- Works on microcontrollers: one header, small JSON
One header, plain JSON
Every endpoint is a GET with an x-api-key header, so it works in an n8n HTTP Request node, a Home Assistant REST sensor or an ESP32 HTTPClient without an SDK.
Be gentle with limits
Devices poll forever, so poll slowly: every few minutes for schedules, faster only while something is live. The free plan covers a desk display that checks a handful of times an hour.
Endpoints used
| GET/ufc/live | Is a fight on, and the current bout |
| GET/cs2/matches/live | Live CS2 matches and scores |
| GET/ufc/events/upcoming | Next card for reminders |
| GET/lol/schedule/today | Today's LoL matches |
Build it on a free key
500 requests a month, every game, no card.
More use cases