> ## Documentation Index > Fetch the complete documentation index at: https://docs.basaltic.sh/llms.txt > Use this file to discover all available pages before exploring further. # Get bucket lifecycle configuration ## OpenAPI ````yaml /api-reference/specs/storage.yaml get /v1/buckets/{bucket}/lifecycle openapi: 3.0.3 info: title: Basaltic Storage API version: 1.0.0 description: | Block volumes with their snapshots and snapshot policies, plus bucket management for object storage. The S3 wire protocol itself is served separately at `objects.{region}.basaltic.cloud`. contact: name: Basaltic Support email: ping@basaltic.sh license: name: Proprietary url: https://basaltic.sh/terms servers: - url: https://storage.{region}.basaltic.sh description: Regional API endpoint variables: region: default: sa-saopaulo-1 description: Region code security: - SignatureAuth: [] paths: /v1/buckets/{bucket}/lifecycle: parameters: - name: bucket in: path required: true schema: type: string example: my-app-assets get: tags: - Buckets summary: Get bucket lifecycle configuration operationId: getBucketLifecycle responses: '200': description: Current lifecycle configuration. content: application/json: schema: $ref: '#/components/schemas/BucketLifecycleResponse' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: No lifecycle configuration is set on this bucket. security: - SignatureAuth: [] components: schemas: BucketLifecycleResponse: type: object required: - lifecycle properties: lifecycle: $ref: '#/components/schemas/LifecycleConfig' LifecycleConfig: type: object required: - rules properties: rules: type: array items: $ref: '#/components/schemas/LifecycleRule' Error: type: object required: - error properties: error: type: object required: - code - message - request_id properties: code: type: string description: Error code identifying the type of error example: INVALID_INPUT message: type: string description: Human-readable error message example: Invalid request parameters request_id: type: string format: uuid description: Request ID for debugging example: 550e8400-e29b-41d4-a716-446655440000 LifecycleRule: type: object required: - status properties: id: type: string example: expire-old-logs status: type: string description: >- `disabled` keeps the rule in the configuration but skips it during evaluation. The S3-compatible endpoint spells the same states `Enabled` / `Disabled` in its XML. enum: - enabled - disabled example: enabled filter: type: object properties: prefix: type: string example: logs/ transition: type: object description: >- Move matching objects to another storage class once they are old enough. The object keeps its identity — same key, same version id, same last-modified — and only its bytes move between pools, so pairing a transition with an expiration works: the expiry clock is not restarted by the move. Exactly one of `days` or `date`. When the rule also has an `expiration`, the transition must come strictly first, otherwise the object would be deleted before it ever moved and the rule is rejected. Only one transition per rule: the platform serves two classes, so a second has nowhere to go. The S3-compatible endpoint accepts a single-element `` list and rejects longer ones rather than silently applying the first. required: - storage_class properties: days: type: integer minimum: 1 description: Days after the object's last-modified time. example: 30 date: type: string format: date-time description: Absolute cut-off; fires on the next sweep after this instant. storage_class: type: string description: >- Destination class. Keeps the S3 standard's casing rather than the platform's lowercase convention, because the class vocabulary is S3's. Unsupported values are rejected — a transition to a class that does not exist would silently never run. enum: - STANDARD - COLD example: COLD expiration: type: object properties: days: type: integer example: 30 date: type: string format: date-time noncurrent_version_expiration: type: object properties: noncurrent_days: type: integer example: 7 newer_noncurrent_versions: type: integer example: 3 abort_incomplete_multipart_upload: type: object properties: days_after_initiation: type: integer example: 7 responses: Unauthorized: description: Authentication required or token invalid content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: UNAUTHORIZED message: Authentication required request_id: 550e8400-e29b-41d4-a716-446655440000 Forbidden: description: Insufficient permissions content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: ACCESS_DENIED message: You don't have permission to perform this action request_id: 550e8400-e29b-41d4-a716-446655440000 securitySchemes: SignatureAuth: type: apiKey in: header name: Authorization description: > Request signing with an access key issued to a service account. An HMAC-SHA256 over a canonical form of the request, close to AWS SigV4. The `basaltic` CLI signs for you. Send `Authorization`, `X-Date` (UTC, `YYYYMMDDTHHMMSSZ`) and `X-Nonce` (random per request); add `X-Content-Sha256` to bind a body, and `X-Amz-Security-Token` when using temporary credentials. ``` Authorization: BASALTIC-HMAC-SHA256 Credential=///basaltic/basaltic_request, SignedHeaders=host;x-date;x-nonce, Signature= ``` `` is the region code you are calling, or `global` for the global services. A signature is valid for 5 minutes from `X-Date`, and mutating requests are replay-guarded on the nonce. **Full signing procedure, including a working implementation:** https://docs.basaltic.sh/authentication ## Rate limits There is no global request budget. A limit applies only where an operation documents a `429`, and that operation says what it counts. Those responses carry `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset` and, on a `429`, `Retry-After` — read them rather than hard-coding a number. Retrying before `Retry-After` is refused and extends the window. Everything else is bounded by quota, not by request rate. ````