Issues

An index and topic collection covering issue tracking, bug tracking, and project-management APIs that expose issue, ticket, task, and work-item primitives. Issue tracking APIs are the connective tissue between engineering, product, and operations work — they capture defects, feature requests, user stories, and tasks, then move them through configurable workflows from creation to resolution. This collection includes developer-centric trackers like Jira, Linear, GitHub Issues, and GitLab Issues; project- and work-management platforms like Asana, ClickUp, Monday.com, Trello, and Wrike; product-discovery trackers like Productboard and Shortcut; classic open-source bug trackers like Redmine; and flexible work-item stores like Notion, Airtable, and Smartsheet. It is distinct from the customer-support topic (Zendesk-style help desks) and from incident management (which lives under monitoring).

Issues is profiled on the APIs.io network. Tagged areas include Issue Tracking, Bug Tracking, Project Management, Task Management, and Work Management.

The Issues catalog on APIs.io includes 1 JSON-LD context.

Issues’ developer surface includes developer portal and 1 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

9.6/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

0 APIs 8 Features 7 Use Cases

Issue Tracking Bug Tracking Project Management Task Management Work Management

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 9.6/100 · minimal

Contract Quality 3.1 / 21

Developer Ergonomics 1.6 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.6 / 11

Contract Governance 0.0 / 10

Discoverability 4.1 / 9

Regulatory Posture 0.7 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/issues: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Features 8

Notable capabilities this provider offers.

Issue and Ticket Primitives

Issue tracking APIs expose a core issue/ticket primitive with identifier, title, description, status, assignee, reporter, priority, and timestamps as the unit of work that flows...

Configurable Workflows and Transitions

Trackers like Jira, Linear, and Azure DevOps model state machines on top of issues — open, in-progress, in-review, done — and expose transition APIs that move work between state...

Labels, Components, and Custom Fields

Issue APIs let teams classify work using labels, tags, components, fix versions, epics, and arbitrary custom fields, which are first-class resources that can be created, listed,...

Comments and Activity Streams

Issues accumulate conversation and history. Most trackers expose comments as a separate resource and provide an audit-style activity stream covering field changes, transitions, ...

Sprints, Boards, and Backlogs

Agile-oriented APIs (Jira Agile, Linear, Shortcut, Azure Boards) expose sprints, iterations, kanban boards, and backlogs as objects you can query and mutate alongside the underl...

Webhooks and Event Subscriptions

Issue trackers publish events (created, updated, transitioned, commented) over webhooks so external automations, chatops bots, CI systems, and AI agents can react to work-item c...

Search, JQL, and Saved Queries

Trackers expose query languages or filter parameters (Jira's JQL, GitHub's search syntax, Linear's filter API) for finding issues by status, assignee, label, sprint, or arbitrar...

Attachments and Linked Resources

Issues support file attachments and relationships to other issues (blocks, blocked-by, duplicates, relates-to) and to external artifacts like commits, pull requests, deploys, an...

Scroll for all 8

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Issues Context

10 classes · 16 properties

JSON-LD

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

Comment

10 properties

JSON SCHEMA

Issue

15 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Issues Comment Structure

10 properties

JSON STRUCTURE

Issues Issue Structure

15 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

Issues Comment Example

10 fields

EXAMPLE

Issues Issue Example

15 fields

EXAMPLE

Use Cases 7

What developers build with this provider.

Engineering Issue Tracking

Software teams use Jira, Linear, GitHub Issues, or GitLab Issues as the system of record for bugs, stories, and tasks, with API integrations into IDEs, CI/CD pipelines, and code...

Cross-Team Work Coordination

Work-management platforms like Asana, ClickUp, Monday.com, and Wrike coordinate tasks across engineering, marketing, design, and operations, often syncing with developer tracker...

Product Roadmap and Discovery

Productboard, Shortcut, and Linear connect customer feedback and product opportunities to issues and roadmap items, exposing APIs for ingesting feedback and synchronizing with e...

ChatOps and Bot Automation

Slack, Microsoft Teams, and Discord bots create, update, transition, and comment on issues using tracker APIs — turning chat messages into tickets and pushing status updates bac...

AI Agent Triage and Routing

AI agents use issue tracker APIs to classify incoming issues, suggest labels and assignees, summarize threads, draft replies, link related tickets, and propose status transition...

Reporting, Dashboards, and Analytics

BI tools and dashboards pull cycle time, throughput, lead time, and backlog metrics from issue tracker APIs to measure engineering productivity and project health.

Internal Developer Portals

Backstage, Compass, and other internal developer portals embed issue tracker data alongside services, deployments, and ownership so teams see open issues for the components they...

Scroll for all 7

Integrations 8

Pre-built integrations with other platforms and tools.

Jira

Atlassian's market-leading issue and project tracker for software teams, with a deep REST API covering issues, projects, sprints, JQL search, custom fields, and webhooks.

Linear

Modern, opinionated issue tracker for high-velocity software teams, with a first-class GraphQL API for issues, cycles, projects, and roadmaps.

GitHub Issues

Lightweight tracker built into GitHub repositories, accessible through the GitHub REST and GraphQL APIs alongside pull requests, commits, and Actions.

GitLab Issues

Issue tracker tightly integrated with GitLab repositories, CI/CD, and merge requests, exposed via the GitLab REST and GraphQL APIs.

Asana

Work-management platform with tasks, projects, sections, and custom fields, exposed via the Asana REST API and frequently used as a cross-functional issue tracker.

ClickUp

All-in-one work-management platform with tasks, lists, spaces, and views, accessible through the ClickUp REST API.

Monday.com

Visual work-management platform with boards, items, and columns, accessible through the Monday GraphQL API and widely used as a task and issue tracker.

Azure DevOps

Microsoft's developer platform whose Boards service provides work-item tracking (bugs, user stories, tasks, epics) via the Azure DevOps REST API.

Scroll for all 8

Resources

Get Started 1

Portal, sign-up, and the first successful call

Portal

Portal

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Source (apis.yml)

aid: issues
name: Issues
description: An index and topic collection covering issue tracking, bug tracking, and project-management APIs that expose
  issue, ticket, task, and work-item primitives. Issue tracking APIs are the connective tissue between engineering, product,
  and operations work — they capture defects, feature requests, user stories, and tasks, then move them through configurable
  workflows from creation to resolution. This collection includes developer-centric trackers like Jira, Linear, GitHub Issues,
  and GitLab Issues; project- and work-management platforms like Asana, ClickUp, Monday.com, Trello, and Wrike; product-discovery
  trackers like Productboard and Shortcut; classic open-source bug trackers like Redmine; and flexible work-item stores like
  Notion, Airtable, and Smartsheet. It is distinct from the customer-support topic (Zendesk-style help desks) and from incident
  management (which lives under monitoring).
type: Index
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Issue Tracking
- Bug Tracking
- Project Management
- Task Management
- Work Management
url: https://raw.githubusercontent.com/api-evangelist/issues/refs/heads/main/apis.yml
created: '2026-05-19'
modified: '2026-05-19'
specificationVersion: '0.19'
apis: []
network:
- name: Airtable
  url: https://raw.githubusercontent.com/api-evangelist/airtable/refs/heads/main/apis.yml
- name: Asana
  url: https://raw.githubusercontent.com/api-evangelist/asana/refs/heads/main/apis.yml
- name: Atlassian
  url: https://raw.githubusercontent.com/api-evangelist/atlassian/refs/heads/main/apis.yml
- name: Atlassian Compass
  url: https://raw.githubusercontent.com/api-evangelist/atlassian-compass/refs/heads/main/apis.yml
- name: Atlassian Jira
  url: https://raw.githubusercontent.com/api-evangelist/atlassian-jira/refs/heads/main/apis.yml
- name: Azure DevOps
  url: https://raw.githubusercontent.com/api-evangelist/azure-devops/refs/heads/main/apis.yml
- name: Basecamp
  url: https://raw.githubusercontent.com/api-evangelist/basecamp/refs/heads/main/apis.yml
- name: Bitbucket
  url: https://raw.githubusercontent.com/api-evangelist/bitbucket/refs/heads/main/apis.yml
- name: ClickUp
  url: https://raw.githubusercontent.com/api-evangelist/clickup/refs/heads/main/apis.yml
- name: Gitea
  url: https://raw.githubusercontent.com/api-evangelist/gitea/refs/heads/main/apis.yml
- name: GitHub
  url: https://raw.githubusercontent.com/api-evangelist/github/refs/heads/main/apis.yml
- name: GitLab
  url: https://raw.githubusercontent.com/api-evangelist/gitlab/refs/heads/main/apis.yml
- name: Hive
  url: https://raw.githubusercontent.com/api-evangelist/hive/refs/heads/main/apis.yml
- name: Jira
  url: https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/apis.yml
- name: Linear
  url: https://raw.githubusercontent.com/api-evangelist/linear/refs/heads/main/apis.yml
- name: Microsoft Project
  url: https://raw.githubusercontent.com/api-evangelist/microsoft-project/refs/heads/main/apis.yml
- name: Monday.com
  url: https://raw.githubusercontent.com/api-evangelist/monday-com/refs/heads/main/apis.yml
- name: Notion
  url: https://raw.githubusercontent.com/api-evangelist/notion/refs/heads/main/apis.yml
- name: Productboard
  url: https://raw.githubusercontent.com/api-evangelist/productboard/refs/heads/main/apis.yml
- name: Redmine
  url: https://raw.githubusercontent.com/api-evangelist/redmine/refs/heads/main/apis.yml
- name: Shortcut
  url: https://raw.githubusercontent.com/api-evangelist/shortcut/refs/heads/main/apis.yml
- name: Smartsheet
  url: https://raw.githubusercontent.com/api-evangelist/smartsheet/refs/heads/main/apis.yml
- name: Teamwork
  url: https://raw.githubusercontent.com/api-evangelist/teamwork/refs/heads/main/apis.yml
- name: Trello
  url: https://raw.githubusercontent.com/api-evangelist/trello/refs/heads/main/apis.yml
- name: Wrike
  url: https://raw.githubusercontent.com/api-evangelist/wrike/refs/heads/main/apis.yml
- name: Zoho
  url: https://raw.githubusercontent.com/api-evangelist/zoho/refs/heads/main/apis.yml
common:
- type: Portal
  url: https://apievangelist.com
- type: GitHubOrganization
  url: https://github.com/api-evangelist
- type: Features
  data:
  - name: Issue and Ticket Primitives
    description: Issue tracking APIs expose a core issue/ticket primitive with identifier, title, description, status, assignee,
      reporter, priority, and timestamps as the unit of work that flows through development and project workflows.
  - name: Configurable Workflows and Transitions
    description: Trackers like Jira, Linear, and Azure DevOps model state machines on top of issues — open, in-progress, in-review,
      done — and expose transition APIs that move work between states with optional validations and side effects.
  - name: Labels, Components, and Custom Fields
    description: Issue APIs let teams classify work using labels, tags, components, fix versions, epics, and arbitrary custom
      fields, which are first-class resources that can be created, listed, and assigned via the API.
  - name: Comments and Activity Streams
    description: Issues accumulate conversation and history. Most trackers expose comments as a separate resource and provide
      an audit-style activity stream covering field changes, transitions, and attachments.
  - name: Sprints, Boards, and Backlogs
    description: Agile-oriented APIs (Jira Agile, Linear, Shortcut, Azure Boards) expose sprints, iterations, kanban boards,
      and backlogs as objects you can query and mutate alongside the underlying issues.
  - name: Webhooks and Event Subscriptions
    description: Issue trackers publish events (created, updated, transitioned, commented) over webhooks so external automations,
      chatops bots, CI systems, and AI agents can react to work-item changes in near real time.
  - name: Search, JQL, and Saved Queries
    description: Trackers expose query languages or filter parameters (Jira's JQL, GitHub's search syntax, Linear's filter
      API) for finding issues by status, assignee, label, sprint, or arbitrary custom-field combinations.
  - name: Attachments and Linked Resources
    description: Issues support file attachments and relationships to other issues (blocks, blocked-by, duplicates, relates-to)
      and to external artifacts like commits, pull requests, deploys, and design files.
- type: UseCases
  data:
  - name: Engineering Issue Tracking
    description: Software teams use Jira, Linear, GitHub Issues, or GitLab Issues as the system of record for bugs, stories,
      and tasks, with API integrations into IDEs, CI/CD pipelines, and code review tools.
  - name: Cross-Team Work Coordination
    description: Work-management platforms like Asana, ClickUp, Monday.com, and Wrike coordinate tasks across engineering,
      marketing, design, and operations, often syncing with developer trackers via API.
  - name: Product Roadmap and Discovery
    description: Productboard, Shortcut, and Linear connect customer feedback and product opportunities to issues and roadmap
      items, exposing APIs for ingesting feedback and synchronizing with engineering work.
  - name: ChatOps and Bot Automation
    description: Slack, Microsoft Teams, and Discord bots create, update, transition, and comment on issues using tracker
      APIs — turning chat messages into tickets and pushing status updates back into channels.
  - name: AI Agent Triage and Routing
    description: AI agents use issue tracker APIs to classify incoming issues, suggest labels and assignees, summarize threads,
      draft replies, link related tickets, and propose status transitions for human review.
  - name: Reporting, Dashboards, and Analytics
    description: BI tools and dashboards pull cycle time, throughput, lead time, and backlog metrics from issue tracker APIs
      to measure engineering productivity and project health.
  - name: Internal Developer Portals
    description: Backstage, Compass, and other internal developer portals embed issue tracker data alongside services, deployments,
      and ownership so teams see open issues for the components they own.
- type: Integrations
  data:
  - name: Jira
    description: Atlassian's market-leading issue and project tracker for software teams, with a deep REST API covering issues,
      projects, sprints, JQL search, custom fields, and webhooks.
  - name: Linear
    description: Modern, opinionated issue tracker for high-velocity software teams, with a first-class GraphQL API for issues,
      cycles, projects, and roadmaps.
  - name: GitHub Issues
    description: Lightweight tracker built into GitHub repositories, accessible through the GitHub REST and GraphQL APIs alongside
      pull requests, commits, and Actions.
  - name: GitLab Issues
    description: Issue tracker tightly integrated with GitLab repositories, CI/CD, and merge requests, exposed via the GitLab
      REST and GraphQL APIs.
  - name: Asana
    description: Work-management platform with tasks, projects, sections, and custom fields, exposed via the Asana REST API
      and frequently used as a cross-functional issue tracker.
  - name: ClickUp
    description: All-in-one work-management platform with tasks, lists, spaces, and views, accessible through the ClickUp
      REST API.
  - name: Monday.com
    description: Visual work-management platform with boards, items, and columns, accessible through the Monday GraphQL API
      and widely used as a task and issue tracker.
  - name: Azure DevOps
    description: Microsoft's developer platform whose Boards service provides work-item tracking (bugs, user stories, tasks,
      epics) via the Azure DevOps REST API.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
humanURL: https://apievangelist.com

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/issues"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/issues/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/issues/evidence"

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.

GitHub Google LinkedIn

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