Frequently asked questions
Short answers about access, pricing, image quality, limits, data and what the API does not do yet.
Updated
Access and pricing
Can I use the API today?
It is in early access. Tell us about your catalog and the system it lives in, and we will switch it on for your workspace.
What does it cost?
Each render is 1 credit, from the same credits your workspace uses in the app. Adding scenes and upscaling are free, and a render that fails costs nothing. See Credits and billing and Pricing.
Is there a test mode?
Not yet. Every render made through the API is real and spends a credit, and failed renders are given back. To check a key or your setup without spending anything, call Retrieve your account, or list your scenes and products.
Who can make keys?
Workspace owners and admins, under Settings, in Developers. See Manage API keys.
Images and quality
What resolution are the images?
4K, as PNG or JPEG (kept as the model made it), in the aspect ratio closest to the scene’s picture. See Image output and links.
Can I get upscaled images?
A request can ask for one with upscale: true, at no extra credit, and each render says in upscale_status whether it got one. See Upscaling.
Do I need 3D models of my products?
No. A flat swatch or a clear product image is enough. The preparation guides show what works best for each kind of product.
How long does a render take?
Most finish in about 20 to 60 seconds once they start. Times vary with the image and how busy the service is, and none is guaranteed. Large batches are worked through a few renders at a time.
How long do image links last?
At least 30 days. Download each image when its render completes, and fetch the render again if you need a fresh link. See Image output and links.
Can one render show several products?
Each render puts one product, or one paint color, on one surface of a scene. Scenes you build in the app’s Editorial mode are listed by List all scenes too, and can be rendered into like any other.
Building with the API
Are there SDKs?
Not yet. There is ready-to-paste client code for Node.js and Python, and the OpenAPI specification generates a client in most other languages.
Are there webhooks?
Not yet. You poll a render or a scene until it reaches a final status. See Poll for results.
Can I add products through the API?
Not yet. Add products to your catalog in the app, then render them through the API by id. Paint colors need no product at all: send a hex value. See Paint colors.
Can a retry charge me twice?
Not if you send an Idempotency-Key with every render request: the same key and body are charged once, however often they are sent. See Idempotent requests.
How many renders can I send at once?
Up to 100 in one request, and as many requests as your rate limit allows. See Render in batches.
Can I call the API from a browser or a mobile app?
No. A secret key must stay on your servers. To put Skip Shoot in front of shoppers, use the website visualizer, which has its own key that is safe in a web page.
Your data
Who owns the images?
You do. The Terms of service say renders made from your content are yours, and Skipshoot LLC claims no ownership of them.
Do you train AI on my images?
No. We do not use your content to train or fine-tune AI models. The Privacy Policy explains how images are handled.
Where do API renders show up?
In your workspace’s gallery in the app, marked as made by the API, so your team can find, share and download them.
Something these pages do not answer? Email admin@skipshoot.com and we’ll help.
