Method: projects.locations.applications.addStreamInput

Adds target stream input to the Application. If the Application is deployed, the corresponding new Application instance will be created. If the stream has already been in the Application, the RPC will fail.

HTTP request

POST https://{endpoint}/v1/{name=projects/*/locations/*/applications/*}:addStreamInput

Where {endpoint} is one of the supported service endpoints.

The URLs use gRPC Transcoding syntax.

Path parameters



Required. the name of the application to retrieve. Format: "projects/{project}/locations/{location}/applications/{application}"

Request body

The request body contains data with the following structure:

JSON representation
  "applicationStreamInputs": [
      object (ApplicationStreamInput)
  "requestId": string

object (ApplicationStreamInput)

The stream inputs to add, the stream resource name is the key of each StreamInput, and it must be unique within each application.



Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request.

For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.

The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).

Response body

If successful, the response body contains an instance of Operation.

Authorization Scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.