Eventarc API

Name: Eventarc API API
Brand: Eventarc API
Availability: InStock

✓ Official Vendor SpecCloud 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.

Quickstart

Get started with Eventarc API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an Eventarc trigger from GCS to Cloud Run"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Eventarc API 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

GET STARTED

Start building with Eventarc API API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Eventarc API 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

Why though Jentic?

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

Credential isolation

Google service account keys are stored encrypted in the Jentic vault. Agents receive scoped OAuth access tokens with cloud-platform; the runtime service account attached to the trigger is referenced by name so its key never enters the agent context.

Intent-based discovery

Agents search by intent (e.g. 'fire Cloud Run when a file lands in GCS') and Jentic returns the trigger create operation with the eventFilters and destination schemas, including hints from the providers catalogue.

Time to first call

Direct Eventarc integration: 2-4 days for OAuth, IAM setup, trigger schema, and operation polling. Through Jentic: under 1 hour for a one-shot trigger creation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloud Pub/Sub API

Underlying transport for many Eventarc event types

Use directly when fine-grained control over subscriptions, ack deadlines, and dead-letter is needed beyond what Eventarc exposes

Complementary

Cloud Run Admin API

Manages Cloud Run services that Eventarc triggers invoke

Use alongside Eventarc when the agent needs to deploy or update the destination service

Complementary

Workflows API

Orchestrates multi-step flows that can be a trigger destination

Use when the trigger should kick off a Workflow rather than a single service

FAQs

Specific to using Eventarc API 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.