Authentication
All requests use your FetchLayer API key as a Bearer token. There are no Printables or Prusa credentials, no OAuth flow, and no account to link.
Sending requests
bash
curl -X POST https://api.fetchlayer.dev/printables/search-models \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"query":"planter"}'Keep your key secret
Only use API keys in server-side code and rotate a key immediately if it is exposed.
Downloading images
The media download endpoint is a GET, and carries the same Bearer header. Because the key travels in a header rather than the URL, a media URL cannot be shared without also sharing the key.
bash
curl -X GET "https://api.fetchlayer.dev/printables/media?url=https%3A%2F%2Fmedia.printables.com%2F...%2Fcover.jpg&filename=cover.jpg" \
-H "Authorization: Bearer ss-your-key" \
-H "Range: bytes=0-65535" \
--output cover.jpgWhat a request costs
One request is one credit, and each page walked by a paginated call counts as one — pages: 10 bills as ten. Two routes are free and consume nothing: /resolve-url, which makes no upstream request at all, and /filter-values, which is the lookup that makes every filtered search valid.
Authentication errors
A missing or invalid key returns HTTP 401.
json
{
"error": "Invalid API key"
}