Getting Started
Search MakerWorld in two steps, then follow a model through to its print profiles.
1. Get your API key
Create an account and generate a FetchLayer API key from your dashboard. No MakerWorld login, Bambu Lab account, or OAuth flow is involved.
Create free account →2. Search for models
curl -X POST https://api.fetchlayer.dev/makerworld/search-models \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"query":"cable management","sortBy":"trending","printableOnly":true,"limit":30}'Tip
/resolve-url first — it tells you whether it points at a model, a designer, a collection, a contest or a search, and hands back the id to use. It does not consume a credit. 3. Follow a model to its print profiles
Every result carries a modelId. Pass it to /model-detail for the file manifest, remix lineage, and every published print profile with its printer, nozzle size, print time and filament use.
curl -X POST https://api.fetchlayer.dev/makerworld/model-detail \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"model":"412809","printProfileLimit":20}'4. Always read notes
Every JSON response carries a notes array. It is empty when the result is complete, and carries a plain-English string when it is not — a page walk that stopped early, a print-profile list truncated by printProfileLimit, or a listing MakerWorld itself cut short. Treat a non-empty notes as a signal to raise pages or page on with cursor.
{
"modelCount": 100,
"hasNextPage": true,
"nextCursor": "eyJwYWdlIjoy...",
"notes": [
"Stopped after 1 page; more results are available."
]
}No designer catalogue
/designer-profile gives you their lifetime counts and their pinned showcase — not everything they have made. Error responses
Every error, on every route, is JSON in one shape: error (what went wrong, in words), status, code, retryable and requestId, which also comes as the X-Request-Id header. Branch on code and retryable rather than on the text; on a 5xx the text is generic. Quote requestId when reporting a problem.
{
"error": "Missing required parameter: url",
"status": 400,
"missing": ["url"],
"code": "invalid_input",
"retryable": false,
"requestId": "922874e3-c0d0-40d8-8866-d198af132420"
}| code | Status | Retryable | Meaning |
|---|---|---|---|
| invalid_input | 400 | no | The request needs fixing; error names the field. A missing required parameter also lists it in missing. |
| unauthorized | 401 | no | The API key is missing or not valid. |
| insufficient_credits | 402 | no | Nothing left to spend: no credits, a used-up free trial, or a monthly allowance and credit balance both spent. error says which. Waiting does not help; topping up does. |
| forbidden | 403 | no | This key or account is not allowed this request. |
| not_found | 404 | no | What the request names does not exist or is not public. |
| expired | 410 | no | What the request refers to is no longer available; ask for it afresh. |
| quota_exceeded | 429 | no | A request-rate limit was reached; error says which. Slow down before sending more. |
| cancelled | 499 | no | The caller closed or cancelled the request before it finished. The work was stopped and nothing was charged. |
| time_limit | 503 | yes | Your timeoutMs ran out before there was anything to return; ask again, or allow more time. |
| temporarily_unavailable | 503 | yes | Not available right now; ask again shortly. |
| store_unreachable | 503 | yes | Store routes (Shopify, WooCommerce): the store itself can’t be reached right now — it may be offline. Ask again later. Where a store route doesn’t say so yet, an offline store is temporarily_unavailable. |
| upstream_error | 502 | yes | The source answered in a way that could not be used; ask again later. |
| internal_error | 500 | yes | Something failed on our side; ask again later, and quote requestId if it persists. |
| tool_error | — | no | MCP only: a tool call failed in a way no other code describes; error says what. |
More codes may be added; treat one you do not recognise by its retryable flag. Over MCP, a tool error carries the same fields in structuredContent, and as a JSON text block beside the message.