Autional Autional
API Reference GitHub autional.com →

POST /admin/storage/buckets

Create a new storage bucket (logical record + MinIO physical bucket) for the current tenant, with visibility (private/public/temp) and description. Default bucket cannot be deleted. Reference: GDPR Art 32 (Security of Processing).

Storage Service `bearerAuth` application/json

Request Body

Schema: dto.CreateBucketRequest

FieldTypeRequiredExampleConstraintsDescription
name string Yes
description string No
visibility string No

Responses

StatusDescriptionSchema
201Created successfully, returns bucket detailsdto.BucketDetailResponse
400Parameter validation failed or bucket name already existsdto.Problem
401Unauthenticated or token expireddto.Problem
403Insufficient permissions, admin role requireddto.Problem
404Tenant not founddto.Problem
500Internal server error (MinIO operation failed, etc.)dto.Problem

Referenced Schemas

dto.BucketDetailResponse

FieldTypeRequiredExampleConstraintsDescription
code integer No
data dto.BucketResponse No
message string No
timestamp string No

dto.BucketResponse

FieldTypeRequiredExampleConstraintsDescription
created_at string No
description string No
id string No
is_default boolean No
name string No
physical_name string No
visibility string No

dto.FieldViolation

FieldTypeRequiredExampleConstraintsDescription
code string No Code is the error code (optional). Used for programmatic identification of error types, e.g., "required", "format", "range"
description string No Description is a human-readable error description. Should explain what rule was violated, e.g., "Must be a valid email address"
field string No Field is the path to the error field. Uses dot notation for nested fields, e.g., "user.email" or "addresses[0].city"
value object No Value is the value that caused the error (optional, used in development mode). May not be returned in production to avoid leaking sensitive information.

dto.Problem

FieldTypeRequiredExampleConstraintsDescription
code integer No Code is the business error code. Used for programmatic handling of specific error scenarios. Example: 30101001
detail string No Detail is a human-readable explanation for this specific error instance. May contain specific error details, e.g., "Field 'email' is required"
errors array of

See dto.FieldViolation

No Errors is a list of field-level validation errors (extension field). Follows Web API standard practice, each error contains field name and error message.
i18n_args object No I18nArgs are internationalization parameters. Used for dynamically filling translation templates.
i18n_key string No I18nKey is the internationalization key. Used for client-side localization of error messages. Example: "error.user_not_found"
instance string No Instance is the specific URI reference where the problem occurred. Usually the request URL, may include query parameters. Example: "/api/v1/users?limit=invalid"
request_id string No RequestID is the unique request identifier. Used for log correlation and issue tracking. Example: "req_550e8400-e29b-41d4-a716-446655440000"
retry_after integer No RetryAfter is used for 429 Too Many Requests responses. Indicates how many seconds the client should wait before retrying (RFC 6585).
service string No Service is the service name. Used in microservice architecture to locate the error source. Example: "auth-service"
span_id string No SpanID is the current span identifier. Used for precise location of the current node in a distributed trace.
status integer No Status is the HTTP status code produced. Used by clients to distinguish problem types, does not change with Accept-Language. Example: 400, 401, 403, 404, 500
timestamp string No Timestamp is the error occurrence time. ISO 8601 format. Example: "2026-04-03T12:00:00Z"
title string No Title is a short, human-readable summary of the problem type. The same Type should always have the same Title (does not vary by instance). Example: "Invalid Request Parameters"
trace_id string No TraceID is the distributed trace identifier. Follows W3C Trace Context standard. Example: "00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01"
type string No Type is a URI reference that identifies the problem type. When dereferenced, it should provide human-readable documentation. Example: "https://api.example.com/errors/invalid-request"