AsyncAPI channel · SPIFFE · SPIFFE Workload API Events

/spiffe.workload.SpiffeWorkloadAPI/FetchX509SVID

Streaming channel through which workloads receive X.509-SVID identity documents. After the workload sends a request, the server streams back an initial bundle of all SVIDs the workload is authorized to hold, followed by updated bundles whenever certificates are rotated or authorization changes. The stream remains open indefinitely and the workload should reconnect if the stream is interrupted.

Open source AsyncAPI → All SPIFFE channels SPIFFE provider profile
Provider: SPIFFE AsyncAPI: v2.6.0 Spec: SPIFFE Workload API Events Operations: 1 Messages: 1

Channel address

/spiffe.workload.SpiffeWorkloadAPI/FetchX509SVID

Operations

fetchX509SVID
Stream X.509 SVID updates

Messages

X509SVIDResponse
A batch of X.509-SVIDs for the workload
Content-Type: application/protobuf

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.