Ambassador · Schema
HostSpec
Specification for an Ambassador Host
API DevelopmentGatewaysIngressKubernetesMock ServersMocksPlatformTesting
Properties
| Name | Type | Description |
|---|---|---|
| hostname | string | Hostname that this Host resource applies to. Supports wildcard patterns like *.example.com. |
| ambassador_id | array | Ambassador IDs that should apply this Host |
| acmeProvider | object | ACME certificate provider configuration for automatic TLS certificates |
| tlsContext | object | Reference to a TLSContext resource for TLS configuration |
| tlsSecret | object | Reference to a Kubernetes TLS Secret containing certificates |
| requestPolicy | object | Policy for handling insecure requests |
| selector | object | Label selector for Mappings this Host should be associated with |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/HostSpec",
"title": "HostSpec",
"type": "object",
"description": "Specification for an Ambassador Host",
"required": [
"hostname"
],
"properties": {
"hostname": {
"type": "string",
"description": "Hostname that this Host resource applies to. Supports wildcard patterns like *.example.com.",
"example": "api.example.com"
},
"ambassador_id": {
"type": "array",
"description": "Ambassador IDs that should apply this Host",
"items": {
"type": "string"
},
"example": "500123"
},
"acmeProvider": {
"type": "object",
"description": "ACME certificate provider configuration for automatic TLS certificates",
"properties": {
"authority": {
"type": "string",
"description": "ACME server URL",
"example": "https://acme-v02.api.letsencrypt.org/directory"
},
"email": {
"type": "string",
"format": "email",
"description": "Email for ACME registration and certificate notifications"
},
"privateKeySecret": {
"type": "object",
"description": "Reference to a Kubernetes Secret for the ACME private key",
"properties": {
"name": {
"type": "string"
}
}
},
"registration": {
"type": "string",
"description": "ACME registration URL (automatically managed)"
}
},
"example": "example_value"
},
"tlsContext": {
"type": "object",
"description": "Reference to a TLSContext resource for TLS configuration",
"properties": {
"name": {
"type": "string",
"description": "Name of the TLSContext to use"
}
},
"example": "example_value"
},
"tlsSecret": {
"type": "object",
"description": "Reference to a Kubernetes TLS Secret containing certificates",
"properties": {
"name": {
"type": "string",
"description": "Name of the Kubernetes Secret"
}
},
"example": "example_value"
},
"requestPolicy": {
"type": "object",
"description": "Policy for handling insecure requests",
"properties": {
"insecure": {
"type": "object",
"properties": {
"action": {
"type": "string",
"description": "How to handle insecure (non-TLS) requests",
"enum": [
"Redirect",
"Reject",
"Route"
]
},
"additionalPort": {
"type": "integer",
"description": "Additional port to listen on for insecure requests"
}
}
}
},
"example": "example_value"
},
"selector": {
"type": "object",
"description": "Label selector for Mappings this Host should be associated with",
"properties": {
"matchLabels": {
"type": "object",
"additionalProperties": {
"type": "string"
}
}
},
"example": "example_value"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/ambassador-hostspec"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.