Foldkit
Your customers design their own boxes on your site, in 3D, and you get print-ready files.
Foldkit is a packaging designer you put inside your own product. A customer picks a box style, sets its dimensions, lays out artwork on a flat dieline that maps live onto an interactive 3D box, and you receive a design you can render as SVG, DXF, a dieline PDF or a print-ready PDF/X-4.
It runs in an iframe on your page, under your brand, with your catalog. Your customers never see ours.
Pick an integration shape
There are two, and the only question that separates them is whether you have a backend that can hold a secret.
| Publishable key | Session token | |
|---|---|---|
| You need | A key pasted into your page | A backend endpoint that mints a token |
| We know your customer as | Anonymous | Your own id (externalUserId) |
| Designs are | Reachable by whoever holds the id | Scoped to the customer you named |
| Works from | Origins you have verified, and nowhere else | Anywhere your backend serves |
| Time to first render | Minutes | An afternoon |
Start with the publishable key — it is what the quickstart uses, and you can move to session tokens without changing the page. The sandbox gives you both, pre-provisioned, with no account.
What you get back
- A design id, the moment the customer saves — over a
savedevent in the page, and over adesign.savedwebhook to your backend. - A preview image at
GET /v1/designs/:id/preview.png, for the cart line and the order confirmation. - Print files — SVG, DXF, a dieline PDF, or PDF/X-4 with bleed, crop marks and an ICC profile — rendered on request and delivered as a signed URL.
The rest of these docs
Concepts
- Concepts — Tenants, keys, embed sessions, permissions, and designs versus documents.
- Security & data handling — Isolation, what a leaked key is worth, retention, deletion and export.
Integrate
- SDK (recommended) — Mount the editor, drive it, listen to it.
- Server-to-server — Mint session tokens, read designs back, render print files from your backend.
- Raw iframe — No script tag at all — and the one parameter it needs.
- Webhooks — Subscribe, verify a signature in three languages, survive a rotation.
- Branding — What is themeable, what is not, and why.
- Configuration — Styles, materials, export formats, limits and feature flags.
Reference
- SDK reference — Every option, command, event and error the SDK exposes.
- API reference — Every `/v1` operation, generated from the contract itself.
- Errors & troubleshooting — Every error code, what causes it, and the one thing to check first.
- Changelog & deprecation policy — What changed, and what we promise not to break.
- Status — Live status of the API, editor, exports and webhooks.