API Reference
API Reference
Complete REST API documentation for Bingsan, compliant with the Apache Iceberg REST Catalog specification
API Reference
Complete REST API documentation for Bingsan, compliant with the Apache Iceberg REST Catalog specification.
Base URL
http://localhost:8181/v1Authentication
When authentication is enabled, include the bearer token in requests:
curl -H "Authorization: Bearer <token>" http://localhost:8181/v1/namespacesSee Authentication Configuration for details.
Content Type
All requests with a body should use:
Content-Type: application/jsonAPI Sections
Core Operations
- Namespaces - Namespace CRUD operations
- Tables - Table management and commits
- Views - View management
Error Responses
All error responses follow this format:
{
"error": {
"message": "Error description",
"type": "ErrorType",
"code": 400
}
}Common Error Types
| Code | Type | Description |
|---|---|---|
| 400 | BadRequestException | Invalid request parameters |
| 401 | UnauthorizedException | Missing or invalid authentication |
| 403 | ForbiddenException | Permission denied |
| 404 | NoSuchNamespaceException | Namespace not found |
| 404 | NoSuchTableException | Table not found |
| 404 | NoSuchViewException | View not found |
| 409 | AlreadyExistsException | Resource already exists |
| 409 | CommitFailedException | Optimistic locking failure |
| 500 | ServerError | Internal server error |
Catalog Prefix
Bingsan supports prefixed API paths for multi-catalog deployments:
/v1/{prefix}/namespaces
/v1/{prefix}/namespaces/{namespace}/tablesExample:
curl http://localhost:8181/v1/my-catalog/namespaces