Huly Tracker

Tracker is Huly's project and issue management module (subtasks, milestones, templates, custom workflows) with optional two-way GitHub Issues/Projects sync. Issues, projects, and related objects are accessed programmatically as platform documents through the Huly Platform SDK rather than via a dedicated public REST API.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/huly-tracker"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

huly-openapi.yml Raw ↑
openapi: 3.0.1
info:
  title: Huly Platform API
  description: >-
    Huly is an open-source, all-in-one project management and team collaboration
    platform. Programmatic access is provided primarily through the Node.js SDK
    @hcengineering/api-client, which connects to the Huly Platform transactor
    over a persistent WebSocket connection (connect) or via a REST client
    (connectRest), authenticating with email/password or a token. The SDK
    exposes document-oriented operations (findOne, findAll, createDoc,
    updateDoc, removeDoc, addCollection, updateCollection, removeCollection,
    createMixin, updateMixin) over the platform data model rather than a set of
    fixed, publicly documented REST resource paths.

    As of this writing, Huly does not publish a stable, public HTTP REST API
    with documented endpoint paths and request/response schemas. The platform's
    HTTP/WebSocket transports (account service and transactor) are
    self-hosted-configurable and intended to be consumed through the official
    SDK. To avoid fabricating endpoints, this document intentionally declares
    no paths. See the Huly API client documentation and examples for the
    supported, SDK-based interface.
  termsOfService: https://huly.io/
  contact:
    name: Huly (Hardcore Engineering)
    url: https://huly.io/
  license:
    name: Eclipse Public License 2.0
    url: https://www.eclipse.org/legal/epl-2.0/
  version: '1.0'
externalDocs:
  description: Huly API client (@hcengineering/api-client) documentation
  url: https://github.com/hcengineering/huly.core/blob/main/packages/api-client/README.md
servers:
  - url: https://huly.io
    description: >-
      Huly Cloud landing surface. The actual programmatic surface is the
      account service and transactor of a given Huly deployment (for example
      wss://<host>/transactor and https://<host>/account in self-hosted
      configurations), consumed via the official SDK rather than fixed
      public REST paths.
paths: {}