API Integration - GenPsd Docs

API reference

Parameter	`picurl`
Value	A publicly reachable image URL. URL must use `https://`
Behavior	Opens the editor, fetches the image, and creates a new project. On success, `picurl` is removed from the address bar.
Locales	Supported path prefixes (`locale`): `/zh-cn/` 简体中文、 `/zh-tw/` 繁體中文、 `/ja/` 日本語、 `/ko/` 한국어、 `/en/` English。 You may also use `/`; the site redirects by browser language and `genpsd-locale`, keeping `picurl`.

Option 1: No locale prefix (auto language)

Use the site root; first visit follows system language. If the user switched language before, that preference wins.

Option 2: Locale prefix (fixed UI language)

Add a locale prefix to open that language UI. Replace en in the examples with any prefix from the table.

Use cases

E-commerce — Link “Edit in GenPsd” from product pages with main or scene image URLs.
Assets / DAM — Open selected assets with picurl for layering and export.
AI output / tickets — Pass generated image URLs into GenPsd for quick edits and layers.
Support / collaboration — Backend builds GenPsd links from user-submitted image URLs.

Integration steps

Prepare an HTTPS direct image URL (response must be an image, not HTML).
Ensure CORS allows the browser (Access-Control-Allow-Origin includes www.genpsd.com or *).
encodeURIComponent the image URL and append it as picurl.
Open the full URL in a new tab or iframe; users can separate layers and export PNG / JPG / WEBP / PSD / PPTX.

Note: Without CORS the browser blocks the fetch. Use a same-origin proxy or manual upload.

Examples

Example 1: Fixed template

Store a GenPsd entry URL on your side and swap the image parameter:

Example 2: JavaScript

const imageUrl = "https://cdn.example.com/sku/banner-image.jpg";
const entry = new URL("/en/", "https://www.genpsd.com");
entry.searchParams.set("picurl", imageUrl);
window.open(entry.href, "_blank", "noopener,noreferrer");

Example 3: HTML button

FAQ

If both picurl and project are present, picurl wins and creates a new project.
Only standard image responses are supported; PDFs or web pages will fail.
Layer processing runs locally; projects stay in the user’s IndexedDB, not on your servers.
For integration, private deployment, or batch processing, email encoyang@gmail.com with your use case, expected volume, and target locales. We reply on business days.