GET /api/api-gateway/apis
Lists visible API configurations.
Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.
Configure HTTP API forwarding with the gateway’s management API and test the generated stage/name route.
API configuration is managed under /api/api-gateway/apis. Forwarded application traffic uses /api/gateway/{stage}/{api-name}/... . The account token used for management is separate from the API’s configured client authentication.
A saved toggle or configured authentication type must be validated with an actual request. Dashboard counters and displayed values do not replace upstream access or runtime checks.
Use your Genorbex deployment’s origin followed by the path below. Replace IDs with resources accessible to your account. Authentication and permissions are checked by each endpoint.
Lists visible API configurations.
Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.
Creates an API configuration with its target, stage, methods, authentication, and rate limit.
Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.
Forwards a request using the selected API configuration.
Authentication: The authentication policy configured for the selected gateway API.
Need help with your setup? Visit the Help Center or contact Genorbex.