Skip to content
CloudEvents Specification
Shell Makefile
Branch: master
Clone or download
duglin Merge pull request #550 from jagregory/patch-1
Update Distributed Tracing extension spec links
Latest commit 03a10f6 Dec 2, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
adapters Merge pull request #541 from duglin/makev1 Oct 24, 2019
artwork Fix bad hrefs for our images (#424) Apr 28, 2019
community adding contrib entry Oct 16, 2019
extensions Update Distributed Tracing extension spec links Dec 2, 2019
share Ran command on all markdown. (#411) Mar 28, 2019
tools fix issue with filenames starting with http May 29, 2018
.gitignore add artwork (#297) Aug 30, 2018
.travis.yml add ref to RFC2119 and href checker Jan 7, 2018 Ran command on all markdown. (#411) Mar 28, 2019 run the linter Oct 17, 2019
LICENSE Adding Copyright date and owners (#113) Mar 14, 2018
Makefile if 521 and 529 go in, then rename for consistency Oct 15, 2019
OWNERS Make OWNERS point to the spreadsheet for our list of 'approvers' Sep 21, 2018 Add Ruby SDK to SDK lists Nov 14, 2019 Add Ruby SDK to SDK lists Nov 14, 2019 run the linter Oct 17, 2019 v1.0 Oct 17, 2019 v1.0 Oct 17, 2019 run the linter Oct 17, 2019 v1.0 Oct 17, 2019 v1.0 Oct 17, 2019 v1.0 Oct 17, 2019 v1.0 Oct 17, 2019 v1.0 Oct 17, 2019 v1.0 Oct 17, 2019 Fix typo Nov 27, 2019 Update to title format. (#447) Jun 12, 2019 v1.0 Oct 17, 2019
source-event-action.png First pass at a primer Jun 29, 2018
spec.avsc v1.0 Oct 17, 2019
spec.json remove dataencoding and intro data_base64 in JSON (#492) Sep 5, 2019 Fix typo Oct 28, 2019


CloudEvents logo

Events are everywhere. However, event producers tend to describe events differently.

The lack of a common way of describing events means developers must constantly re-learn how to consume events. This also limits the potential for libraries, tooling and infrastructure to aide the delivery of event data across environments, like SDKs, event routers or tracing systems. The portability and productivity we can achieve from event data is hindered overall.

CloudEvents is a specification for describing event data in common formats to provide interoperability across services, platforms and systems.

CloudEvents has received a large amount of industry interest, ranging from major cloud providers to popular SaaS companies. CloudEvents is hosted by the Cloud Native Computing Foundation (CNCF) and was approved as a Cloud Native sandbox level project on May 15, 2018.

CloudEvents Documents

The following documents are available:

Latest Release Working Draft
Core Specification:
CloudEvents v1.0 master
Optional Specifications:
AMQP Protocol Binding v1.0 master
AVRO Event Format - master
HTTP Protocol Binding v1.0 master
JSON Event Format v1.0 master
Kafka Protocol Binding - master
MQTT Protocol Binding v1.0 master
NATS Protocol Binding v1.0 master
Web hook v1.0 master
Additional Documentation:
CloudEvents Adapters - master
CloudEvents SDK Requirements - master
Documented Extensions - master
Primer v1.0 master
Proprietary Specifications - master

If you are new to CloudEvents, it is recommended that you start by reading the Primer for an overview of the specification's goals and design decisions, and then move on to the core specification.

Since not all event producers generate CloudEvents by default, there is documentation describing the recommended process for adapting some popular events into CloudEvents, see CloudEvents Adapters.


In addition to the documentation mentioned above, there are also an SDK proposal and a set of SDKs being developed:


Learn more about the people and organizations who are creating a dynamic cloud native ecosystem by making our systems interoperable with CloudEvents.

  • Contributors: people and organizations who helped us get started or are actively working on the CloudEvents specification.
  • Coming soon: demos & open source -- if you have something to share about your use of CloudEvents, please submit a PR!


The CloudEvents project is working to formalize the specification based on design goals which focus on interoperability between systems which generate and respond to events.

In order to achieve these goals, the project must describe:

  • Common attributes of an event that facilitate interoperability
  • One or more common architectures that are in active use today or planned to be built by its members
  • How events are transported from producer to consumer via at least one protocol
  • Identify and resolve whatever else is needed for interoperability


The mailing list for e-mail communications:

And a #cloudevents Slack channel under CNCF's Slack workspace.

Meeting Time

See the CNCF public events calendar. This specification is being developed by the CNCF Serverless Working Group. This working group meets every Thursday at 9AM PT (USA Pacific):

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap :

US: +16465588656,,3361029682#  or +16699006833,,3361029682#

Or Telephone:

    US: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)
    or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)

Meeting ID: 336 102 9682

International numbers available:

NOTE: Please use *6 to mute/un-mute your phone during the call.

World Time Zone Converter:

Meeting Minutes

The minutes from our calls are available here.

Recording from our calls are available here.

Periodically, the group may have in-person meetings that coincide with a major conference. Please see the meeting minutes for any future plans.

You can’t perform that action at this time.