Google Cloud Pub/Sub API
Browse all Google APIs✓ Official Vendor SpecCloud InfrastructureServerlessoauth233 EndpointsREST
For Agents
Publish messages, manage topics and subscriptions, and pull or acknowledge messages on Google Cloud Pub/Sub for event-driven and streaming workloads.
Use for: I need to publish a message to a Pub/Sub topic, Pull pending messages from a subscription and acknowledge the ones we processed, Create a new topic with a 7-day message retention policy, Set up a push subscription that delivers messages to a Cloud Run service
Not supported: Does not handle long-running task scheduling, durable workflow orchestration, or stream processing transformations — use for asynchronous topic and subscription messaging only.
Google Cloud Pub/Sub is a globally distributed, fully managed messaging service for asynchronous service-to-service communication, event ingestion, and streaming analytics pipelines. The REST API exposes topics, subscriptions, snapshots, schemas, and IAM controls so producers can publish messages, subscribers can pull or acknowledge them, and operators can manage retention, ordering, and dead-letter behavior. Pub/Sub backs many Google Cloud event flows, including Cloud Storage notifications, Dataflow pipelines, and Cloud Run event triggers.
Install Jentic One Beta
Connect the Cloud Pub/Sub API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Pub/Sub 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: 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 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 Cloud Pub/Sub API.
Create topics and configure message retention, schema, and ordering settings
Create push or pull subscriptions on a topic with custom ack deadlines and dead-letter policies
Publish batches of messages to a topic with attribute-based filtering metadata
Pull messages from a subscription and acknowledge them after processing
Manage Pub/Sub schemas and validate messages against Avro or Protocol Buffer definitions
Create snapshots of subscription state and seek subscriptions to a prior point in time
Use Cases
Patterns agents use Cloud Pub/Sub API for, with concrete tasks.
★ Event-Driven Microservices
Decouple producers and consumers across services using Pub/Sub as the asynchronous transport. Producers publish events to topics; consumers attach pull or push subscriptions, process messages, and acknowledge them. Pub/Sub handles delivery, retry, ordering, and dead-letter routing automatically across regions.
Create topic order-events with 7-day retention, create push subscription order-events-fulfillment to https://fulfillment.example.com/events, and publish a JSON message with attribute event_type=order.created.
Streaming Analytics Ingestion
Ingest high-volume application or device telemetry into Pub/Sub topics so downstream Dataflow or BigQuery pipelines can consume them in near real time. Schema validation can be enforced at the topic level so malformed events are rejected before they enter the pipeline.
Create a Pub/Sub schema in Avro, attach it to topic telemetry, then publish a batch of validated telemetry events from edge devices.
Disaster Recovery and Replay
Use Pub/Sub snapshots and seek-to-time to replay a subscription after a downstream consumer fails or after a bad deploy. Snapshots capture the unacked-message state, and seek operations rewind a subscription to a snapshot or wall-clock timestamp without affecting other subscriptions on the same topic.
Create a snapshot of subscription orders-fulfillment-sub, deploy the fix, then call seek with the snapshot name to redeliver messages from before the bad deploy.
Agent-Driven Event Publishing
An AI agent integrating with Google Cloud uses Jentic to publish events to Pub/Sub topics in response to user requests or upstream signals, so other workloads (workflows, analytics jobs, alerting) can react asynchronously without point-to-point integration.
Search Jentic for publish a message to a pubsub topic, load the schema for projects.topics.publish, and execute it with the topic and a base64-encoded message body.
Key Endpoints
33 endpoints — google cloud pub/sub is a globally distributed, fully managed messaging service for asynchronous service-to-service communication, event ingestion, and streaming analytics pipelines.
METHOD
PATH
DESCRIPTION
GET
/v1/{+project}/topics
List topics in a project
GET
/v1/{+project}/subscriptions
List subscriptions in a project
GET
/v1/{+project}/snapshots
List snapshots in a project
POST
/v1/{+name}:commit
Commit a schema revision
POST
/v1/{+name}:rollback
Rollback a schema to a prior revision
POST
/v1/{+parent}/schemas:validate
Validate a schema definition
POST
/v1/{+parent}/schemas:validateMessage
Validate a message against a schema
GET
/v1/{+project}/topics
List topics in a project
GET
/v1/{+project}/subscriptions
List subscriptions in a project
GET
/v1/{+project}/snapshots
List snapshots in a project
POST
/v1/{+name}:commit
Commit a schema revision
POST
/v1/{+name}:rollback
Rollback a schema to a prior revision
POST
/v1/{+parent}/schemas:validate
Validate a schema definition
POST
/v1/{+parent}/schemas:validateMessage
Validate a message against a schema
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google OAuth 2.0 credentials are stored encrypted in the Jentic vault. Scoped access tokens (cloud-platform or pubsub) are issued at call time so the underlying refresh token never enters the agent, and IAM bindings determine what operations the agent can perform.
Intent-based discovery
Agents search Jentic by intent (publish a message, pull messages, create a subscription) and Jentic returns the matching Pub/Sub operation with its input schema, so the agent can build a correct request without reading Google's discovery doc.
Time to first call
Direct integration with Pub/Sub takes 1-2 days for auth, IAM, and message encoding patterns. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Pub/Sub API through Jentic.
What authentication does the Cloud Pub/Sub API use?
The API uses Google OAuth 2.0 with the cloud-platform or pubsub scopes, sent as a Bearer token in the Authorization header. Through Jentic the OAuth credentials are stored in the vault and short-lived access tokens are minted per call so the refresh token never enters the agent.
Can I publish messages with attributes for filtering?
Yes, every message body can include a map of string attributes. Subscriptions can declare a filter expression that matches on those attributes, so the same topic can fan out to multiple consumers each receiving only the events relevant to them.
What are the rate limits for the Cloud Pub/Sub API?
Pub/Sub publisher and subscriber quotas are large by default and are documented on Google Cloud's Pub/Sub quotas page in MB/s and ops/s. For very high-throughput workloads consider using the gRPC client libraries instead of REST and request quota increases up front.
How do I publish a message through Jentic?
Search Jentic for publish a message to a pubsub topic, load the schema for the projects.topics.publish operation which maps to POST /v1/{+topic}:publish, then execute it with messages encoded as base64 in the request body.
Is the Cloud Pub/Sub API free?
Pub/Sub has a free tier of 10 GB of message data per month; beyond that, throughput is billed per GB ingested, delivered, and stored. Snapshots and seek operations also incur storage charges. Pricing is identical whether the API is called directly or through Jentic.
How do I replay messages after a bad deploy?
Take a snapshot of the subscription before the deploy with POST /v1/{+name}:createSnapshot semantics on snapshots, then call POST /v1/{+subscription}:seek with the snapshot name after the fix is deployed to redeliver messages that were acked during the broken window.
GET STARTED