Profiling Atlassian — 138 APIs Across Three Products

Atlassian carries one of the largest surfaces in the catalog — 138 distinct APIs — and unlike most high-count providers, it isn’t one product fragmented. It’s three: Jira, Confluence, and Bitbucket, each decomposed to the resource level. Walking it is a lesson in what happens when a company catalogs a whole product portfolio instead of a single app.

What’s actually in the surface

The 138 APIs split cleanly along product lines:

Bitbucket (~8 APIs) — Repositories, Pull Requests, Snippets, Workspaces, Teams, Hook Events, Addon, User. The source-and-collaboration surface.
Confluence (~16 APIs) — Content, Content Body, Content States, Space, Search, Label, Template, Relation, Analytics, Audit, Inline Tasks, Long Task. The knowledge-base surface, with content broken down by structural concern.
Jira (~110+ APIs) — the bulk of the count. Issue, Issues, Issue Link, Issue Type, Issue Type Scheme, Field, Field Configuration, Filter, JQL, Dashboard, Project, Permission Scheme, Notification Scheme, Workflow, plus dozens more. Every configurable facet of Jira is its own API.

What’s interesting about the shape

The count is portfolio breadth, not monolith fragmentation. Plaid’s 39 or Stripe’s 57 come from one product splitting by regulatory or operational role. Atlassian’s 138 come from three mature products, each decomposed. It’s a different cause for a similar number — and the catalog makes the distinction visible because each spec carries its product lineage.
Jira’s configurability is the API count. Field configurations, screen schemes, issue-type schemes, permission schemes, notification schemes — Jira is endlessly configurable, and each configuration dimension is a separate surface. The API portfolio is a direct readout of the product’s flexibility.
Confluence splits content from its body. Content and Content Body are separate APIs — structure versus payload. That’s a deliberate modeling choice that makes content programmatically composable.

The takeaway

A hundred thirty-eight APIs across three products is what a developer-collaboration platform looks like when every product is treated as a first-class, fully-decomposed surface. The takeaway for other multi-product vendors: don’t bury Bitbucket inside one giant “Atlassian API.” Keep the product lineage in the contract, and the catalog — and your users — can navigate it. Walk the full surface on the Atlassian provider page.