Pub/Sub API (event-bus)
- Pub/Sub API and Event Allocations
- Bidirectional Streaming
- Generate a Client Trace ID to Troubleshoot Non-Pub/Sub API Errors
- General Considerations
- Event Data Serialization with Apache Avro
- Event Deserialization Considerations
- Event Message Durability
- Pub/Sub API and the Expanded Event Bus
- Pull Subscription and Flow Control
- Generate Code from the Proto File
- Pub/Sub API as a gRPC API
- Handle Errors
- Get Started with Pub/Sub API
- Managed Event Subscriptions (Beta)
- Code Examples
- API End-of-Life Policy
- Pub/Sub API Endpoints
- Pub/Sub API Features
- Step 2: Build the Python Client
- Step 1: Generate the Stub Files
- Step 2: Build the Client
- Step 5: Subscribe to Change Events
- Java Quick Start for Managed Event Subscriptions (Beta)
- Step 1: Create ManagedEventSubscription with Tooling API
- Step 3: Publish Events and Verify the Managed Subscription
- Step 2: Start the Managed Subscription
- Step 3: Configure Client Parameters
- Step 1: Define a Platform Event
- Step 4: Publish and Subscribe to Platform Events
- Java Quick Start
- Java Quick Start for Publishing and Subscribing to Events
- Step 5: Write Code That Publishes a Platform Event Message
- Python Quick Start for Pub/Sub API
- Step 3: Set Up Events
- Step 4: Write Code That Subscribes to an Event Channel
- Quick Starts
- Retry Long-Lived RPC Calls After an Error Occurs
- Provide the RPC ID When Contacting Support to Troubleshoot an Error
- Include Authorization Headers in RPC Method Calls
- Set a Deadline on the GetSchema, GetTopic, and Publish Unary RPC Methods
- Authentication
- Event Types
- Use Pub/Sub API
- GetSchema RPC Method
- GetTopic RPC Method
- ManagedSubscribe RPC Method (Beta)
- Publish RPC Method
- PublishStream RPC Method
- Subscribe RPC Method