Printables API Docs — Endpoints & JSON Examples | FetchLayer

Printables API v1

Search and browse public 3D models on Printables, read the designers who publish them, follow their collections, and track the design contests the community competes in — all from https://api.fetchlayer.dev/printables, with your FetchLayer key and nothing else.

OpenAPI JSON

Printables API at a glance

This is the reference: every endpoint, its parameters and the fields it returns. The essentials first.

Returns
3D models, makers and contests, as typed JSON.
Endpoints
12 endpoints, grouped as Models, Designers, Collections, Contests and Utility. See them all
Request
POST https://api.fetchlayer.dev/printables/<endpoint> with a JSON body.
Auth
Your FetchLayer API key as a Bearer token. One key works for every platform we support. Authentication
Cost
1 credit per page of results a call returns; the exact figure is on every response. Credits are $1.99 per 1,000 pay-as-you-go, plans start at $25 a month, and new accounts get 30 free requests.
MCP
Also on our MCP server for AI agents, with the same key and the same billing. Connect an agent

What teams use it for, with worked examples: Printables API

Before you filter anything

Every id-shaped filter on a model search — category, licence, material, printer, design tool — takes an id, never a name. There are 639 valid printer values alone, and an id that does not exist comes back as an empty result set rather than an error, so a guessed "Prusa MK4" reads as "no models match". POST /filter-values returns the whole vocabulary in one call, costs no credit, and is meant to be cached.

Two limits worth knowing

  • Model files are described, not downloadable. A model's file listing carries each file's name, size, kind and slicing settings, but no download URL — model-file downloads aren't publicly available, so no public one exists. GET /media streams images and the instructions PDF, not geometry.
  • Read notes[] on every response. It is where a truncated walk or an upstream limit is reported. A short result set with a note in it is a capped result, not an empty corner of the site.

Available endpoints

Product overview Printables API: what it returns, pricing and use cases