Hey, human!
HTTP/2 200 OK content-type: text/markdown; charset=utf-8 vary: accept, user-agent x-agent: [ai_agent]
Loading the agent response…
Remove a file from a brand
Takes one file off the brand and deletes the stored file unless something of the brand still uses it. Send slot as a query parameter. icon, main_logo, banner, social_image and favicon need only the slot. logo needs id (the logo id from listBrandAssets), asset needs id (the collection file id from listBrandAssets), team_photo needs member_id (or member_name when the member has no id) and guideline_image needs section_id and id (the image id from the brand's guidelines). It is the editor's own all-or-nothing save. Nothing there is 404 not_found; older-editor images on the brand block asset removal (409). Needs brands:files.
Do this with AI
I want to remove a file from a brand. Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/removebrandfile.md Authenticate with your API key as a Bearer token in the Authorization header. Then make the request for me and tell me what came back.
Paste this into Claude, Cursor, or any AI assistant and it will do it for you.
https://tarkle.com/api/v1/brands/{brand}/filescurl --request DELETE \
--url 'https://tarkle.com/api/v1/brands/brand/files?slot=icon' \
--header 'Authorization: Bearer $API_KEY' \
--header 'X-Workspace-Key: X-Workspace-Key'Path parameters
brandstringrequiredBrand id (uuid) or slug
Query parameters
slotstringrequiredicon, main_logo, banner, social_image, favicon, logo, asset, team_photo or guideline_image
idstringlogo, asset and guideline_image: the id of the file
member_idstringteam_photo: the team member's id
member_namestringteam_photo: the member's name, when the member has no id
section_idstringguideline_image: the guideline section's id
workspace_keystringThe same key as the X-Workspace-Key header, for clients that cannot set headers. Send one of the two, or both with the same value (different values are 400 conflicting_workspace)
Header parameters
X-Workspace-KeystringrequiredThe 8-character key of the workspace this call acts on; GET /workspaces lists the keys a token can use. A workspace id is refused (400 workspace_key_required)
Idempotency-KeystringMakes a write safe to repeat. Send a random value (a UUID is fine) of up to 255 visible characters. A repeat of the same request gets the first answer again, with the header `Idempotent-Replayed: true`, and does nothing twice. The same key for a different request is 422 `idempotency_key_reused`; the same request while the first one is still running is 409 `idempotency_in_progress`. A 5xx or 429 is not remembered, so retrying it runs the request again. Keys last 24 hours and belong to the account that created the token.