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…
Where an upload stands (never finishes it)
Returns where an upload you started stands: status, parts_received for a multipart upload and, once finished, the file. It only reads and never finishes the upload. For a multipart version upload pass the multipart_id that startUpload returned. Needs files:write.
Do this with AI
I want to where an upload stands (never finishes it). Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/getupload.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/uploads/{id}curl --request GET \
--url https://tarkle.com/api/v1/uploads/3fa85f64-5717-4562-b3fc-2c963f66afa6 \
--header 'Authorization: Bearer $API_KEY' \
--header 'X-Workspace-Key: X-Workspace-Key'Path parameters
idstring · uuidrequiredAn upload id (uuid)
Query parameters
multipart_idstringFor a multipart version upload: the multipart_id that startUpload returned
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)