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…
Fill a Word template into a new .docx ({placeholders}, lists, repeated table rows)
The file in the path is a Word (.docx) template with {placeholders}; it is never changed. `values` maps each placeholder name to text, or to a list of rows ([{ item: 'Setup', price: '100' }]) for a repeated block or table row. Every placeholder must have a value and every value a placeholder: otherwise 422 unprocessable_file with details.missing, details.unused and details.placeholders (the template's own placeholder names). Placeholder names are used exactly as sent (they are never renamed). name and folder_id choose the new file (default '<template> (filled).docx' next to the template). Needs files:write; 20 calls a minute per token.
What you provide
- Values: Each placeholder name (exactly as written in the template) to text, or to a list of rows for a repeated block
- Nameoptional: The new file's name; default '<template> (filled).docx'
- Folder idoptional: The folder; omitted keeps the template's folder
Do this with AI
I want to fill a Word template into a new .docx ({placeholders}, lists, repeated table rows). Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/filltemplate.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/files/{id}/fill-templatecurl --request POST \
--url https://tarkle.com/api/v1/files/id/fill-template \
--header 'Authorization: Bearer $API_KEY' \
--header 'Content-Type: application/json' \
--header 'X-Workspace-Key: X-Workspace-Key' \
--data '
{
"values": {},
"name": "name",
"folder_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}
'Path parameters
idstringrequiredA file id (digits) or a folder 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/jsonrequiredvaluesobjectrequiredEach placeholder name (exactly as written in the template) to text, or to a list of rows for a repeated block
namestringThe new file's name; default '<template> (filled).docx'
folder_idstring · uuid | nullThe folder; omitted keeps the template's folder