No more product-photo ambiguity.
The public landing page, Lensora app route, docs and OpenAPI all point to the same narrow tool and the same endpoint.
Cleaner, not generative studio scenes
This page is for catalogue cleanup and layout rebuilding. It does not promise marble backgrounds, cinematic scenes, or old preset-based studio shots.
Seller metadata built in
Send article number, size range and footer text as form fields. The output is a clean listing/catalogue image for sellers and agencies.
Same endpoint everywhere
Website CTA, Lensora UI and API docs use /v1/image/product-photo-catalogue-clean.
API contract
image — JPG, PNG or WebP, max 20MBart_no, size_text, footer, output_format (jpeg, png, webp)GET /v1/image/{generation_id} or generation status endpoint in your SDK flowcurl -X POST https://api.pixelapi.dev/v1/image/product-photo-catalogue-clean \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "image=@catalogue-photo.jpg" \ -F "art_no=Art no. 1595" \ -F "size_text=M to 4XL" \ -F "footer=Three colour options shown | Folded catalogue view | Size range: M to 4XL" \ -F "output_format=jpeg"
Simple pricing
Use the same pay-as-you-go PixelAPI credits as the rest of the platform. Failed queue/inference jobs are refunded by the API where applicable.
$0.039 per image
No public page on PixelAPI should show the old 15-credit Product Photo price for this tool.
FAQ
Is this the old preset-based endpoint?
No. The public Product Photo experience is now the Marketplace Product Photo Cleaner using /v1/image/product-photo-catalogue-clean.
Can I still open it inside Lensora?
Yes. The app route is /app/#product-photo. Lensora copy now describes the catalogue cleaner, not the older multi-step studio-shot workflow.
What images work best?
Single product, apparel, accessory or packaged-good seller photos. Avoid multi-product collages when you need one clean catalogue subject.
Where are the docs?
Use /docs/product-photo for curl, Python and Node examples.