Amazon API Gateway · Arazzo Workflow

AWS API Gateway Deploy an HTTP API to a New Stage

Version 1.0.0

Confirm an HTTP API, create a deployment, and publish it to a new stage bound to that deployment.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub API GatewayCloudRESTHTTPWebSocketServerlessMCPAgentCoreDeveloper PortalArazzoWorkflows

Provider

aws-api-gateway

Workflows

deploy-http-api-stage
Create a deployment and bind a new stage to it.
Confirms an API, creates a deployment, and creates a stage referencing the new deployment id.
3 steps inputs: apiId, description, stageName outputs: apiName, deploymentId, stageName
1
confirmApi
Confirm the API exists before deploying it.
2
createDeployment
Create a deployment snapshot of the current API configuration.
3
createStage
Create a stage bound to the new deployment id.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: AWS API Gateway Deploy an HTTP API to a New Stage
  summary: Confirm an HTTP API, create a deployment, and publish it to a new stage bound to that deployment.
  description: >-
    Publishes a new stage for an existing Amazon API Gateway V2 HTTP or WebSocket
    API. The workflow confirms the API exists, creates a deployment snapshot, and
    creates a stage bound to that deployment id. Because createDeployment collides
    with the V1 description it is addressed through the V2 source. Every step
    spells out its request inline so the flow can be read and executed without
    opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: apisApi
  url: ../openapi/aws-api-gateway-apis-api-openapi.yml
  type: openapi
- name: deploymentsApi
  url: ../openapi/aws-api-gateway-deployments-api-openapi.yml
  type: openapi
- name: stagesApi
  url: ../openapi/aws-api-gateway-stages-api-openapi.yml
  type: openapi
workflows:
- workflowId: deploy-http-api-stage
  summary: Create a deployment and bind a new stage to it.
  description: >-
    Confirms an API, creates a deployment, and creates a stage referencing the
    new deployment id.
  inputs:
    type: object
    required:
    - apiId
    - stageName
    properties:
      apiId:
        type: string
        description: Identifier of the existing API.
      description:
        type: string
        description: Optional description for the deployment.
      stageName:
        type: string
        description: Name of the stage to create.
  steps:
  - stepId: confirmApi
    description: Confirm the API exists before deploying it.
    operationId: getApi
    parameters:
    - name: api_id
      in: path
      value: $inputs.apiId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      apiName: $response.body#/Name
  - stepId: createDeployment
    description: Create a deployment snapshot of the current API configuration.
    operationId: $sourceDescriptions.deploymentsApi.createDeployment
    parameters:
    - name: api_id
      in: path
      value: $inputs.apiId
    requestBody:
      contentType: application/json
      payload:
        Description: $inputs.description
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      deploymentId: $response.body#/DeploymentId
      deploymentStatus: $response.body#/DeploymentStatus
  - stepId: createStage
    description: Create a stage bound to the new deployment id.
    operationId: createStage
    parameters:
    - name: api_id
      in: path
      value: $inputs.apiId
    requestBody:
      contentType: application/json
      payload:
        StageName: $inputs.stageName
        DeploymentId: $steps.createDeployment.outputs.deploymentId
        AutoDeploy: false
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      stageName: $response.body#/StageName
  outputs:
    apiName: $steps.confirmApi.outputs.apiName
    deploymentId: $steps.createDeployment.outputs.deploymentId
    stageName: $steps.createStage.outputs.stageName

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/aws-api-gateway-deploy-http-api-stage-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

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.

A second provider on the same verified email joins the account you already have.