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…
Fresh signed URLs for a range of parts (from_part, count up to 100)
Returns fresh signed URLs for a range of parts of a multipart upload: from_part (default 1) and count (default 20, up to 100). Use it when the first URLs have expired or to sign the next batch. A single-part upload answers 409 not_multipart; an expired upload 410. Needs files:write.
What you provide
- From partoptional: The first part number to sign; at most part_count
- Countoptional: How many parts to sign
- Multipart idoptional: For a multipart version upload: the multipart_id that startUpload returned
Do this with AI
I want to fresh signed URLs for a range of parts (from_part, count up to 100). Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/signuploadparts.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}/partscurl --request POST \
--url https://tarkle.com/api/v1/uploads/3fa85f64-5717-4562-b3fc-2c963f66afa6/parts \
--header 'Authorization: Bearer $API_KEY' \
--header 'Content-Type: application/json' \
--header 'X-Workspace-Key: X-Workspace-Key' \
--data '
{
"from_part": 1,
"count": 20,
"multipart_id": "multipart_id"
}
'Path parameters
idstring · uuidrequiredAn upload id (uuid)
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/jsonfrom_partintegerThe first part number to sign; at most part_count
countintegerHow many parts to sign
multipart_idstringFor a multipart version upload: the multipart_id that startUpload returned