Remove a child site
const url = 'https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/storage-links/a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d/children/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15';const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/storage-links/a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d/children/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15 \ --header 'Authorization: Bearer <token>'Removes a child from the configuration. The site flips back to its own storage, with the data it set aside when it was linked.
How it works
The change is saved before any site is redeployed; redeploy reports whether the immediate redeploys landed, and the sync retries any that did not. The site cannot be deleted or added elsewhere until it has been redeployed.
Required permissions
team:manage_storage_links:writeon the team
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Unique id (UUID) of the team that owns the addressed resources, as shown in the team settings on the Blotout platform.
Example
7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9Unique id (UUID) of the team that owns the addressed resources, as shown in the team settings on the Blotout platform.
Unique id (UUID) of the storage link configuration.
Example
a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5dUnique id (UUID) of the storage link configuration.
Unique id (UUID) of the child site.
Example
3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15Unique id (UUID) of the child site.
Responses
Section titled “Responses”The child was removed.
object
Outcome of the immediate redeploys; a failed one is retried by the sync, so the change is saved either way.
object
Whether every affected site was redeployed at once.
Why a redeploy was left to the sync, or null.
Example
{ "redeploy": { "redeployed": true, "reason": null }}invalid_params — A path parameter failed validation (for example a malformed UUID); details pinpoints the offending parameter.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Field-level validation errors: a tree keyed by input property, each node carrying an errors array of human-readable messages. Render it to help the caller correct the request.
object
Example
{ "error": "invalid_params", "details": { "errors": [], "properties": { "teamId": { "errors": [ "Invalid UUID" ] } } }}unauthenticated — The Authorization: Bearer token is missing, malformed, or no longer valid. Generate a team API token or obtain a new OAuth access token.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "unauthenticated"}forbidden — The bearer credential lacks the required permission or belongs to another team, or its user lacks the organization role a developer operation needs. Update its policies, use a credential bound to the addressed team, or ask an organization owner for the role; message states the reason when one is known.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Human-readable reason for this specific failure, intended for display — do not parse it programmatically.
Example
{ "error": "forbidden", "message": "The Cloudflare API token is invalid or expired."}not_found — The addressed resource does not exist within this team; check the id and retry.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "not_found"}internal — Unexpected server error. Nothing is guaranteed to have been persisted; idempotent operations are safe to retry.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "internal"}