API Gateway

Configure HTTP API forwarding with the gateway’s management API and test the generated stage/name route.

Open API Gateway

Configure and test an API

  1. Create an API configuration with its name, stage, allowed methods, target URL, and authentication option.
  2. Review timeout, rate limit, CORS, and forwarding settings offered by the form.
  3. Call the generated /api/gateway/{stage}/{api-name}/... path on your own deployment.
  4. Verify the upstream response, access policy, and any logging or scheduled operation you enable.

Management and traffic

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.

API endpoints

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.

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.

POST /api/api-gateway/apis

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.

GET /api/gateway/{stage}/{apiName}/{...path}

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.