2. 400 - unknown table

The SQL parsed fine, but the table named in the FROM (or JOIN, or UPDATE) clause is not declared in any registered schema for this tenant. This is the SQL-layer mirror of a schema_not_found 404 - same root cause, different surface.

A SELECT against a table name that doesn't exist in the catalog.

curl -X POST "https://$OC_HOST/v1/tenants/$OC_TENANT/sql" \
  -H "Authorization: Bearer $OC_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"sql": "SELECT * FROM does_not_exist"}'

{
  "error": "unknown_table",
  "message": "table 'does_not_exist' is not declared in any schema for tenant",
  "retry": false
}

• List schemas for the tenant: GET /v1/tenants/:t/schemas. Find the one you meant.
• Table names are case-sensitive and fully qualified - shop.customers, not Customers.
• If the schema is missing entirely, register the manifest first via PUT /v1/tenants/:t/schemas/:id.
• retry: false - the same SQL will keep failing until the schema is in place.