The UUID does not change
Renaming changes the name and nothing else. The UUID stays as it was, so a render request already in production goes on working and nothing you have stored against that identifier needs touching. That is the reason a badly named template is worth renaming rather than uploading again: a fresh upload would hand you a new UUID to chase through your integration.Why templates arrive badly named
A template uploaded in the browser takes the file name it came with, which is why a library filled from a folder of exports often reads as a column of serial numbers. A template uploaded over the API takespsd_name, up to 255
characters, and is given a name derived from the filename when you send none.
The name is what the library search matches, so the half minute spent here comes
back the first time you look for one template among two hundred.
Renaming over HTTP
The same edit runs over the API. Send the new name to Update an existing PSD mockup, or to Update an existing photo mockup for one built from a product photo.name runs between 1 and 255 characters, and
both routes answer with the record they just changed rather than a bare
acknowledgement, so you confirm the change without a second call. The same call also carries the
template’s colour list, so a rename and a colour change travel together when you
send both.
Listing templates afterwards takes the name as a handle too. name matches a
fragment and ignores case, and sort accepts name alongside created_at and
updated_at. Pagination covers walking a long list.
Everyone sees the same name
The library belongs to the organization rather than to the person who uploaded, so a rename is immediately what every member sees, in the browser and over the API alike. Agree a naming convention early when more than one person uploads, because the search field is only as good as the names in it.Learn more
- My mockups for the rest of the library, including colours, bulk upload and deletion.
- Upload a PSD for naming a template as it arrives.