ThreadProof Embroidery APIRead-only endpoints live

The ThreadProof Embroidery API

The same engine behind ThreadProof, exposed as an API. The full vision: POST your artwork, get back an analysis, stitch-plan candidates, a simulated stitch-out, and validated machine files. Today three read-only reference endpoints are live; the hosted compile step is on the roadmap — and we'll tell you exactly where each piece stands.

The vision

A single POST turns artwork into machine-ready, proven embroidery files — the browser flow, as a hosted pipeline.

POST artwork Analysis Stitch candidates Simulation Validated machine files
Honest status: the digitizing and compile engine runs entirely in your browser today (HTML canvas). There is no server-side render yet, so the compile endpoint returns 501 not_implemented rather than pretending to run. The read-only endpoints below genuinely work server-side right now.

Available now — read-only reference

Static, zero-dependency JSON. No auth, no rate limit today, cache disabled. These mirror the values the browser engine uses, so your integration and the web tool always agree.

GET/api/v1/formats

Every machine file format ThreadProof knows about and how far along each one is: available exports today, beta exports but isn't fully round-trip verified, roadmap isn't built yet.

Example response
{
  "formats": [
    { "id": "dst", "name": "Tajima DST", "status": "available" },
    { "id": "exp", "name": "Melco EXP", "status": "available" },
    { "id": "jef", "name": "Janome JEF", "status": "available" },
    { "id": "pes", "name": "Brother PES", "status": "beta" },
    { "id": "vp3", "name": "Husqvarna/Pfaff VP3", "status": "roadmap" }
  ]
}
GET/api/v1/fabric-profiles

Recommended stabilizer, needle, and a short note for each fabric — cotton, polo, performance, fleece, towel, denim, canvas, leather, twill, and hat. Reasonable embroidery defaults, not a guarantee; always test on scrap first.

Example response (excerpt)
{
  "fabricProfiles": [
    {
      "id": "polo",
      "label": "Polo knit",
      "recommendedStabilizer": "Medium cutaway",
      "needle": "75/11 ballpoint",
      "note": "Stretchy knit — cutaway + center-walk/zigzag underlay stops registration drift."
    }
    /* … cotton, performance, fleece, towel, denim, canvas, leather, twill, hat */
  ]
}
GET/api/v1/machine-profiles

Common home and commercial machine families and the format each one prefers. When a native format is still beta or roadmap we fall back to DST, which nearly every machine reads via USB.

Example response (excerpt)
{
  "machineProfiles": [
    {
      "id": "brother-babylock",
      "label": "Brother / Baby Lock",
      "nativeFormat": "pes",
      "nativeStatus": "beta",
      "useFormat": "dst",
      "note": "PES export is in beta — use DST for now; nearly all Brother/Baby Lock machines read DST via USB."
    }
    /* … tajima, janome, melco-bernina, pfaff-husqvarna */
  ]
}

Every endpoint is GET-only and returns 405 method_not_allowed for other verbs.

Coming soon — hosted compile

The async job API that turns artwork into validated machine files, server-side. On the roadmap.

POST/api/v1/threadproof/jobsRoadmap

Submit artwork plus a fabric, hoop, and machine target; get back a job you can poll for analysis, stitch-plan candidates, a simulated stitch-out, a stitchability score, and downloadable machine files. Not built server-side yet — the engine is browser-based today.

What it returns today
HTTP/1.1 501 Not Implemented

{
  "error": "not_implemented",
  "message": "The ThreadProof compile engine currently runs in the browser. A hosted compile API (server-side render) is on the roadmap. Use the web app at /embroidery-converter, or contact us for API access."
}

API pricing

Indicative plans for the hosted compile API when it ships. Display only — nothing to buy here yet. Talk to us if you want early API access.

Developer

$49 /mo

For prototypes and low volume — read-only endpoints plus a modest hosted-compile allotment when it launches.

Contact us

Scale

$999 /mo

For platforms and high-volume digitizers — bulk compile, SLA, and expert-review integration.

Contact us

Want machine-ready files today?

The full ThreadProof engine already runs in your browser — upload artwork, proof three versions, and export DST, EXP, or JEF right now. No API needed.

Open the web tool

FAQ

Is the ThreadProof Embroidery API free to use?
The three read-only reference endpoints (formats, fabric profiles, machine profiles) are free, unauthenticated GET requests with no rate limit today. The hosted compile API is not yet available; pricing shown for it is indicative only and nothing is billed yet.

Which endpoints actually work right now?
GET /api/v1/formats, GET /api/v1/fabric-profiles, and GET /api/v1/machine-profiles are live and return real JSON server-side today. POST /api/v1/threadproof/jobs is not implemented yet and returns 501 not_implemented.

Can I submit artwork through the API today?
No, not yet. The digitizing and stitch-simulation engine currently runs entirely in your browser at /embroidery-converter; there is no server-side compile endpoint yet, so a POST to the jobs endpoint returns a 501 response rather than a fake success.

Do the read-only endpoints require authentication?
No, the three live endpoints require no API key today and have no rate limit or cache. Any authentication or rate limiting for a future compile API has not been built yet.

Which machine file formats are covered?
The formats endpoint lists Tajima DST, Melco EXP, and Janome JEF as available today, Brother PES as beta (exports but not fully round-trip verified), and Husqvarna/Pfaff VP3 as roadmap (not yet built).

How do I get access to the hosted compile API when it launches?
Contact VectorProof directly. The Developer, Growth, and Scale pricing tiers shown on this page are indicative plans for when the hosted compile API ships; nothing is purchasable through this page yet.

Related tools

The ThreadProof web app, plus the rest of the cutting & craft suite.