Column | Description |
Name | Displays API name with an icon representing the API type. API type can be REST, SOAP, OData, and WebSocket. |
Description | Displays brief description of the API. |
Active endpoints | Indicates the active endpoints available for the API and shows how an API can be called. These are the active endpoint indicators: specifies that the API Gateway endpoint is active. This implies that the API can be called on the API Gateway endpoint. specifies that the API Gateway endpoint is inactive. The API is not exposed by API Gateway and API calls are rejected by API Gateway with HTTP 404 responses. specifies that the API is deployed to one or more Microgateways and therefore has active Microgateway endpoints. The API does not have any active API Gateway endpoints. Any API calls against API Gateway are rejected by API Gateway with HTTP 404 responses. The available Microgateway endpoints can be looked up in the API details screen. The list of active Microgateway endpoints is updated whenever a new Microgateway is registered or a Microgateway is de-registered. If the last Microgateway becomes unavailable, the endpoint indicator no longer shows active Microgateway endpoints specifies that API Gateway and Microgateway endpoints are active but there is no routing of API calls from API Gateway to Microgateway endpoints. This situation results from deploying an API with an active API Gateway endpoint to one or more Microgateways. The policy enforcement is done on the API Gateway and Microgateways independently. Deactivating and activating the API in API Gateway establishes the routing to the Microgateway endpoints. specifies that API Gateway and Microgateway endpoints are active. API calls against the API Gateway endpoint are routed to the Microgateway endpoints. If multiple Microgateway endpoints are available, API Gateway applies load balanced routing to the API calls. The load balancing follows the round-robin algorithm. If a Microgateway endpoint becomes unavailable the next endpoint is contacted. If no Microgateway endpoint replies, the API call in API Gateway fails. The list of Microgateways covered by the routing is updated dynamically. The policy definitions in API Gateway are enforced by Microgateways. To activate the routing in API Gateway to Microgateways, the APIs have to be deployed to Microgateway first before activating the API in API Gateway. If the last Microgateway becomes unavailable the routing is not removed implicitly. API calls against API Gateway fail as no Microgateway endpoint is available. specifies that an API has an active AppMesh endpoint, but no active API Gateway endpoint. An AppMesh endpoint is established by performing an APIfy operation. The policy definitions in API Gateway are enforced within the AppMesh. The API is not exposed by API Gateway and API calls are rejected by API Gateway with HTTP 404 responses. specifies that API Gateway and AppMesh endpoints are active. API calls against the API Gateway endpoint are routed to the AppMesh endpoint. The policy definitions in API Gateway are enforced within the AppMesh. |
Version | Displays API version. |
Modified Time | Displays the time when the API was last modified. |