asyncapi/spec

The AsyncAPI specification allows you to create machine-readable definitions of your asynchronous APIs.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 12th, 2026
Created on November 18th, 2016
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 382
Total Stargazers: 5,304 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.5 hours
Mean response time: 28.1 days
90th percentile: 68.8 days
Tracked items: 78

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 77% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "🐞 Bug" is answered fastest, typically in about 7 hours, while "❔ Question" waits about 9 days. Only 2% of issues opened in the past year have been closed. Three people close 69% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 35
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 595 days
Stale 30+ days: 33
Stale 90+ days: 30

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (39)
  • ❔ Question (24)
  • 🐞 Bug (15)
  • 💡 Proposal (RFC 1) (15)
  • 💭 Strawman (RFC 0) (10)
  • keep-open (9)
  • good first issue (3)
  • released (3)

Detailed Description

AsyncAPI is a specification for creating machine-readable definitions of asynchronous APIs. It provides a standardized way to document APIs that communicate through asynchronous protocols and messaging systems, enabling tooling and automation around event-driven architectures.

The specification solves the problem of documenting asynchronous communication patterns in a structured, machine-readable format. Rather than relying on informal documentation, AsyncAPI allows developers to define the channels, messages, and protocols used in asynchronous systems in a way that tools can parse and validate. The approach works by defining a markdown-based specification that serves as the source of truth, with corresponding JSON Schema files available for validation and tooling integration.

Teams building event-driven systems that use protocols like Kafka, AMQP, MQTT, WebSockets, or STOMP should consider adopting this specification. It suits projects where multiple services communicate asynchronously and where clear documentation of message contracts is valuable. The specification maintains backward compatibility across versions while evolving to support new use cases, with multiple stable versions available for different adoption timelines.

The project maintains an active specification with regular updates and a structured versioning approach. The specification is developed openly with a contributor's guide and examples provided to support adoption. The project has established sponsorship relationships with organizations across the event-driven architecture and API management space, indicating sustained backing and real-world usage.