Official vendor OpenAPI document · agent-readyCloud InfrastructureServerlessoauth225 EndpointsREST
For Agents
Create event triggers that route Cloud and third-party events to Cloud Run, Cloud Functions, GKE, or Workflows targets, with filtering, channels, and full lifecycle management.
Use for: I need to fire a Cloud Run service when a new file lands in a GCS bucket, Create a trigger for Pub/Sub messages that invokes a Cloud Function, Set up a third-party channel to receive Datadog events, List all triggers in the project so I can audit them
Not supported: Does not publish events, run code, or manage destination services - use for creating and managing event triggers, channels, and routing only.
Eventarc routes events from Google Cloud sources, third-party SaaS providers, and custom publishers to event-driven workloads such as Cloud Run, Cloud Functions, GKE, and Workflows. The API manages triggers (which events to listen for and where to send them), channels and channel connections (third-party event delivery), Google API and provider catalogues, and the long-running operations that back these resources. Triggers can filter on event type, attributes, and source so each consumer receives only the events it cares about. It is the canonical event bus for Google Cloud serverless and container workloads.
Install Jentic One Beta
Connect the Eventarc API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eventarc API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Feventarc" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Feventarc" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Eventarc API.
Create a trigger that listens for a specific event type from a Google Cloud source and delivers to a Cloud Run service
Filter events by attributes such as resource name, method, or service so only relevant events fire the target
Set up a channel and channel connection to receive events from a third-party SaaS provider
List available Google API event sources and provider catalogues so the agent picks valid event types
Patch an existing trigger to change its destination, filter, or service account without recreating it
Cancel or check long-running operations that back trigger and channel creation
Use Cases
Patterns agents use Eventarc API for, with concrete tasks.
★ GCS Object Created > Cloud Run Pipeline
Data ingestion teams set up triggers that fire whenever a new object lands in a Cloud Storage bucket so a Cloud Run worker processes it without an always-on consumer. The API creates the trigger with eventFilters on type='google.cloud.storage.object.v1.finalized' and the bucket resource name. Pipeline wiring takes minutes versus building an alternative Pub/Sub-plus-subscription stack from scratch.
POST /v1/{+parent}/triggers with eventFilters [{attribute:'type',value:'google.cloud.storage.object.v1.finalized'},{attribute:'bucket',value:'my-bucket'}] and destination.cloudRun.service set to the worker.
Third-Party SaaS Event Delivery
Platform teams wire SaaS providers (Datadog, Stripe-style partners, internal vendors) into Google Cloud workloads via Eventarc channels. The provider sends events to a channel; the team creates triggers off that channel scoped to event types of interest. This consolidates third-party event delivery on the same routing primitives as native Google Cloud events.
POST /v1/{+parent}/channels to create a channel for the provider, then POST /v1/{+parent}/triggers referencing the channel and the desired event type.
Cross-Service Event-Driven Architectures
Engineering teams break monoliths into event-driven services where each domain reacts to others' events through Eventarc. Triggers route the right events to Cloud Run, Cloud Functions, or Workflows targets, and the patch endpoint allows non-disruptive evolution of routing as the topology changes. New event consumers appear in days, not weeks.
PATCH /v1/{+name} on the existing trigger to add an attribute filter for service='users.example.com' so only user-domain events reach the worker.
Agent-Configured Event Routing via Jentic
An AI agent helping a developer set up a serverless workflow can create the right Eventarc trigger through Jentic without the developer learning Eventarc resource paths or filter syntax. The agent learns the available event types from the providers list and creates the trigger that matches the developer's intent in one step.
Search Jentic for 'create an Eventarc trigger', load the POST /v1/{+parent}/triggers schema, and execute it with the developer's source bucket and target Cloud Run service.
Key Endpoints
25 endpoints — eventarc routes events from google cloud sources, third-party saas providers, and custom publishers to event-driven workloads such as cloud run, cloud functions, gke, and workflows.
METHOD
PATH
DESCRIPTION
POST
/v1/{+parent}/channelConnections
Create a channel connection from a provider
GET
/v1/{+parent}/channelConnections
List channel connections
PATCH
/v1/{+name}
Patch a trigger, channel, or related resource
DELETE
/v1/{+name}
Delete a trigger or channel
POST
/v1/{+name}:cancel
Cancel a long-running operation
GET
/v1/{+name}/locations
List supported locations
POST
/v1/{+parent}/channelConnections
Create a channel connection from a provider
GET
/v1/{+parent}/channelConnections
List channel connections
PATCH
/v1/{+name}
Patch a trigger, channel, or related resource
DELETE
/v1/{+name}
Delete a trigger or channel
POST
/v1/{+name}:cancel
Cancel a long-running operation
GET
/v1/{+name}/locations
List supported locations
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
Eventarc API
- Foundational (D-)41/100
67
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
67
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B+Signals: 4
69%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
72%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Eventarc API by hand means standing up Google OAuth2 with the right scopes, targeting eventarc.googleapis.com, and building the resource-path calls yourself for triggers, channels, and routing. Through Jentic you install once, import the Eventarc API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Eventarc puts the resource name in the URL path (/v1/{+parent}/channelConnections, /v1/{+name}), so a rule can pin your agent to one project or location: it can list and create channel connections there and nothing else. You choose the operations it may call, so destructive ones like deleting a resource are not included unless you add them.
Credential isolation
Your Google OAuth credential for Eventarc is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Eventarc triggers' or 'create a channel connection', and Jentic returns the matching Eventarc operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Eventarc API through Jentic.
What authentication does the Eventarc API use?
Eventarc uses Google OAuth 2.0 with the cloud-platform scope. A service account with the eventarc.admin role (or a narrower trigger-specific role) creates triggers; a separate runtime service account is attached to each trigger so it can invoke the destination. Through Jentic the credentials live in the encrypted vault.
Can I filter events by attribute on the Eventarc API?
Yes. POST /v1/{+parent}/triggers accepts an eventFilters list of attribute-value pairs (type, bucket, methodName, serviceName, and so on). Triggers fire only when an event matches every filter, so a single source can fan out to many targets.
What are the rate limits for the Eventarc API?
Per-project quotas default to 60 trigger writes per minute and 600 reads per minute, with separate quotas on event delivery to destinations. Trigger and channel operations return long-running operations that the API surfaces via the operations resource.
How do I create a Cloud Run trigger through Jentic?
Search Jentic for 'create an Eventarc trigger to Cloud Run', load the POST /v1/{+parent}/triggers schema, and execute it with eventFilters for the source you want and destination.cloudRun.service set to your Cloud Run service. Jentic returns the long-running operation; poll until DONE.
Is the Eventarc API free?
The API is free to call. Eventarc charges per million events delivered (with a free tier of 1 million events per month) plus standard charges for the destination service. See https://cloud.google.com/eventarc/pricing for current rates.
How do I patch an existing trigger?
PATCH /v1/{+name} with the trigger resource name and an updateMask listing the fields to change (eventFilters, destination, serviceAccount). The change is applied as a long-running operation and the trigger continues to deliver events on the previous configuration until the operation completes.
Can I limit what my agent is allowed to do with the Eventarc API?
Yes. Because you run your own self-hosted Jentic One instance, your rules decide exactly which Eventarc operations and credentials the agent may use. Eventarc carries the resource name in the URL path (for example /v1/{+parent}/channelConnections and /v1/{+name}), so a rule can pin the agent to a single project or location and let it only list and create the triggers and channels there. You pick the operations it may call, so destructive ones like deleting a trigger or channel are excluded unless you explicitly add them.
GET STARTED