> ## 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. # Which mockup type to use, a PSD template or a product photo > Let the files you already own pick the mockup type. The answer is usually settled before you write any code, by what you already have on disk. Both types sit behind the same API key, take the same export options and report to the same webhook endpoints under their own event names, so one catalogue can hold both and your integration differs only in which two endpoints it calls. ## Choose a PSD template when you own the layered file A Photoshop file carries work a designer already did: the warp curving a print around a mug, the shadow falling across a fold, the mask trimming artwork to a frame, the blend mode letting fabric texture through. All of it renders as authored, so realism is a property of the file rather than something you tune request by request. [Preparing a PSD](/docs/psd-mockups/preparing-a-psd) is where that work gets done. The file also gives you the widest set of things to change per render. One template covers the artwork in any of its design areas, the wording on a live text layer, a colour overlay and adjustments on a design area, group outlines, and the export format and pixel size. That is what makes a single PSD enough for a colour range, or for names printed across hundreds of personalised items. ## Choose a photo mockup when a photograph is all you have Plenty of products never came with a layered file. A [photo mockup](/docs/photo-mockups/overview) turns one product photograph into a template you keep and render onto for as long as you want it. Send the photograph as a URL or as base64 and the printable areas come back prepared. If you already know where artwork belongs, send your own convex four point areas with the same call, up to eight of them, and they are used exactly as given. A render then names up to eight targets. A print area places artwork inside a bounded zone such as a chest panel or a poster face, and a product surface prints across the whole item, which is how an all over print is done. Drawing a print area does not take the surface away, so one photograph carries both. [Print areas and surfaces](/docs/photo-mockups/print-areas) reads the two lists field by field. ## Side by side | | PSD template | Photo mockup | | - | - | - | | You start from | A layered Photoshop file | One product photograph | | Placement comes from | Smart objects the designer built | Areas prepared for you, or corner points you send | | Changes per render | Artwork, live text, colour overlay, adjustments, group outlines, export | Artwork, placement, adjustments, export | | Setup | Registering the template costs nothing | Creating the mockup is charged once | | Every render | Charged per image | Charged per image | The credit weight of each operation differs, and the current numbers are on [pricing](https://sudomock.com/pricing). ## If you would rather not build the template Our team can prepare templates for your catalogue. Write to [support](https://sudomock.com/contact) with the product and an image showing where the print goes, and the mockup comes back ready to render against. ## Learn more One photograph, from the create call to a finished render. One template, from upload to a batch of images. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.