Generate a working file path from file tree template.

POST /data/tasks/{task_id}/working-file-path
Jwt authorization

Generate file path based on several parameters Revision can be computed automatically as next revision if not given.

Path parameters

  • task_id string(uuid) Required
application/json

Body Required

  • name string

    Default value is main.

  • mode string

    Default value is working.

  • software_id string(uuid)
  • comment string
  • revision integer
  • separator string

    Default value is /.

Responses

  • 200 application/json

    Working file path generated

    Hide response attribute Show response attribute object
    • path string
  • 400

    Malformed file tree

POST /data/tasks/{task_id}/working-file-path 
curl \
 --request POST 'http://api.example.com/data/tasks/a24a6ea4-ce75-4665-a070-57453082c25/working-file-path' \
 --header "Authorization: $API_KEY" \
 --header "Content-Type: application/json" \
 --data '{"name":"main","mode":"working","software_id":"a24a6ea4-ce75-4665-a070-57453082c25","comment":"Updated lighting","revision":1,"separator":"/"}'
Request examples 
{
  "name": "main",
  "mode": "working",
  "software_id": "a24a6ea4-ce75-4665-a070-57453082c25",
  "comment": "Updated lighting",
  "revision": 1,
  "separator": "/"
}
Response examples (200) 
{
  "path": "/project/asset/working/main_v001.blend"
}