hosting

POST `/v1/storage/buckets`

Provision Zinn® storage, or attach a bucket of your own.

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати storage.manage бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

curl -X POST https://api.zinndigital.com/v1/storage/buckets \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "name": <string> }'

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

With ownership: zinn this provisions storage on our own backend and needs nothing else. With ownership: customer it attaches an existing S3-compatible bucket and requires bucket_name, endpoint, access_key_id and secret_access_key. The key pair is written to Vault and never to a column; the bucket is created pending and only becomes active once the write has returned, so a failure part way leaves a visibly unfinished bucket rather than one that reads as configured and cannot sign. Requires storage.manage.

Ҷисми дархост

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`name`	`string`	Бале	—
`ownership`	`string<zinn, customer>`	Не	—
`vendor`	`string<r2, s3, b2, bunny, gcore, minio>`	Не	—
`bucket_name`	`string`	Не	—
`endpoint`	`string`	Не	—
`region`	`string`	Не	—
`public_base_url`	`string`	Не	—
`access_key_id`	`string`	Не	Required for `ownership: customer`. Written to Vault, never to a column.
`secret_access_key`	`string`	Не	Required for `ownership: customer`. Written to Vault, never to a column.

Ҷавоб

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`id`	`string`	Бале	—
`name`	`string`	Бале	The customer's own label, not the bucket's name at the vendor.
`ownership`	`string<zinn, customer>`	Бале	`zinn` is storage we operate and bill for; `customer` is the organisation's own bucket, which costs us nothing and is not metered against their allowance.
`vendor`	`string<r2, s3, b2, bunny, gcore, minio>`	Бале	—
`status`	`string<pending, active, suspended, failed>`	Бале	—
`bucket_name`	`string`	Бале	—
`endpoint`	`string`	Не	—
`region`	`string`	Не	—
`public_base_url`	`string`	Не	Where a public object is readable. Empty means the bucket is private and its objects are reachable only through a presigned URL.
`bytes_stored`	`integer`	Не	—
`objects_stored`	`integer`	Не	—
`usage_measured_at`	`string`	Не	When the size above was last measured against the vendor. `null` means it has not been measured yet — which is not the same as empty.
`has_credential`	`boolean`	Бале	Whether a stored key exists. The key and the Vault path it lives at are deliberately absent from this payload.
`metered`	`boolean`	Бале	Whether this bucket's bytes count against `object_storage_gb`.
`created_at`	`string`	Не	—

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 422 · 429

POST /v1/storage/buckets