Bidirectional streaming gRPC method. The client opens the stream with a DisperseBlobRequest, the disperser replies with a BlobAuthHeader containing a challenge parameter, the client signs and returns an AuthenticationData message, and the disperser closes by sending a DisperseBlobReply with the assigned request_id.
Client-to-disperser frames on the DisperseBlobAuthenticated stream.
receive
receiveAuthenticatedReply
Disperser-to-client frames on the DisperseBlobAuthenticated stream.
Messages
AuthenticatedRequest
Client frame on the DisperseBlobAuthenticated stream.
Content-Type:
AuthenticatedReply
Disperser frame on the DisperseBlobAuthenticated stream.
Content-Type:
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.