MakeLocal

• Browse products — List products currently available to order on MakeLocal. Use when the user wants to see what they can buy or order. Returns id, title, description, price, currency, and number of models per product.
• Get product detail — Get full detail for a single MakeLocal product by id, including its models, required steps and capabilities. Use after browse_products when the user wants details on one product.
• List makers — List active MakeLocal makers (local makers / production units) and their capabilities, manufacturingProcesses and materials. Use when the user wants to find who can make something, optionally filtered by manufacturingProcess (e.g. "FDM", "SLA") or material.
• Get maker detail — Get detail for a single MakeLocal maker (production unit) by id, including its capabilities, manufacturingProcesses and materials. Use after list_makers for one maker.
• List my 3D Models — List the signed-in person's own 3D Models, drafts included, with each one's id, title, status and visibility. Use it to find a Model by name before reading or changing it.
• Get my 3D Model — Read one of your 3D Models by id with all its versions, so you can tell which version is published and which is a draft. Find the id with list_my_models.
• Create a 3D Model — Start a new 3D Model owned by the signed-in person, as a draft nobody else sees until a version is published. Needs the design capability. Prices are in minor units (grosze, cents). Attach the model file afterwards with save_my_model_draft_version.
• Edit my 3D Model — Change the details of one of your 3D Models: title, description, price (minor units), licence terms, visibility, Workspace, photos or tags. Only the fields you pass change. Visibility "public" shows the Model in the public catalogue once a version is published. To publish a version use publish_my_model_version; to remove the Model use remove_my_model.
• List tags for 3D Models — List the approved tags for 3D Models. Pass their ids as tagIds when you create or edit a 3D Model.
• Save my 3D Model draft version — Save the draft version of one of your 3D Models: its semver, changelog and files. A Model has at most one draft; saving again replaces its files and details. Nobody else sees the draft until you publish it with publish_my_model_version, using the versionNumber this returns.
• Get an upload address for my 3D Model file — Get a one-hour address to upload a file for one of your 3D Models. Send the file bytes yourself with an HTTP PUT to uploadUrl, using the method and headers returned; never put the file in the chat. Then call attach_my_model_file with the returned s3Key to put it on the draft version.
• Attach an uploaded file to my 3D Model draft — Put a file you uploaded with get_my_model_upload_url on the draft version of that 3D Model. A version holds one 3D file (kind "model"), so attaching a model file replaces the previous one; previews and attachments are added. Without a draft yet, give the semver to start one. Publish the draft afterwards with publish_my_model_version, asking the person first.
• Publish my 3D Model version — Publish one version of your 3D Model. Ask the person first. The Model goes live and this version becomes the one people who buy or license it get; the previously published version is archived. With visibility "public" anyone can then find the Model in the public catalogue and buy it at its price; "link" shows it to anyone with the link, "org" to Workspace members. A paid Model needs a payout-ready Stripe account.
• Remove my 3D Model — Remove one of your 3D Models, as the web app does: it is archived, not erased. Ask the person first. An archived Model leaves the public catalogue and cannot be picked for new orders or Products; its versions, files and the licences already sold are kept.
• List my Products — List the Products the signed-in person coordinates, drafts included, with each one's id, title, status, visibility and Workspace. Use it to find a Product by name before reading or changing it.
• Get my Product — Read one Product by id with its workflow: the stages an order for it goes through, from the workflow version the Product is pinned to. Find the id with list_my_products.
• Create a Product — Start a new Product as a draft that only the person sees, with its title, description, price (integer minor units, e.g. cents) and photos. Set up its stages with set_my_product_workflow and make it public with publish_my_product.
• Edit a Product — Change a Product's title, description, price, delivery budget, photos, visibility or Workspace; send only the fields that change. A draft changes at once. On a live Product the text, price and photos wait as unpublished changes until publish_my_product, while visibility applies at once. Make it live with publish_my_product; erase it with remove_my_product.
• Get an upload address for a Product photo or stage file — Get a one-hour address to upload a photo or a model file for your Products. Send the file bytes yourself with an HTTP PUT to uploadUrl, using the method and headers returned; never put the file in the chat. Then pass the returned s3Key in photos to create_my_product or edit_my_product, or in a lane’s fileIds or photos to set_my_product_workflow.
• List workflows — List the workflows the person can put a Product on: their own, their Workspace’s and the public ones, official defaults first, each with its published version number. Pass the id and that number as workflowId and workflowVersion to set_my_product_workflow.
• List 3D Models a Product can use — List the published 3D Models a Product lane can be bound to: owned (yours or licensed, free to use) and marketplace (must be bought first). Pass the Product’s currency so only models priced in it are listed. Use a model’s id and publishedVersionId as a lane’s modelId and modelVersionId in set_my_product_workflow.
• Set a Product's workflow — Choose the workflow (and version) whose stages an order for the Product goes through, and per lane the model files, material, process and fee per stage, as the web editor saves them. Send null workflowId to clear it. A setup the editor would refuse is refused here with the reason; fix it and call again. On a live Product it waits until publish_my_product. Read the current setup with get_my_product.
• Publish a Product — Make the Product public to buyers. A draft goes live and can be ordered by anyone it is visible to; on a live Product the unpublished changes replace what buyers see. Ask the person first.
• Discard a Product's unpublished changes — Throw away a live Product's unpublished changes, returning it to what buyers see now. The discarded changes cannot be recovered. Ask the person first.
• Unpublish a Product — Take a live Product off the marketplace, as the web app's Unpublish does: it stops being for sale, so no one can order it, and goes back to a draft only the person sees. Make it live again with publish_my_product. Ask the person first.

Showing the first 25 tools — full list and schemas: Directory API.