Namespaces

Namespaces organize MCP process servers. Each namespace maps to its own Postgres schema, which HotMesh uses for workflow execution. Deploying a YAML workflow registers its namespace.

All endpoints require authentication.

List namespaces

GET /api/namespaces

Returns every registered namespace.

Example request

curl -s https://lt.acme.dev/api/namespaces \
  -H "Authorization: Bearer $LT_TOKEN"

Response 200

{
  "namespaces": [
    {
      "id": "a1b2c3d4-...",
      "name": "lt-yaml",
      "description": "YAML workflow process server",
      "schema_name": "lt-yaml",
      "is_default": false,
      "metadata": null,
      "created_at": "2025-01-01T00:00:00Z",
      "updated_at": "2025-01-01T00:00:00Z"
    }
  ]
}

Register a namespace

POST /api/namespaces

Creates a namespace, or returns the existing one with the same name. YAML workflow deployment calls this for you.

Auth: Requires builder access (superadmin or the engineer role).

Request body

Field	Type	Required	Description
name	string	Yes	Unique namespace name (becomes the HotMesh app ID and schema name).
description	string	No	Human-readable description.
metadata	object	No	Arbitrary metadata.

Example request

curl -s https://lt.acme.dev/api/namespaces \
  -X POST \
  -H "Authorization: Bearer $LT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "lt-yaml", "description": "YAML workflow process server"}'

Response 200: The namespace record (created or existing).

Response 400: name is missing.