Your naming template
Needs the scope settings:write
How files are named for your account, with an example.
OK
application/json- response
preset*stringstandard: {articleId}{type}{view}_{n}.{ext}, and {articleId}.{ext} for 3D files. gs1: the GS1 Product Image Standard release 5.0, from the product's GTIN (a second image with the same codes gets _s02, scenes and spins are always numbered); the images of a product without a GTIN are named as standard, and a job with gs1 names for it is refused. amazon: {articleId}.MAIN for the main image and PT01, PT02 and so on for the rest; videos and 3D files as standard. custom: your own pattern.
"standard""gs1""amazon""custom"pattern?stringWith preset custom: a pattern from the tokens {articleId}, {externalId}, {gtin}, {variant}, {type}, {view}, {n}, {n:2}, {width}, {height}, {date}, {attr:key} and {ext}.
length <= 200example*stringWhat a front packshot of CH-1001 would be called.
curl -sS https://platform.charpstar.co/api/v1/naming \ -H "Authorization: Bearer $CHARPSTAR_API_KEY"{ "preset": "standard", "example": "CH-1001_packshot_front_1.png"}Your saved scene styles GET
The saved scene styles of your account, so a whole range shares one look: our team makes them with you. Name one in a scene job's options.style.
Set your naming template PUT
Set the naming template for every file we produce for you: the standard pattern, the GS1 Product Image Standard, Amazon's MAIN and PT01 scheme, or your own pattern from the tokens. - Override it per job with the job's naming. - File names use letters A to Z, digits, '-', '_' and '.', up to 200 characters; accented letters are converted. - The same output always gets the same name, so an updated image replaces the earlier file.