How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Table Format Namespaces API

Namespace (database/schema) management

Table Format Namespaces API is one of 8 APIs that Table Format publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Namespaces. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against a single base URL, https://{catalog-host}.

5 operations 3 paths 7 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://catalog-service/
Authentication
HTTP Bearer, OAuth 2.0
License
Resource Areas
1

Authentication & Security 2

Table Format Namespaces API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Namespaces 5

Namespace (database/schema) management

GET
/v1/namespaces
List Namespaces
listNamespaces 3 params → 200401
POST
/v1/namespaces
Create Namespace
createNamespace body → 200409
GET
/v1/namespaces/{namespace}
Get Namespace Metadata
loadNamespaceMetadata 1 param → 200404
DELETE
/v1/namespaces/{namespace}
Drop Namespace
dropNamespace 1 param → 204404
POST
/v1/namespaces/{namespace}/properties
Update Namespace Properties
updateNamespaceProperties 1 param body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are UpdateNamespacePropertiesResponse (3 properties), GetNamespaceResponse (2 properties), ListNamespacesResponse (2 properties), CreateNamespaceRequest (2 properties). Each schema is shown below with its type and property counts.

UpdateNamespacePropertiesRequest
object
2 properties
IcebergErrorResponse
object
1 property
UpdateNamespacePropertiesResponse
object
3 properties
CreateNamespaceResponse
object
2 properties
CreateNamespaceRequest
object
2 properties 1 required
ListNamespacesResponse
object
2 properties
GetNamespaceResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

table-format-namespaces-api-openapi.yml Raw ↑

Other APIs Table Format publishes across the network.

Delta Lake
Apache Hudi
Table Format Commits API
Table Format Configuration API
Table Format OAuth2 API
Table Format Tables API
Table Format Views API
Where this information came from

This is an independent, third-party profile of Table Format Namespaces API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.