ORACLE CLOUD
API Gateway actions
18 actions you can wire into a flow, alongside everything else in the Oracle Cloud integration.
Every API Gateway action
- OCI API Gateway: Change API CompartmentMove an API Gateway API into a different compartment: the API keeps its OCID, only its compartment placement changes.
- OCI API Gateway: Change Deployment CompartmentMove an API Gateway deployment into a different compartment: the deployment keeps its OCID, only its compartment placement changes.
- OCI API Gateway: Change Gateway CompartmentMove an API Gateway gateway into a different compartment: the gateway keeps its OCID, only its compartment placement changes.
- OCI API Gateway: Create APICreate an API resource holding an OpenAPI specification. Returns the API in a CREATING state plus a work-request id: poll Get API until ACTIVE.
- OCI API Gateway: Create DeploymentPublish an API on a gateway under a path prefix, with its routes defined by an API specification. Returns a work-request id: poll Get Deployment until ACTIVE.
- OCI API Gateway: Create GatewayCreate an API Gateway on a subnet. Choose a PUBLIC (internet-facing) or PRIVATE endpoint type. Returns the gateway in a CREATING state plus a work-request id: poll Get Gateway until ACTIVE.
- OCI API Gateway: Delete APIDelete an API resource by its OCID: returns a work-request id that tracks the delete to completion.
- OCI API Gateway: Delete DeploymentDelete an API Gateway deployment by its OCID: it unpublishes the API from the gateway. Returns a work-request id to track the delete.
- OCI API Gateway: Delete GatewayDelete an API Gateway by its OCID: it moves to DELETING and returns a work-request id to track the removal.
- OCI API Gateway: Get APIFetch a single API Gateway API resource by its OCID: its specification type, lifecycle state and details.
- OCI API Gateway: Get DeploymentFetch a single API Gateway deployment by its OCID: its gateway, path prefix, endpoint and lifecycle state.
- OCI API Gateway: Get GatewayFetch a single API Gateway by its OCID: its endpoint type, subnet, hostname and lifecycle state.
- OCI API Gateway: List APIsList the API resources in a compartment. Optionally filter by exact display name or lifecycle state, and cap the page size. Walks pagination up to a safe cap.
- OCI API Gateway: List DeploymentsList the API deployments in a compartment. Optionally filter by gateway OCID or exact display name. Walks pagination up to a safe cap.
- OCI API Gateway: List GatewaysList the API gateways in a compartment. Optionally filter by exact display name or lifecycle state, and cap the per-page size. Walks pagination up to a safe cap.
- OCI API Gateway: Update APIPartially update an API resource: change only the display name or specification content you supply; blank fields are left unchanged. Asynchronous: returns a work-request id, poll Get API until ACTIVE.
- OCI API Gateway: Update DeploymentPartially update an API Gateway deployment: change only the display name and/or API specification (JSON) you supply; blank fields are left unchanged. Returns a work-request id; poll Get Deployment until ACTIVE.
- OCI API Gateway: Update GatewayPartially update an API Gateway: change only the display name you supply; a blank field is left unchanged. Returns a work-request id; poll Get Gateway until ACTIVE.
Also in Oracle Cloud
Autonomous Database24 actionsBastion10 actionsBlock Volumes69 actionsCertificates20 actionsCloud Guard20 actionsCompute17 actionsContainer Engine44 actionsData Catalog26 actionsData Flow20 actionsDNS54 actionsDocument Understanding12 actionsEmail19 actionsEvents6 actionsExadata27 actionsFile Storage49 actionsFunctions15 actionsGenerative AI14 actionsIdentity90 actionsLanguage16 actionsLoad Balancer61 actionsLogging17 actionsMonitoring15 actionsMySQL HeatWave17 actionsNetwork Load Balancer33 actionsNetworking62 actionsNoSQL Database16 actionsNotifications16 actionsObject Storage15 actionsQueue19 actionsSpeech13 actionsStreaming30 actionsVault50 actionsVision10 actionsVulnerability Scanning19 actionsWeb Application Acceleration13 actionsWeb Application Firewall17 actions
Put API Gateway in a flow
These actions sit on the same canvas as every other integration, so a API Gateway step can follow a form, a schedule or a message without any glue code.