Quoting API

Quickstart

Three calls: register the model, upload the bytes, ask for a quote. wait holds the response for up to 30 seconds so a simple integration doesn't need polling.

# 1. register the model
curl -X POST https://api.3dash.in/v1/models \
  -H "Authorization: Bearer $SK" -H "Content-Type: application/json" \
  -d '{"filename":"bracket.stl","bytes":4831922}'
# -> { "id": "mdl_8fA2k9", "upload": { "method": "PUT", "url": "..." } }

# 2. upload the bytes to the url you were given
curl -X PUT "$UPLOAD_URL" --data-binary @bracket.stl

# 3. quote it
curl -X POST "https://api.3dash.in/v1/quotes?wait=10" \
  -H "Authorization: Bearer $SK" -H "Content-Type: application/json" \
  -d '{"material":"pla",
       "lines":[{"model_id":"mdl_8fA2k9","quantity":2,"infill":20}]}'

Authentication

Authorization: Bearer <key>. Two kinds, and the difference matters more than it looks.

There is one mode. Your keys are live from the first day of the free trial — no separate sandbox key to swap out before you launch, and no chance of shipping one by mistake. Your allowance is set by your plan; see Limits.

What the origin allowlist does

Add the sites you call us from on your account page. A publishable key presented from anywhere else is refused with origin_not_allowed, and one presented with no Origin at all — curl, a server, a script — is refused with publishable_key_without_origin.

Because of that, our own origins are always accepted alongside yours. You do not need to add 3dash.in to make the widget work, and adding your own domain is what you need for calls your own pages make with a publishable key.

Endpoints

That is the whole surface. There is no list endpoint for any resource in v1, and anything not in this table returns 404 unknown_endpoint.

The three you read from

GET /v1/machines — your printers. status is the field that matters: only ready can be quoted on, and a machine says so here rather than failing at quote time.

{ "object": "list", "data": [
  { "id": "mch_a1", "object": "machine", "name": "Bambu Lab A1 0.4 nozzle",
    "family": "bambu", "engine": "bambu-studio",
    "status": "ready", "settings_recovered": 556 }
] }
# status: ready | unsupported (Cura) | engine_unavailable | incomplete | missing
# no rate, no hourly cost — see "Amounts, never rates"

GET /v1/materials — what this shop offers, and the density we compute grams with.

{ "object": "list", "data": [
  { "id": "pla", "name": "PLA", "density_g_cm3": 1.24 }
] }
# the id is what you send as "material" on a quote

GET /v1/health — no key, never rate-limited. engines is the machine-readable version of what this page claims: if a family reads false, machines in it are listed engine_unavailable rather than quoted.

{ "object": "health", "ok": true, "version": "v1",
  "engines": { "prusa": true, "bambu": true, "orca": true, "cura": false } }

Onboarding a printer

Send a G-code you already sliced this week. Every PrusaSlicer, Orca and Bambu Studio G-code carries its full resolved configuration in the comments — 347 settings for Prusa, 556 for the Bambu family, including your whole support strategy even if supports were switched off for that job.

curl -X POST https://api.3dash.in/v1/machines \
  -H "Authorization: Bearer $SK" --data-binary @benchy.gcode

The response comes back unconfirmed on purpose. A G-code carries that job's overrides, so a one-off print you sliced at 5 perimeters and 80 mm/s would otherwise become your standing profile and quietly skew every quote after it. Show the values back to yourself, then confirm.

What a quote is, and isn't

When the slice outlasts your wait

A slice is p50 0.84 s and p95 4.97 s per line, so ?wait=10 returns a finished quote almost every time and cannot promise to. Past the hold you get 202 and a pending quote — the same object, with null where the numbers will be — and you poll it. Handle both from one code path: the shape does not change.

POST /v1/quotes?wait=10   ->  202  { "id": "qte_M3xQ1", "status": "pending",
                                     "lines": [ { "grams": null, "amount": null } ] }

# then, until it settles — a second or two apart is plenty
GET /v1/quotes/qte_M3xQ1  ->  200  { "status": "completed", ... }
                          ->  200  { "status": "failed", "error": { ... } }

# a FAILED quote is a 200 with an error inside it, not an HTTP error:
# the request was fine, the slice was not. Branch on `status`, not the code.

Which printer a part goes to

machine_id is optional. Leave it off and every line is routed on its own to the printer best suited to that part. Send it, on the body or on a single line, and that machine is used as given.

Routing never silently substitutes for a machine you named: a pinned machine_id is used or the request errors.

It doesn't try to guess your cheapest printer. An hourly rate doesn't rank machines by what a part actually costs — the profile changes grams and print time too, and those dominate. On one test part, a ₹40/h machine came out 44% cheaper for the job than a ₹25/h one, being faster and laying down less plastic. Knowing the real answer would mean slicing on every candidate, so your list order decides instead.

What the line overrides

A customer who picks 60% infill has to get a 60% price, so the quote line wins over your profile for the few things a customer actually chooses. Everything else comes from your profile — which is the entire point of onboarding from a G-code you sliced yourself.

Limits

All of these are enforced. Sizing your integration against them beats discovering them.

Errors

One envelope for every failure, including inside a failed quote object. Send us the request_id.

{ "error": {
    "type": "slice_error",
    "code": "build_volume_exceeded",
    "message": "The model is 262 mm tall; this machine's Z is 210 mm.",
    "param": "lines[0].model_id",
    "doc_url": "https://business.3dash.in/api-docs#errors",
    "request_id": "req_9Kd21"
} }

Every code we return

type tells you whether to retry; code is the one to branch on. New codes may be added inside v1, so treat an unfamiliar one as its type rather than throwing.

A failed quote carries this same envelope in its error field, inside a 200. The request was valid; the slice was not.

Conventions