OpenapiIngress
Creates or replaces one edge transform and hot-applies it. — POST /v1/ingress/middlewares
Creates or replaces one edge transform and hot-applies it.
POST /v1/ingress/middlewares
| Address | https://api.hanzo.ai/v1/ingress/middlewares |
| Method | POST |
| Operation | post_ingress_middlewares |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Creates or replaces one edge transform and hot-applies it. POST mints an id when the body omits one; PUT takes the id from the URL, which wins over any id in the body. type must be one of redirectScheme, stripPrefix, addPrefix or headers, and stripPrefix/addPrefix each require their config key.
Request
4 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
config | body | object | — | Config is the transform's parameters: redirectScheme takes scheme (default https) and permanent ("true" ⇒ 301, else 302); stripPrefix REQUIRES prefixes… |
config.* | body | string | — | |
id | body | string | — | ID identifies the transform within the org: [A-Za-z0-9-_.], at most 128 chars. |
type | body | string | — | Type is the transform: redirectScheme, stripPrefix, addPrefix or headers. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | Middleware | ok |
200 body — 4 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
config | body | object | — | Config is the transform's parameters: redirectScheme takes scheme (default https) and permanent ("true" ⇒ 301, else 302); stripPrefix REQUIRES prefixes… |
config.* | body | string | — | |
id | body | string | — | ID identifies the transform within the org: [A-Za-z0-9-_.], at most 128 chars. |
type | body | string | — | Type is the transform: redirectScheme, stripPrefix, addPrefix or headers. |
Failure carries the platform error shape — see Errors.
Examples
hanzo ingress middlewares createimport { Configuration, IngressApi } from 'hanzoai';
const api = new IngressApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIngressMiddlewares({ config: {}, id: "<id>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IngressApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IngressApi(client).post_ingress_middlewares(config={}, id="<id>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IngressAPI.PostIngressMiddlewares(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, ingress_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = ingress_api::post_ingress_middlewares(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IngressApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new IngressApi(client).postIngressMiddlewares();curl -X POST https://api.hanzo.ai/v1/ingress/middlewares \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"config": {},
"id": "<id>"
}'The door reaches ingress through the ingress tool, which names its 18 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_ingress_middlewares"
}
}
}'How is this guide?