IDE

An index and topic collection covering integrated development environments (IDEs), code editors, and cloud workspaces with APIs. This topic captures the editors, IDEs, and developer workspaces that expose programmable surfaces, including local desktop IDEs (Visual Studio, JetBrains IDEs, Eclipse), modern AI-first editors (Cursor, Windsurf), agentic coding assistants (Aider, Cline, Continue, GitHub Copilot, Amazon Q Developer, Tabnine), notebook environments (Jupyter, JupyterLab, JupyterHub, Google Colab), cloud development platforms (Replit), plugin marketplaces (JetBrains Marketplace), and editor extension APIs (Visual Studio Code). IDEs and editor-as-API platforms expose extension APIs, Language Server Protocol (LSP) endpoints, workspace and project APIs, debugging APIs, plugin marketplaces, telemetry, completion and chat APIs, and remote workspace orchestration. This collection is distinct from API client tooling (HTTP request testing) and focuses on the surface where developers write, edit, debug, and run code.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

How we profile IDE

Each block below is one kind of artifact we hold for IDE. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Features 8

The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.

Notable capabilities this provider offers.

Extension and Plugin APIs

IDEs expose extension APIs that let third-party developers add commands, views, language support, debuggers, and integrations. Examples include the VS Code Extension API, JetBra...

Language Server Protocol (LSP)

LSP is a JSON-RPC protocol that standardizes how editors communicate with language tooling (completion, hover, diagnostics, references). It is the backbone of polyglot editor su...

Workspace and Project APIs

Editors expose workspace, project, and file-system APIs that extensions and remote clients use to read, write, and watch source files, including multi-root workspaces and remote...

AI Completion and Chat APIs

Modern editors and assistants (GitHub Copilot, Cursor, Windsurf, Tabnine, Continue, Cline, Aider, Amazon Q Developer) expose inline completion, chat, and agentic edit APIs that ...

Plugin and Extension Marketplaces

Marketplaces like the VS Code Marketplace and JetBrains Marketplace host millions of extensions and expose APIs for publishing, searching, and managing plugin metadata, download...

Notebook and Kernel APIs

Jupyter and JupyterLab expose REST APIs and a WebSocket-based messaging protocol for managing kernels, sessions, contents, and terminals, powering notebook computing in Colab, J...

Cloud Workspaces and Remote Development

Cloud-based IDEs like Replit and remote-development backends provide APIs for provisioning ephemeral workspaces, managing containers, and streaming editor sessions to browsers.

Debugger and Test Adapter Protocols

Standards like the Debug Adapter Protocol (DAP) and Test Adapter Protocol let editors integrate with debuggers and test runners across many languages through a single, portable ...

Scroll within the panel for all 8 ·

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

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

Ide Context

8 classes · 21 properties

JSON-LD

JSON Schema 2

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

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

Extension

14 properties

JSON SCHEMA

Workspace

10 properties

JSON SCHEMA

JSON Structure 2

JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.

JSON Structure definitions describing this provider's data shapes.

Ide Extension Structure

14 properties

JSON STRUCTURE

Ide Workspace Structure

10 properties

JSON STRUCTURE

Examples 2

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Ide Extension Example

14 fields

EXAMPLE

Ide Workspace Example

10 fields

EXAMPLE

Use Cases 7

What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.

What developers build with this provider.

Building AI Coding Assistants

Developers integrate LLM-backed completion and agentic editing into IDEs through extension APIs and editor-side hooks, powering products like Copilot, Cursor, Windsurf, Continue...

Custom Internal Developer Tooling

Engineering platform teams build internal extensions for VS Code, JetBrains, and Eclipse to embed company-specific scaffolding, deployment, and code-review tooling directly into...

Notebook-Driven Data Science Workflows

Data teams use Jupyter, JupyterLab, JupyterHub, and Google Colab APIs to automate notebook execution, manage shared kernels, provision multi-user environments, and integrate wit...

Cloud-Native Onboarding and Ephemeral Environments

Platforms like Replit and remote workspace backends use APIs to spin up pre-configured cloud IDEs for tutorials, interviews, and short-lived development environments without loc...

Plugin Distribution and Marketplace Automation

ISVs publish, version, and analyze extensions via the JetBrains Marketplace and Visual Studio Marketplace APIs, integrating release pipelines and revenue reporting into CI/CD.

Game and Real-Time Editor Tooling

Engines like Unity expose editor APIs and packages that integrate live services (multiplayer, analytics, build, asset management) directly into the editor used by game developers.

Standardized Language Tooling Across Editors

Tooling authors implement Language Server Protocol once and expose features (completion, navigation, diagnostics) across every LSP-capable editor, reducing per-IDE integration c...

Scroll within the panel for all 7 ·

Integrations 8

Pre-built integrations with other platforms tell you where this provider already fits in a stack.

Pre-built integrations with other platforms and tools.

Visual Studio Code

The dominant open-source code editor with the VS Code Extension API, Language Server Protocol implementation, Debug Adapter Protocol, and a marketplace of 60,000+ extensions.

JetBrains IDEs

A family of professional IDEs (IntelliJ IDEA, PyCharm, GoLand, WebStorm, PhpStorm, RubyMine, Rider) built on the JetBrains Platform SDK with a unified plugin model and marketplace.

Cursor

AI-first code editor forked from VS Code with deep agentic editing, codebase-aware chat, and tab-driven inline completion.

Windsurf

AI-native editor (formerly Codeium) featuring Cascade autonomous agent, multi-step planning, and enterprise APIs for completion analytics and team management.

GitHub Copilot

AI pair programmer integrated into VS Code, Visual Studio, JetBrains, Neovim, and the GitHub web UI, with Copilot Chat and agent APIs.

Jupyter / JupyterLab

Interactive computing platform exposing REST APIs and a WebSocket messaging protocol for kernels, sessions, contents, and terminals across notebook, JupyterLab, and JupyterHub d...

Replit

Cloud development platform offering instant containerized workspaces, multiplayer editing, an integrated terminal, and APIs for managing Repls and deployments.

Eclipse Foundation

Open-source community behind the Eclipse IDE, Eclipse Theia, Eclipse Che, and a wide ecosystem of editor and language tooling projects.

Scroll within the panel for all 8 ·

Resources

Every other property we hold for IDE — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

← All providers · Data indexed from github.com/api-evangelist/ide · machine-readable index on apis.io