AsyncAPI channel · SPIFFE
· SPIFFE Workload API Events
/spiffe.workload.SpiffeWorkloadAPI/FetchJWTSVID
Request-response channel for fetching a JWT-SVID for a specific audience. Unlike X.509 streaming, JWT-SVIDs are issued on demand with a short TTL and should be fetched fresh for each use. The workload specifies the audience claim(s) and optionally a specific SPIFFE ID to obtain a JWT for.
Provider:SPIFFEAsyncAPI: v2.6.0Spec: SPIFFE Workload API EventsOperations: 1Messages: 1
Channel address
/spiffe.workload.SpiffeWorkloadAPI/FetchJWTSVID
Operations
subscribe
fetchJWTSVID
Receive a JWT-SVID
Messages
JWTSVIDResponse
One or more JWT-SVIDs for the requested audience
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.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.