You are viewing the Apigee Management API reference documentation. For the main product docs, and to search all docs, go to

Deploy a shared flow

Deploy a shared flow


Deploy a shared flow

Deploys a shared flow revision to an environment in an organization. Shared flows cannot be used until they have been deployed to an environment.


If you experience HTTP 500 errors during deployment, consider using the override parameter to deploy the shared flow in place of a revision currently deployed.


The size limit of a shared flow bundle is 15 MB.

Resource URL /organizations/{org_name}/environments/{env_name}/sharedflows/{shared_flow_name}/revisions/{revision_number}/deployments

Query Parameters

Name Values Description

true to deploy the shared flow revision in place of the revision currently deployed (also known as "zero downtime" deployment).


Enforces a delay, measured in seconds, before the currently deployed API proxy revision is undeployed and replaced by the new revision that is being deployed. Use this setting to minimize the impact of deployment on in-flight transactions. The default value is 0.

Request Body

org_name Name of your organization. null true

env_name Name of the environment to which the shared flow should be deployed. null true

shared_flow_name The name of the shared flow to deploy. null true

revision_number The revision number of the shared flow to deploy. null true

HTTP Basic

OAuth 2.0



Make a request and see the response.

Make a request and see the response.

Make a request and see the response.

Response Error Details

  • HTTP Code
    Error Code
  • 400

    Bad Request if the shared flow can't be deployed because it's already deployed.

Resource Summary



Shared flows


Help or comments?

  • If something's not working: Ask the Apigee Community or see Apigee Support.
  • If something's wrong with the docs: Click the "Send Feedback" button.
    (Incorrect? Unclear? Broken link? Typo?)