Amazon EventBridge Schema Registry

Name: Amazon EventBridge Schema Registry API
Brand: Amazon EventBridge Schema Registry
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityhmac31 EndpointsREST

For Agents

Store, version, discover, and generate code bindings for the event schemas that flow through Amazon EventBridge.

Connect the Amazon EventBridge Schema Registry to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon EventBridge Schema Registry, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon EventBridge Schema Registry API.

Create and manage schema registries with CreateRegistry and DeleteRegistry

Author or import OpenAPI 3 / JSON Schema event definitions with CreateSchema and UpdateSchema

Track schema versions and inspect a specific version with DescribeSchema and ListSchemaVersions

Auto-detect new schemas from EventBridge event traffic with CreateDiscoverer and StartDiscoverer

GET STARTED

Start building with Amazon EventBridge Schema Registry API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon EventBridge Schema Registry, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon EventBridge Schema Registry, keeping it validated and agent-ready. The Schema Registry stores and versions the structure of events flowing through Amazon EventBridge — both AWS-published schemas and custom schemas your applications produce. Discoverers can auto-detect new schema shapes from event traffic; the registry exposes versions, code-binding artifacts, and search so engineering teams can generate strongly-typed event handlers in their language of choice.

Use Cases

Patterns agents use Amazon EventBridge Schema Registry API for, with concrete tasks.

★ Strongly-typed event consumer generation

Application teams use the Schema Registry to generate Java, Python, or TypeScript code bindings for events they consume from EventBridge. PutCodeBinding triggers generation; GetCodeBindingSource downloads the artifact zip. This eliminates hand-written deserialisation, catches breaking-change bugs at compile time rather than runtime, and keeps consumers in step with producers across teams.

Call PutCodeBinding with RegistryName='my-app', SchemaName='OrderPlaced', SchemaVersion='3', and Language='Python36', then poll DescribeCodeBinding until status is CREATE_COMPLETE and download via GetCodeBindingSource.

Auto-discovery of unknown event shapes

Platform teams turn on schema discovery against an event bus to automatically generate schemas for new event shapes that arrive. CreateDiscoverer and StartDiscoverer attach the discoverer to a bus; the registry then populates the discovered-schemas registry as events flow, giving engineering visibility into payload structure without manual onboarding.

Call CreateDiscoverer with the EventBridge bus ARN, StartDiscoverer to begin discovery, then list discovered schemas with ListSchemas filtered by SchemaType='OpenApi3'.

Schema governance across teams

Architecture teams use multiple registries to separate AWS-managed schemas from team-owned schemas, applying tags via TagResource so each registry is clearly owned. UpdateSchema accepts new versions while preserving prior ones, so consumers can pin to a known version while producers iterate. This is the governance layer that prevents accidental breaking changes from rippling through downstream services.

Call CreateRegistry RegistryName='payments-team', CreateSchema for InvoiceFinalised with content from the team's OpenAPI 3 definition, then TagResource with Owner='payments-team'.

Agent-driven event schema lookup through Jentic

AI agents that route or transform events use Jentic to call DescribeSchema, SearchSchemas, and ListSchemaVersions without holding raw AWS credentials. Jentic stores keys in the MAXsystem vault, signs each request with SigV4, and returns the structured schema content — so an agent can fetch the canonical shape of an event before deciding how to handle it.

Search Jentic for 'describe an EventBridge schema', load DescribeSchema, and execute it with RegistryName='aws.events' and SchemaName matching the event detail-type to retrieve the canonical structure.

Key Endpoints

31 endpoints — jentic publishes the only available openapi specification for amazon eventbridge schema registry, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/registries/name/{registryName}

Create a schema registry

POST

/v1/registries/name/{registryName}/schemas/name/{schemaName}

Create or update a schema

GET

/v1/registries/name/{registryName}/schemas/name/{schemaName}

Describe a schema and its content

GET

/v1/registries/name/{registryName}/schemas

List schemas in a registry

POST

/v1/discoverers

Create a schema discoverer on an EventBridge bus

GET

/v1/discoverers

List discoverers

POST

/v1/registries/name/{registryName}/schemas/name/{schemaName}/language/{language}

Generate a code binding

GET

/v1/registries/name/{registryName}/schemas/name/{schemaName}/language/{language}/source

Download a generated code binding

POST

/v1/registries/name/{registryName}

Create a schema registry

POST

/v1/registries/name/{registryName}/schemas/name/{schemaName}

Create or update a schema

GET

/v1/registries/name/{registryName}/schemas/name/{schemaName}

Describe a schema and its content

GET

/v1/registries/name/{registryName}/schemas

List schemas in a registry

POST

/v1/discoverers

Create a schema discoverer on an EventBridge bus

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS credentials are stored encrypted in the Jentic vault (MAXsystem). Each Schema Registry call is signed with SigV4 server-side; the agent only receives scoped, short-lived authorisation, so raw access keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'describe an EventBridge schema') and Jentic returns matching Schema Registry operations with their input schemas, so the agent calls DescribeSchema or PutCodeBinding without browsing AWS docs.

Time to first call

Direct Schema Registry integration: 1-2 days for SigV4 signing, polling code-binding generation, and S3-style download handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon EventBridge

The event bus that the schema registry catalogues schemas for

Use EventBridge to publish and route events; use the Schema Registry to define and discover the structure of those events.

Complementary

AWS Lambda

Lambda functions are the most common typed-binding consumers of registered schemas

Use Lambda to consume events; use Schema Registry-generated code bindings to deserialise them in a strongly-typed way.

Complementary

AWS Step Functions

Step Functions workflows triggered by EventBridge benefit from registered, versioned schemas

Use Step Functions for orchestrating multi-step event-driven workflows; use Schema Registry to keep the input shape stable across versions.

FAQs

Specific to using Amazon EventBridge Schema Registry API through Jentic.

Why is there no official OpenAPI spec for the EventBridge Schema Registry?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon EventBridge Schema Registry via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the EventBridge Schema Registry API use?

It uses AWS Signature Version 4 HMAC signing with an access key ID and secret access key, optionally with a session token. Through Jentic, those credentials live in the MAXsystem vault and the agent never handles raw secrets — Jentic signs each request server-side.

Can I publish or consume events with the EventBridge Schema Registry API?

No — this API stores schemas and versions, not events themselves. To publish events, use the EventBridge PutEvents operation on the events service. To consume, attach an EventBridge target (Lambda, SQS, Step Functions). The schema registry is the type system, not the event bus.

What are the rate limits for the EventBridge Schema Registry API?

AWS does not publish a fixed RPS in the spec; standard AWS API throttling applies and the service returns ThrottlingException on overage. There are also quotas on schemas per registry and discoverers per account, surfaced in the AWS service quotas console.

How do I generate Python code bindings for an event schema through Jentic?

Search Jentic for 'generate EventBridge code binding', load PutCodeBinding, and call POST /v1/registries/name/{registryName}/schemas/name/{schemaName}/language/Python36. Poll DescribeCodeBinding until Status is CREATE_COMPLETE, then download with GetCodeBindingSource. Install with pip install jentic.

What schema formats does the EventBridge Schema Registry support?

The registry supports OpenAPI 3.0 and JSON Schema Draft 4 as schema content. CreateSchema accepts either format; DescribeSchema returns the original content as written. AWS-managed schemas (the aws.events registry) are published in OpenAPI 3.0 form by default.