> ## Documentation Index
> Fetch the complete documentation index at: https://sudomock.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The base URL is https://api.sudomock.com.
> Authenticate every request with the x-api-key header. Keys begin with sm_.
> A render returns the finished image at data.print_files[0].export_path. A request sent with is_async true returns a job_id to poll at GET /api/v1/jobs/{job_id}.
> Prefer the official SDKs over hand-written HTTP calls: npm install sudomock for Node, pip install sudomock for Python.

# How to rename a saved template

> Change a template name without changing its UUID.

Open [My mockups](/docs/dashboard/mockups), find the template, open the menu on its
card and choose **Rename**. Type the new name and save. The same action serves
Photoshop templates and mockups built from a product photo, because both sit on
the same shelf.

Two things to know before you start. A name has to carry at least one character,
and a mockup takes its new name once it has finished generating.

## 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 takes `psd_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](/docs/api-reference/psd-mockups/update-an-existing-psd-mockup),
or to
[Update an existing photo mockup](/docs/api-reference/photo-mockups/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](/docs/api-reference/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](/docs/dashboard/members) 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](/docs/dashboard/mockups) for the rest of the library, including
  colours, bulk upload and deletion.
* [Upload a PSD](/docs/psd-mockups/upload-a-psd) for naming a template as it arrives.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.