Height API
Height's project management REST API for creating, reading, and updating tasks, lists, forms, and attributes in Height workspaces. Known for its real-time collaboration model and flexible task structure with custom attributes.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS enforced. OAuth2 provides user-scoped tokens. API keys are full workspace access — no per-key scope restriction. Recommend creating a dedicated service account for agent access. No IP allowlisting documented.
⚡ Reliability
Best When
Your team uses Height and wants a clean, well-documented REST API for agent-driven task automation with real-time webhook support.
Avoid When
You're evaluating new tooling — Height has a smaller community and fewer integrations than Linear or Jira.
Use Cases
- • Creating tasks from agent-detected events (bugs, alerts, support tickets)
- • Querying task lists and status for sprint planning and reporting agents
- • Updating task attributes and statuses as agent workflows progress
- • Automating triage by routing tasks to the right lists based on agent classification
- • Syncing Height tasks with external tools like GitHub or Slack via webhooks
Not For
- • Teams not using Height (low market penetration compared to Jira or Linear)
- • Complex enterprise workflows requiring deep Jira-style customization
- • Agents needing GraphQL (Height is REST-only)
- • High-volume bulk operations (rate limits apply)
Interface
Authentication
Secret API keys available for server-side agent use. OAuth 2.0 available for user-context integrations. API keys are workspace-scoped. OAuth tokens carry user-level permissions. Tokens passed as Authorization: Bearer header.
Pricing
Generous free tier with API access. Small team-friendly pricing. Notably more affordable than Jira for small engineering teams. API included on all plans.
Agent Metadata
Known Gotchas
- ⚠ Task IDs are UUIDs — Height uses readable task numbers in the UI (e.g., HT-123) but the API requires UUID form; must look up ID via search
- ⚠ Custom attributes are workspace-specific and must be discovered via the attributes endpoint before use — no standard schema
- ⚠ Webhook payloads use an action type system (task.created, task.updated, etc.) but update events do not include previous state — diffing requires agents to cache state
- ⚠ List IDs are required for task creation — agents must know the target list UUID, not just name
- ⚠ No official SDK means agents must handle HTTP directly or use community libraries with no support guarantees
- ⚠ Real-time API uses Server-Sent Events (SSE) for live updates — polling is supported but SSE is preferred for event-driven agents
- ⚠ Rate limit errors return 429 with no Retry-After header — agents must implement exponential backoff heuristically
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Height API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.