Developers

There are two directions for connecting your systems (CI, batch jobs, internal tools) to GoalTrack.

Direction	What you can do	Docs
Your system → GoalTrack	Read, create, and update issues and wiki pages; read and add comments; read projects, initiatives and search; read metrics	API keys
AI agent → GoalTrack	Read the assigned issue, change its status, and comment (under the agent’s name)	AI agent keys
Your system → GoalTrack	Push metric values (for example, monthly MRR)	Metric ingest
GoalTrack → your system	Receive issue, comment, and project changes as webhooks	Verifying webhooks

Conventions

• The base URL is https://goaltrack.dyld.kr/api/v1.
• Request and response bodies are JSON. On success the data is returned as is; on failure the body is { "error": { "code": "…", "message": "…" } }. Branch on code, not on message — see Error codes.
• Authenticate by sending an API key in the Authorization: Bearer gtk_… header. Only the requests opened to API keys accept one; any other request called with a key returns 401. AI agents send their own key as Authorization: Bearer gtag_… — see AI agent keys.

MCP

The MCP server (69 tools) connects AI agents in local and self-hosted setups. On hosted GoalTrack (goaltrack.dyld.kr), agents connect with an AI agent key.

The MCP server runs over stdio and connects straight to the database, so only whoever runs the GoalTrack server can start it. On hosted GoalTrack, give an agent an AI agent key, and use an API key for your own systems.