CloudEvents Validator screenshot

CloudEvents Validator

Validate a CloudEvents JSON event: the four required attributes, specversion 1.0, a URI-reference source and an RFC 3339 time.

Privacy First
0 Runs
Updated 2026-11-17
Runs in your browser
No sign-up, no upload

What the CloudEvents Validator does

The four required attributes are specversion, id, source and type. This page checks presence and type, that specversion is the string 1.0, that source is a non-empty URI-reference without spaces, and that a time is an RFC 3339 UTC timestamp.

The report lists which optional attributes are present, because subject, datacontenttype, dataschema and time are usually what a consumer needs next.

It validates the envelope, not the payload: data is not inspected and dataschema is not resolved. It also does not check that a type is registered in a schema registry — that is the registry's job.

How to use it

Paste the event into the CloudEvent JSON box, or press Run with the example already there.

Read the Validation report below: the specversion, type, source, id and the optional attributes present.

Remove an attribute and press Run again — the refusal names the field that is required.

Worked example

Input:

{
  "specversion": "1.0",
  "id": "1",
  "source": "/app",
  "type": "user.created",
  "time": "2026-11-17T00:00:00Z"
}

Output:

Valid: yes
Specversion: 1.0
Type: user.created
Source: /app
Id: 1
Optional present: time

Why it runs in your browser

The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.

A CloudEvents 1.0 check: the four required attributes are present, the specversion is exactly `1.0`, the source is a URI-reference and the time, if present, is RFC 3339 UTC.

The missing attribute is named, so a malformed event says which field an emitter forgot rather than that it is invalid.

What it does, and what it does not

The four required attributes are `specversion`, `id`, `source` and `type`. This page checks presence and type, that specversion is the string `1.0`, that source is a non-empty URI-reference without spaces, and that a `time` is an RFC 3339 UTC timestamp.

The report lists which optional attributes are present, because `subject`, `datacontenttype`, `dataschema` and `time` are usually what a consumer needs next.

It validates the envelope, not the payload: `data` is not inspected and `dataschema` is not resolved. It also does not check that a `type` is registered in a schema registry — that is the registry's job.

How to use CloudEvents Validator

Paste the event into the CloudEvent JSON box, or press Run with the example already there.

Read the Validation report below: the specversion, type, source, id and the optional attributes present.

Remove an attribute and press Run again — the refusal names the field that is required.

What to Expect

Best for

  • Catching a malformed event before a broker sees it
  • Checking which optional attributes an emitter sends

Not ideal for

  • Validating the payload, which needs its schema
  • Checking a registry, which this page cannot reach

What this tool keeps

  • The required attribute names exactly
  • The optional attributes that are present

What may need cleanup

  • Validate the payload against dataschema separately
  • A registered type is the registry's check, not this page's

Common errors

  • The page refuses it: required attribute specversion is missing

Example use cases

  • Reviewing an emitter's output
  • Debugging an event a consumer rejects

Sample input

CloudEvent JSON: { …

Sample output

Validation report: Valid: yes …

Who this is for

  • Developers building an event-driven service
  • Anyone integrating a CloudEvents broker

Frequently asked questions

Which attributes are required?

specversion, id, source and type. Everything else is optional, and the page lists which optional attributes your event carries.

Does source have to be a URL?

No. It is a URI-reference, so /app and urn:example:app are both valid. Only an empty value or one containing a space is refused.

Is the data checked?

No. data belongs to the event's own schema, named by dataschema. This page validates the envelope that wraps it.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.