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…
Import a brand file from a web address
Both upload steps in one call, for a picture that is already on the web (a logo returned by lookupBrandFromDomain, say). Send slot and url (https, public) and, for logo or asset, the fields completeBrandFileUpload takes. The server fetches the address (public hosts only, redirects checked), stores it and attaches it with the same checks as an upload: size, type and real content. An address that is not a public image, is too large or fails the checks is 422 invalid_file and nothing is attached. Returns the attached file (201). Needs brands:files.
What you provide
- Slot
- Url: The https address of a public image
- Nameoptional
- Typeoptional
- Usageoptional
- Collection idoptional
- Collection nameoptional
- Member idoptional
- Member nameoptional
- Section idoptional
- Kindoptional
- Captionoptional
Do this with AI
I want to import a brand file from a web address. Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/importbrandfile.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}/files/importcurl --request POST \
--url https://tarkle.com/api/v1/brands/brand/files/import \
--header 'Authorization: Bearer $API_KEY' \
--header 'Content-Type: application/json' \
--header 'X-Workspace-Key: X-Workspace-Key' \
--data '
{
"slot": "icon",
"url": "url",
"name": "name",
"type": "type",
"usage": "digital",
"collection_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"collection_name": "collection_name",
"member_id": "member_id",
"member_name": "member_name",
"section_id": "section_id",
"kind": "image",
"caption": "caption"
}
'Path parameters
brandstringrequiredBrand id (uuid) or slug
Query parameters
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.
Body
application/jsonrequiredslotstringrequiredurlstringrequiredThe https address of a public image
namestringtypestringusagestringcollection_idstring · uuidcollection_namestringmember_idstringmember_namestringsection_idstringkindstringcaptionstring