(registered 2026-05-12, last updated 2026-05-12)

Media type name: application

Media subtype name: cloudevents-batch+json

Required parameters: N/A

Optional parameters: N/A

Encoding considerations: binary

as per application/json

Security considerations: The CloudEvents specification and format does not directly deal with security with respect to on-the-wire protections. Since the CloudEvents format is really about standardizing how data appear within a message, not what the data is, it is assumed that existing transport security mechanisms will be used. In this respect, CloudEvents is meant to be additive to existing transport flows.

Specifically, to the points mentioned in the instructions at https://www.iana.org/form/media-types:

- A CloudEvent is not meant to contain active or executable content - at least not as part of the CloudEvents definition itself. It's just text/binary data to CloudEvents.

- CloudEvents itself doesn't need privacy or integrity services. If needed by the application, they can layer that on top of the CloudEvent structure, but it is out of scope for CloudEvents.

Interoperability considerations: As this is a usage/variant of application/json, this media type does not introduce any new interoperability concerns.

Published specification:

https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/formats/json-format.md

Applications which use this media: HTTP-based application. application/cloudevents+json is used when the HTTP body of a message contains exactly one CloudEvent. application/cloudevents-batch+json is used when the HTTP body of a message is setup to contain any number of CloudEvents. And in that case it’s a JSON array of individual CloudEvents.

Fragment identifier considerations: None but see:

https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/formats/json-format.md

Restrictions on usage: None

Additional information:

1. Deprecated alias names for this type: None
2. Magic number(s): None
3. File extension(s): json
4. Macintosh file type code: TEXT
5. Object Identifiers: None

Person to contact for further information:

1. Name: Doug Davis
2. Email: duglin&gmail.com

Intended usage: COMMON

Author/Change controller: CloudEvents project in the Linux Foundation (Cloud Native Computing Foundation)