HipChat website screenshot

HipChat

HipChat was Atlassian's team chat platform, providing persistent group chat, video, file sharing, and an extensive integration ecosystem. Atlassian discontinued HipChat Cloud, Stride, HipChat Server, and HipChat Data Center on February 15, 2019 after selling the IP to Slack in July 2018 and committing to a joint migration path for customers. This profile preserves the historical API surface (REST API v2, Webhooks, Connect add-on framework) for archival and migration-pattern research; no live endpoints remain.

HipChat publishes 2 APIs on the APIs.io network: REST API v2 and Webhooks API. Tagged areas include Chat, Messaging, Collaboration, Team Communication, and Sunset.

The HipChat catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 3 Spectral governance rulesets.

HipChat’s developer surface includes documentation, engineering blog, pricing, and 9 more developer resources.

51.3/100 developing ▬ flat Agent 19/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessPaid
2 APIs
ChatMessagingCollaborationTeam CommunicationSunsetHistoricalAtlassianWebhook

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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.
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/hipchat: 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 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

HipChat REST API v2

The HipChat REST API v2 was the primary developer surface for the team chat platform, exposing rooms, users, messages, notifications, emoticons, OAuth sessions, add-on capabilit...

HipChat Webhooks API

Event-driven webhook delivery from HipChat rooms. Webhooks could be registered via the REST API or declared in an add-on descriptor. Each delivery included a JWT-signed signed_r...

Pricing Plans 1

Published pricing tiers and plan structures.

Hipchat Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Hipchat Rate Limits

2 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

HipChat Webhooks API

Event-driven webhook deliveries from Atlassian's discontinued HipChat platform. Every webhook POST included a `signed_request` query parameter containing a JWT that the receiver...

ASYNCAPI

Semantic Vocabularies 1

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

Hipchat Context

27 classes · 12 properties

JSON-LD

Spectral Rules 3

Spectral governance rulesets for linting and validating these APIs.

HipChat API Rules

6 rules · 1 errors 5 warnings

SPECTRAL

HipChat API Rules

5 rules · 4 warnings 1 info

SPECTRAL

HipChat API Rules

9 rules · 3 errors 4 warnings 2 info

SPECTRAL

JSON Schema 4

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

HipChat Message

10 properties

JSON SCHEMA

HipChat Room

13 properties

JSON SCHEMA

HipChat User

15 properties

JSON SCHEMA

HipChat Webhook

7 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Hipchat Message Structure

8 properties

JSON STRUCTURE

Hipchat Room Structure

11 properties

JSON STRUCTURE

Examples 4

Example request and response payloads for these APIs.

Hipchat Room Example

13 fields

EXAMPLE

Hipchat User Example

15 fields

EXAMPLE

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hipchat Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Hipchat Vulnerability Disclosure

security.txt · contact published

SECURITY

Hipchat Trust Center

FedRAMP

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: hipchat
url: https://raw.githubusercontent.com/api-evangelist/hipchat/refs/heads/main/apis.yml
name: HipChat
description: HipChat was Atlassian's team chat platform, providing persistent group chat, video, file sharing, and an extensive
  integration ecosystem. Atlassian discontinued HipChat Cloud, Stride, HipChat Server, and HipChat Data Center on February
  15, 2019 after selling the IP to Slack in July 2018 and committing to a joint migration path for customers. This profile
  preserves the historical API surface (REST API v2, Webhooks, Connect add-on framework) for archival and migration-pattern
  research; no live endpoints remain.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hipchat.png
created: 2024-01-01 00:00:00+00:00
modified: '2026-05-23'
specificationVersion: '0.23'
scoreLabel: SUNSET
lifecycle: discontinued
deprecated: true
deprecatedReason: HipChat has been discontinued. Retained for historical reference.
tags:
- Chat
- Messaging
- Collaboration
- Team Communication
- Sunset
- Historical
- Atlassian
- Webhook
tags_raw:
- Chat
- Messaging
- Collaboration
- Team Communication
- Sunset
- Historical
- Atlassian
- Webhooks
apis:
- name: HipChat REST API v2
  description: The HipChat REST API v2 was the primary developer surface for the team chat platform, exposing rooms, users,
    messages, notifications, emoticons, OAuth sessions, add-on capabilities, and webhook management. Authentication supported
    four token types (add-on tokens, user tokens, personal access tokens, and room notification tokens) passed as either an
    auth_token query parameter or an Authorization Bearer header. The API was retired on February 15, 2019 alongside the rest
    of the HipChat product line.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  baseUrl: https://api.hipchat.com/v2
  humanURL: https://developer.atlassian.com/server/hipchat/about-the-hipchat-rest-api/
  tags:
  - Chat
  - Rooms
  - Message
  - User
  - Notification
  - Webhook
  - Authentication
  - Sunset
  tags_raw:
  - Chat
  - Rooms
  - Messages
  - Users
  - Notifications
  - Webhooks
  - OAuth
  - Sunset
  properties:
  - type: Documentation
    url: https://developer.atlassian.com/server/hipchat/about-the-hipchat-rest-api/
  - type: APIReference
    url: https://www.hipchat.com/docs/apiv2
    title: Original API Reference (offline; archive.org snapshots)
  - type: OpenAPI
    url: openapi/hipchat-rest-api-openapi.yml
  - type: Authentication
    url: https://developer.atlassian.com/server/hipchat/auth/
  - type: RateLimits
    url: https://developer.atlassian.com/server/hipchat/hipchat-rest-api-rate-limits/
  - type: RateLimits
    url: rate-limits/hipchat-rate-limits.yml
  - type: Security
    url: https://developer.atlassian.com/server/hipchat/hipchat-rest-api-scopes/
    title: OAuth Scopes
  - type: GettingStarted
    url: https://developer.atlassian.com/server/hipchat/getting-started-with-atlassian-connect-for-hipchat/
  - type: SDKs
    url: https://github.com/hipchat/hipchat-php
    title: hipchat-php — Official PHP wrapper
  - type: SDKs
    url: https://github.com/hipchat/hipchat-rb
    title: hipchat-rb — Official Ruby wrapper with Capistrano hooks
  - type: SDKs
    url: https://github.com/hipchat/hubot-hipchat
    title: hubot-hipchat — HipChat adapter for GitHub's Hubot
  - type: CLI
    url: https://github.com/hipchat/hipchat-cli
    title: hipchat-cli — Shell scripts wrapping the REST API
  - type: Integrations
    url: https://github.com/hipchat/redmine_hipchat
    title: Redmine plugin for room notifications
  - type: Integrations
    url: https://github.com/hipchat/triatomic
    title: Starter Hubot configuration for Heroku
  - type: GitHubOrganization
    url: https://github.com/hipchat
  - type: JSONSchema
    url: json-schema/hipchat-room-schema.json
  - type: JSONSchema
    url: json-schema/hipchat-user-schema.json
  - type: JSONSchema
    url: json-schema/hipchat-message-schema.json
  - type: JSONSchema
    url: json-schema/hipchat-webhook-schema.json
  - type: JSONLD
    url: json-ld/hipchat-context.jsonld
  - type: Versioning
    url: https://developer.atlassian.com/server/hipchat/hipchat-connect-versioning/
  - type: Sunset
    url: https://www.atlassian.com/blog/announcements/new-atlassian-slack-partnership
    title: 'Sunset announcement: HipChat & Stride discontinued; IP sold to Slack (July 26, 2018)'
  - type: Sunset
    url: https://www.atlassian.com/migration/move-from-hipchat-to-slack
    title: 'End-of-life: February 15, 2019 — official migration to Slack'
  contact:
  - type: Support
    url: https://www.atlassian.com/migration/move-from-hipchat-to-slack
    title: Migration support (post-sunset)
- name: HipChat Webhooks API
  description: Event-driven webhook delivery from HipChat rooms. Webhooks could be registered via the REST API or declared
    in an add-on descriptor. Each delivery included a JWT-signed signed_request query parameter that the receiving service
    was expected to verify. The room_message event was the primary integration pattern, with additional events covering room
    enter, exit, topic change, archive, notification, and file upload. The webhook surface was retired with the rest of HipChat
    on February 15, 2019.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  baseUrl: https://api.hipchat.com/v2/room/{id_or_name}/webhook
  humanURL: https://developer.atlassian.com/server/hipchat/webhooks/
  tags:
  - Webhook
  - Event
  - Chat
  - Sunset
  tags_raw:
  - Webhooks
  - Events
  - Chat
  - Sunset
  properties:
  - type: Documentation
    url: https://developer.atlassian.com/server/hipchat/webhooks/
  - type: AsyncAPI
    url: asyncapi/hipchat-webhooks-asyncapi.yml
  - type: Authentication
    url: https://developer.atlassian.com/server/hipchat/understanding-jwt-for-apps/
    title: JWT verification of signed_request
  - type: JSONSchema
    url: json-schema/hipchat-webhook-schema.json
  - type: Sunset
    url: https://www.atlassian.com/migration/move-from-hipchat-to-slack
common:
- type: Website
  url: https://www.atlassian.com/
- type: TrustCenter
  url: security/hipchat-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/hipchat-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/hipchat-domain-security.yml
- type: Documentation
  url: https://developer.atlassian.com/server/hipchat/
- type: DeveloperPortal
  url: https://developer.atlassian.com/server/hipchat/
- type: GitHubOrganization
  url: https://github.com/hipchat
- type: Blog
  url: https://www.atlassian.com/blog/announcements/new-atlassian-slack-partnership
  title: Atlassian-Slack partnership announcement (July 26, 2018)
- type: Sunset
  url: https://www.atlassian.com/migration/move-from-hipchat-to-slack
  title: HipChat → Slack migration (sunset February 15, 2019)
- type: Integrations
  url: https://www.atlassian.com/partnerships/slack
  title: Atlassian + Slack partnership
- type: Pricing
  url: plans/hipchat-plans-pricing.yml
  title: Historical pricing (no longer in market)
- type: RateLimits
  url: rate-limits/hipchat-rate-limits.yml
- type: FinOps
  url: finops/hipchat-finops.yml
  title: Historical FinOps record (no longer billable)
maintainers:
- FN: API Evangelist
  email: info@apievangelist.com
  url: 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/hipchat"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hipchat/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hipchat/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.

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