[APP] HostTracker

Name of app / service

HostTracker (https://www.host-tracker.com/) - website, server and certificate monitoring from 300+ locations: uptime, SSL, DNS, blacklist and page-speed checks, monitors, alerts, incidents, status pages.

Link to developer documentation

API v2 docs: https://www.host-tracker.com/apidocs/v2
OpenAPI 3.1: https://github.com/HostTracker/openapi (raw: https://raw.githubusercontent.com/HostTracker/openapi/main/openapi-3.1.gen.json)
Auth: per-user API token, sent as Authorization: Bearer ; users mint it at https://www.host-tracker.com/integrations/api with per-family scopes (check, monitor, contact, subs, webhook, statuspage, account). Base URL https://api2.host-tracker.com. No OAuth.
Webhooks: API v2 has signed webhook subscriptions (POST /webhooks, HMAC signature, event catalogue) usable for instant sources.
Suggested app config: api_token (secret) and an optional base_url (defaults to https://api2.host-tracker.com).

Is lack of support preventing you from moving forward, or do you have a workaround?

Workaround today is the generic HTTP action with a bearer header; a first-class app is what HostTracker customers ask for. We are the vendor (HostTracker Ltd) and will maintain the components.

Are there specific actions or triggers you'd like to see for this app?

Ready to submit as a PR once the app exists (7 actions, 4 sources, ESLint-clean, following the components guidelines):

Actions: Run Instant Check, List Monitors, Get Monitor, Create Monitor, Update Monitor, Delete Monitor, List Incidents. Sources: New Monitor Down Event (Instant), New Monitor Up Event (Instant), New Incident Opened (Instant), New Incident (polling).

Start with the components guidelines and HostTracker's API v2 documentation or OpenAPI 3.1 definition. Implement the seven requested actions and four sources using the stated token and base URL configuration; done means the components are ESLint-clean and cover the listed API behaviors.

Written by the indexing model from the issue text.