add_machine
ChatGPTAdd a machine to this shop (POST /api/public/v1/machines/{businessId}). For an assistant connected through OAuth only: as in the dashboard, the machine is added by the user who signed in, and a developers-portal key is refused (NEEDS_SIGNED_IN_USER). WRITES REAL DATA: the machine joins the instant quote with the materials it runs. It is the last step of the production workflow in the server instructions, after the user has confirmed the machine. machine: the fields of the dashboard's machine form. typeMachine (the service, e.g. 3D_PRINTING, CNC_MACHINING, SHEET_METAL) and mark are required; technology names the process within the service (e.g. FDM, SLA), as get_pricing_setup lists the shop's. - mark: the machine's name. - surfaceMachine: the build volume, "XxYxZ" in the machine's unit (e.g. "250x210x210"); "XxY" for sheet metal. unit: mm, cm or inch. - pricePerHour: the hourly rate, in the machine's currency. currency; power; description. - 3D printing slicer settings: numWalls, nozzleDiameter, supportDensity, maxVolumetricFlow, flowRateOverride, supportDepthPerArea, supportsEnabled, infillPattern. - materials: optional, each with add_material's fields; add_material adds more later. The API sets business, machineOwner, status, marginMachine itself. Returns the machine as created, with its id.
add_material
ChatGPTAdd a material to one or more of this shop's machines (POST /api/public/v1/machines/{businessId}/{machineId}/materials). WRITES REAL DATA: customers can pick it in the instant quote straight away. It is the last step of the production workflow in the server instructions, after the user has confirmed the material, its price and the machines. machineIds: the machines that will run it. The dashboard offers a new material to every machine of the technology and lets the user untick some, so the machines are the user's choice. A machine that already carries a material of that name is changed with update_material instead. material: the fields of the dashboard's material form. A name is required. The instant quote prices it from its price, currency (the machine's, from list_machines) and unit, and for 3D printing from its density (the dashboard proposes 1.03 g/cm3). - name; price: a number, per the unit, in the currency; currency: ISO code; unit: what the price is per (cm3, g, kg, lb; m2 for CNC; cm2, m2 or kg for sheet metal). - colors: [{ name, hex, isDefault? }]. The WHOLE list: it replaces the current one, so a color left out of it is removed. - startupCost: { price, currency }, charged once per order line, not per piece. - density: { value, unit: "g/cm3" }; discount; description; keyFeatures; materialType; isPublic. - thicknesses (sheet metal, CNC priced per thickness): the whole list, it replaces the current one. Returns one result per machine: saved: true with the new material (and its id), or saved: false with the reason.
add_order_step
ChatGPTAdd one of the shop's own production steps to a status, as the production management page does (POST .../order-statuses/{status}/steps). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the step shows on the production board at once. Names are unique across all statuses (STEP_NAME_TAKEN); only statuses with takesNewSteps take steps. Confirm with the user first.
add_pricing_rule
ChatGPTAdd a pricing rule to this shop (POST /api/public/v1/pricing/{businessId}/rules), as the Pricing rules page does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the instant quote applies it at once. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. A rule reads "if <condition> <operator> <value>, then <action>": - Conditions: exceeds_machine, order_price, selected_material, selected_post_production, customer_type, file_type for every service; issue_detected for 3D_PRINTING and CNC_MACHINING; min_volume, max_volume for 3D_PRINTING. - Operators: detected for exceeds_machine and issue_detected; is / is_not for the choices; less_than / greater_than / equals for numbers. - Actions: manual_quote, show_warning, custom_message, custom_header_message; file_type also reject_file; order_price also add_fee (with fee, and less_than or greater_than only); customer_type only none or hide_purchase_order. A shop on the free plan has one rule per technology (RULE_LIMIT_REACHED).
add_question
ChatGPTAdd a question to a technology's instant quote (POST /api/public/v1/pricing/ {businessId}/technologies/{technology}/questions), as "Add field" on the Data collection page does. It is asked last. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: customers are asked it at once, and its prices apply. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. displayName and type are required; name (the key, never changeable) defaults to the displayName and must not be taken.
add_technology
ChatGPTStart offering a technology, as the pricing tools page adds one (POST /api/public/v1/pricing/{businessId}/technologies). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the technology joins the instant quote with the dashboard's starting questions (infill and precision where the technology has them). It is the last step of the pricing workflow, after the user has confirmed it. Customers can only order it once the shop has a machine and material for it (add_machine). - service: 3D_PRINTING, CNC_MACHINING or SHEET_METAL. technology: its name (one from list_technologies' canAdd, or the shop's own). A name the shop has, in any spelling, is refused (TECHNOLOGY_EXISTS); so are / \ ? & = % + $ ; : @ " ' < > |. - calculator: left out, the one the dashboard starts the service on. Formula (slicing) is offered for FDM or the shop's own technologies only. - minOrderPrice, minPartPrice: in the shop currency; none for a manual quote. - internalUseOnly hides it from the instant quote; description; alias (the name customers see).
apply_setup_profile
ChatGPTApply a setup profile to the shop, as the pricing tools page does (POST /api/public/v1/shop/{businessId}/setup-profiles/{profile}/apply). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the profile's machines, materials, pricing, questions and lead times join the shop at once. Call preview_setup_profile first, show the user what it changes, and wait for them to confirm. - Only technologies the shop does not offer yet (SETUP_PROFILE_TECHNOLOGIES_EXIST otherwise): send technologies to apply the others only. - On a shop with no pricing yet, a profile may replace its shipping and taxes; that takes the permission behind them (MISSING_PERMISSION otherwise). Returns jobId (keep it: undo_setup_profile needs it), status, written per part, and heldBack: the parts left out.
create_demo_quotes
ChatGPTA demo quote and a demo order for each process the shop can price, as the dashboard makes them at the end of setup (POST /api/public/v1/shop/{businessId}/ demo-quotes). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES DATA: test demands, priced with the shop's current machines, materials and prices, so the user sees what a customer would get. No customer is emailed. Existing demos are re-priced in place; demos the shop had hidden come back. - keys: only some processes, as service|technology (e.g. 3D_PRINTING|FDM). Returns demos (quoteId and orderId per process, for get_quote) and skipped: the processes not ready yet, with why (NO_MATERIAL, MANUAL_PRICING, NO_SAMPLE, PRICING_FAILED).
create_quotes
ChatGPTCreate one or more quotes for customers of this shop (POST /api/public/v1/demand/create-quotes/{businessId}). WRITES REAL DATA AND EMAILS THE CUSTOMER. Each quote is created in the shop, its totals are built from each line item's priceMachine (the price of one piece), and the customer at email receives it with a payment link. Only call this when the user explicitly asks to create or send a quote, and confirm the customer email, items and quantities with them first. Never call it to "try" something. Each quote needs email and at least one quoteModel line item. A line item has the same shape as a quoteModel item returned by get_quote (fileLink, fileName, technology, material, quantity, volume, modelType, ...): build items from an existing quote or from what the user gives you — never invent file links or geometry. Keep the material object whole, or send only its name with service and technology, as in estimate_price — SeekMake fills it in from this shop. The business is set from the API key. Leave demandStatusInfo out: a new quote starts as "quote sent", the way the dashboard sends one. CURRENCY: prices are in the shop's currency, and a quote that names no currency gets the shop's. Set it only when the user asked for another one. CUSTOMER DETAILS: when email belongs to an existing SeekMake customer, their saved name, phone and addresses fill in whatever the quote leaves out. Say so when you report the created quote; send the details yourself to use different ones. A FILE THE USER ATTACHED: put file = { name, content, encoding } in the line item instead of fileLink — same rules as estimate_price (the content, never a path). SeekMake stores and measures it. Price it first: call estimate_price with the same part and file, and send its price as the item's priceMachine. An item with a file and no priceMachine is refused rather than quoted at 0. A rejected call returns its reason — fix the input, do not retry unchanged.
delete_machine
ChatGPTDelete one of this shop's machines (DELETE /api/public/v1/machines/{businessId}/{machineId}). For an assistant connected through OAuth only: as in the dashboard, the machine is deleted by the user who signed in, and a developers-portal key is refused (NEEDS_SIGNED_IN_USER). WRITES REAL DATA and cannot be undone from here: the machine leaves the instant quote with every material it runs, and the lead-time options of those materials leave the shop's pricing, as when the dashboard deletes it. It is the last step of the production workflow in the server instructions, after the user has confirmed which machine goes, knowing its materials go with it. confirmName: the machine's name, as list_machines gives it. A name that is not this machine's is refused (MACHINE_NAME_MISMATCH) and nothing is deleted. Returns the deleted machine.
estimate_price
ChatGPTPrice one part with this shop's pricing (POST /api/public/v1/price-estimation/{businessId}). The last step of the pricing workflow: call it only once the customer has chosen the process (list_machines), the material, the options (get_pricing_setup) and the quantity. Never choose any of them for the customer. Creates nothing and contacts no one. Each call runs the full pricing engine, so price the part the user asked about — do not call it in a loop to explore options. REQUIRED: viewerType ("3D" for a 3D model, "2D" for a flat drawing), the geometry, service, technology, material, quantity and isSupported; color and colorHex when the shop offers colors. The calculator is always the one the shop set for that technology (see get_pricing_setup) — a priceCalculatorTool you send is ignored. GEOMETRY — a 3D part needs one of these, or it is refused with a 400 naming it: - A part already on SeekMake: take the quoteModel item from get_quote — it carries slicingData and rawSlicingData — and change only what the user asks about (material, quantity, color, ...). - A file the user attached: send part.file = { name, content, encoding } instead of fileLink/slicingData. STEP/STP and ASCII STL are text — send them as utf8, as they are. Binary files (binary STL, 3MF, GLB) go as base64. Up to 1.5 MB; formats: stl, step, stp, obj, 3mf, iges, igs, ply, glb. SeekMake measures it. content is the file itself, never a path: SeekMake cannot open files on the user's computer. If you only have a path and cannot read the file, ask the user to attach it. MATERIAL: either copy it whole from a quote of this shop (with its selectedOptions), or send only its name — material = { name: "ABS" } — with service (e.g. "3D_PRINTING") and technology (e.g. "FDM"): SeekMake fills in its price and the machine it runs on from this shop. A name the shop does not carry is refused with the shop's materials for that process (MATERIAL_NOT_FOUND) — pick one of those or ask the user, never invent one. OPTIONS: send the choices the user made (infill, precision, lead time, ...) in selectedOptions, copied from get_pricing_setup. A choice left out is priced with the shop's default option (else its first), as the instant quote pre-selects it — lead time included; post-production is only added when sent. On a shop that prices with its own equation, a choice the equation uses that has no default is refused by name (SELECTED_OPTIONS_REQUIRED) — ask the user. PRICING_EQUATION_FAILED means the shop's own equation could not be computed for this part — say so, do not retry. NO_PRICING_SETUP / MANUAL_PRICING: the shop has no automatic price for that technology — offer create_quotes instead of guessing a price. An option that is not one of this technology's choices (e.g. a precision of another technology) is refused (OPTION_NOT_OFFERED) with the options it offers; a color the material does not come in is refused (COLOR_NOT_OFFERED) with its colors. Returns quote: the part as the instant quote totals it, with the same rules. Give THESE numbers to the customer, as returned — never recompute them: - unitPrice: one piece after the discount and the minimum part price. - discountPercent / discountAmount: the shop's best discount for this part (promotion, quantity, volume or material — the best one, never added together; see get_discounts). minimumPartPrice: set when it raised the price of a piece. - leadTime: the lead time of the whole quote, when the shop sets one per quote. - partsTotal: the pieces. startupCost: once per material, never discounted. otherFixedCharges: options the shop charges as fixed amounts. - minimumOrderSurcharge: added to reach the minimum order value. - subtotal, processingFee (SeekMake's fee), total = subtotal + processingFee. - excludes: shipping and tax are not in total; they depend on the delivery address. Also returned, to explain a price: price is the engine's price of ONE piece before any discount or minimum (the same for 1 or 10 unless the shop prices by quantity), and lineTotal = price x quantity + startupCost before discounts — never give either as the pr…
get_customer
ChatGPTOne customer of this shop and their history with it (GET /api/public/v1/shop/{businessId}/customers/{customerId}). READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). The customer, then demands: their 50 newest quotes and orders, with id, orderNumber, createdAt, priceToClient (what they pay), currency and the number of parts; demandsCount is how many they have in all (list_quotes with their email pages through every one). For one in full, call get_quote with its id.
get_discounts
ChatGPTThis shop's discounts, as its instant quote takes them off a part (GET /api/public/v1/pricing/{businessId}/discounts). READ-ONLY. Every discount, with isActive (an inactive one is not applied): - promotions: a % off every part from the day from to the day to; inEffect says whether it applies today (active and in its dates). - quantityDiscounts: a % off a part ordered in a quantity from fromQuantity to toQuantity. - volumeDiscounts: a % off a part whose volume is from fromVolumeMm3 to toVolumeMm3. - materialDiscounts: a % off every part in that material. - hasActiveCoupon: whether a coupon code is active. The codes are not here: a signed-in user sees them with list_coupons. A part gets the BEST ONE of these, never their sum, and the startup cost is never discounted. estimate_price applies them: use its quote.discountPercent for a part instead of working it out. The minimum order value and minimum part price are in get_pricing_setup; startup costs per material in list_machines. To change them, update_discounts takes these lists back in the same shape.
get_packing_slip
ChatGPTA link to an order's packing slip, the page the dashboard's Download packing slip opens (GET /api/public/v1/shop/{businessId}/orders/{demandId}/packing-slip). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). Answers { orderNumber, url }. The link opens in the SeekMake dashboard, for a member of the shop signed in there: it shows the slip and opens the print dialog to save it as a PDF. Give the link to the user as it is; you cannot open or read the PDF yourself. The slip carries the customer's address: give it to the user only.
get_pattern_status
ChatGPTHow far this shop's pattern-matching pricing is trained, per material. READ-ONLY. Pattern matching prices a part from an equation trained on the shop's own past prices, one equation per machine and material. One entry per technology that prices with it (inUse: true) or still carries training from before it switched calculator (inUse: false). Each material: machine and material ids and names, samples (sample parts on record), pricedSamples (those with a price entered), trained (an equation exists), and confidence (0-1, how well the equation fits the samples) when trained. A material with offered: false is training left from a material or machine the shop no longer has. trained with samples: 0 (and a note) means it was trained before its samples were removed: it still prices with that training, as the dashboard shows. A material that is not trained cannot be priced by pattern matching. Training and adding samples happen in the dashboard (Pricing tools > Pattern matching); this tool cannot do either. The equations, margins and sample prices are not returned.
get_payment_settings
ChatGPTHow this shop gets paid, as its Payments & taxes page shows it. READ-ONLY. Returns the currency, then each payment method customers can use: - stripe: connected (a Stripe account is linked), onboardingStatus as last recorded (completed: onboarding finished; processing or disabled: Stripe still needs something from the shop, finished in the dashboard), externalCheckout. - paypal: active and the PayPal email; apiConnected when PayPal API credentials are set up. - bankTransfer: active and the bank name. purchaseOrder: active. - coupons: code, discount (percent), isActive and usedCount. Account numbers, ids and credentials are never returned. Payment methods, Stripe and payouts are changed in the dashboard; coupon codes with set_coupon.
get_pricing_setup
ChatGPTHow this shop prices each technology: the calculator it uses and the choices a customer makes in its instant quote. In the pricing workflow: step 4. Show the chosen technology's choices with their defaults, and let the customer keep or change them. READ-ONLY. One entry per service and technology: - calculator: default = AI estimate from the geometry; formula = machine time and material from a slicer; pattern-matching = trained on the shop's own past prices; custom = the shop's own equation; metal-system = sheet and metal parts; manual = priced by hand, estimate_price has no automatic price for it. - internalUseOnly: hidden from the instant quote. - minimumPrice / minimumPartPrice: the minimum order value and minimum part price the shop set, when it set them. estimate_price applies them. - choices: infill, precision, lead time, post-production and the shop's own questions, each with its options. An option says how it moves the price (priceMultiplier, percentage, fixedPrice, numberValue), whether it is the default (isDeffault), and materialIds when it applies to some materials only. A choice with wholeQuote: true (lead time, when the shop sets one per quote) applies to the whole quote: send it in selectedOptions all the same, and estimate_price applies it once. To price with a choice, copy the option object unchanged into the part's selectedOptions for estimate_price. Margins, equations and training data are not part of this answer.
get_profile
ChatGPTThe shop's business profile (GET /api/public/v1/shop/{businessId}/profile). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). READ-ONLY. companyName, profileName (its public link name), businessEmail, description, website, logo, address (address, zip, city, region, country, tel), currency, lang (the language of its customer emails and PDFs), vatNumber, status.
get_quote
ChatGPTFetch one demand in full by its ID — every line item, the customer, the address, the status history and the full price breakdown. READ-ONLY: fetches a single demand, makes no changes. WHEN TO CALL: after list_quotes, when the user asks about one specific entry, or when they give you a demand ID directly. The list response already carries the summary fields for every entry, so this is for the one demand that needs detail. STATUS: statusHistory lists every status change with its name and date, oldest first. availableStatuses lists the statuses this shop uses and their substatuses — the only valid values for update_quote. Read both before changing a status. Each line item carries the model file, the chosen material and quantity, and its own price. Money fields are denominated in the demand's currency. PRICES, in the demand's currency, as the dashboard shows them: - priceTotal: the parts, after discounts and coupon, with startup costs and the minimum order applied. No shipping, tax or fee. - priceDelivery: shipping. taxPaid: the tax amount (taxName, taxPercentage). - platformFee: the processing fee charged to the customer. - priceToClient: the FINAL price the customer pays at checkout, all of the above included. Give it as the total; never add the fields up yourself. - priceToManufacturer: what the shop receives. - additionalFees: charges the shop added later, each paid separately with its own tax. PAYMENT LINK: paymentLink is the link the quote email sends the customer to pay (the shop's own client page when it has one). It opens the checkout and signs nobody in. Give it as it is when the user asks for a payment link, for this demand's customer only. SCOPE: the demand must be one list_quotes can return for this shop — its own, or one it manufactures as a partner. Any ID list_quotes gave you will open. Asking for a demand of an unrelated shop returns a permission error, not an empty result — that is expected, not a bug to retry or work around.
get_quote_file
ChatGPTGet a download link for a demand's model files (GET /api/public/v1/demand/access/file/{demandId}). READ-ONLY. Returns a list of { url, token? }, one per file. Links to protected files carry a signed token valid for about five minutes, so a stored link goes stale — call again for a fresh one. Pass filePath (a quoteModel item's fileLink from get_quote) for one file; omit it for every file on the demand. The demand must be one this shop can open.
get_setup_guide
ChatGPTWhat is left to set up in this shop, as its dashboard's setup guide shows it (GET /api/public/v1/shop/{businessId}/setup). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). - guide: the four steps, each done or not: activation (machines and materials), shop_setup, plugin (the instant quote on the shop website) and payments_taxes (a way to get paid). - activationChecklist: what activation needs: location, machines, materials, pricing, shipping or pickup. Machines, materials, pricing, shipping and taxes can be set up with the other tools; the shop setup, plugin and payment steps are done in the dashboard. Like opening the dashboard, it brings the stored setup status up to date.
get_shipping
ChatGPTWhere this shop ships, at what price and how fast (GET /api/public/v1/pricing/{businessId}/shipping). READ-ONLY. In the shop's currency. localPickup / mainOfficePickup: whether the customer can collect the order instead. Each method: - region COUNTRY: destination is the ISO country code (e.g. "TN", "FR"); CONTINENT: a continent code (e.g. "EU", "AF"); OTHERS: everywhere else. - price and daysToDeliver (businessDaysOnly: working days only). - express: a faster option with its own price and days, when the shop offers one. - freeShippingFrom: the order total from which this method is free. The instant quote offers the customer the method of their country, else of their continent. A country in no method is one the shop does not ship to. Shipping is not in estimate_price's total; carrier rates (FedEx, InPost, ...) of a shop that connected a carrier are priced at checkout and are not listed here.
get_shop_stats
ChatGPTThis shop's figures, as its Stats page shows them (GET /api/public/v1/shop/{businessId}/stats). READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). For the period from..to (by creation date); all time without dates. - totalQuotes / totalOrders: quotes received and orders won in the period; conversionRate and quoteConversionRate are percentages. - totalRevenue: revenue from orders that went into production, in currency. avgOrderValue, avgQuoteValue, leadTimeAverage, repeatedCustomerRate. - revenuePerMonth, quotedValuePerMonth, orderedValuePerMonth: one figure per month (by month name) of the last 12 months; with a period, only the months in it. Give the figures as they are; never recompute them.
get_tax_settings
ChatGPTThis shop's tax settings, as its Payments & taxes page shows them. READ-ONLY. Returns: - taxType: VAT = the shop taxes with the rates of its tax table; STRIPE = Stripe Tax works the tax out (the table is not used). stripeTaxAvailable: false on the free plan, which cannot switch to STRIPE. - defaultTaxName: the name shown on a tax line by default (e.g. VAT). - rules: what the tax is charged on besides the parts: addShippingInTaxCalculation, addProcessingFeesInTaxCalculation, additionalFeesInTaxCalculation; and canToggleTaxInclusion: customers can show prices with or without tax. - taxConfigurations: the tax table, one entry per location: location (a country name, a continent code, or DEFAULT) and locationType, then a rate for private customers (clientConfig) and one for companies (businessConfig): taxName, taxValue in percent, isEnabled, and regions with rates of their own when sameForRegions is false. configType SAME: one rate for both; DISTINCT: set apart. A customer is taxed with their country's entry, else their continent's, else DEFAULT; a side with no taxName or not enabled does not apply.
get_widget_link
ChatGPTThe shop's instant quote: its link and the code to embed it on a website (GET /api/public/v1/shop/{businessId}/widget), as the dashboard hands them out. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). READ-ONLY. link: the page customers open to get a price. embedCode: the HTML to paste on the shop's own website (an iframe of embedUrl and SeekMake's script). ownPage: the shop's own page that hosts the embed, when it set one. Both are public and safe to share.
list_coupons
ChatGPTThis shop's coupon codes (GET /api/public/v1/pricing/{businessId}/coupons). READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise): the codes are the shop's to hand out. Each coupon: code, discount (%), isActive (an inactive code is refused at checkout) and timesUsed. A coupon is taken off after the part's own discount, so the two add up. Never give a code to a customer unless the user asks you to.
list_drafts
ChatGPTInstant quotes customers started on this shop and did not finish, newest first (GET /api/public/v1/shop/{businessId}/drafts), as its Drafts page lists them: the ones worth following up. READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise), and a user allowed to see drafts. The shop's plan limits how far back drafts go. search matches the customer or a file name. Answers { data, count }: each draft with the customer (email may be missing), its parts (quoteModel) and its price so far. To follow one up, offer create_quotes for that customer with those parts; never email a customer unless the user asks.
list_lead_times
ChatGPTThis shop's lead times, as the dashboard's Lead time page shows them (GET /api/public/v1/pricing/{businessId}/lead-times): the delivery speeds a customer picks. READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). mode global: one list (leadTimes) for every technology; mode per-technology: a list per technology (technologies[].leadTimes). Each lead time: id, name, days, priceMultiplier (1 keeps the price, 1.5 adds half), default, materialIds.
list_machines
ChatGPTList this shop's machines and the materials each one runs — the catalogue its instant quote offers. In the pricing workflow: steps 2 and 3. Offer the processes, then the materials of the one chosen, and let the customer pick. READ-ONLY. Answers "what do we offer", "which materials for SLA", "what does PLA cost" without touching anything. Each machine: id, name, service, technology, buildVolume, unit, currency, pricePerHour when set, and its materials: id, name, price per priceUnit (sheet and CNC materials may be priced per thickness instead), currency, startupCost, density, colors, and isDefault: true on the one material the instant quote pre-selects for its technology (absent on the others, and on all of them when the shop set none). Prices are the shop's own, in the currency shown — never convert or re-label them. There is no on/off state for a machine: every machine listed is one the shop has. To price a part in one of these materials, call estimate_price with material = { name } and the service and technology of the machine that runs it.
list_order_statuses
ChatGPTThe shop's order statuses and their production steps, as the production management page shows them (GET /api/public/v1/shop/{businessId}/order-statuses). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). READ-ONLY. Each status (fixed by SeekMake) with its steps: name, color, isVisibleToClient, showInJobBoard, editable, removable. takesNewSteps: whether add_order_step takes it.
list_pricing_rules
ChatGPTThis shop's pricing rules (GET /api/public/v1/pricing/{businessId}/rules), as its Pricing rules page lists them. READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise), like the changes to them. Each rule: id, name, service, technology (none: every technology of the service), "if condition operator value, then action", enabled, priority, and for a fee rule its fee { name, amount }. E.g. { condition: "order_price", operator: "less_than", value: "50", action: "add_fee", fee: { name: "Small order", amount: 5 } }.
list_questions
ChatGPTThe questions a technology's instant quote asks the customer, as the dashboard's Data collection page lists them (GET /api/public/v1/pricing/{businessId}/technologies/ {technology}/questions): infill, precision, post-processing and the shop's own. READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). Each question: id, name (the key the pricing equation reads), displayName, type, required, disabled, materialIds, and by type: options (each with id, name, price { type, value }, default), checkedPrice (checkbox), perUnitPrice (number), default. locked says why the dashboard does not let it be changed (e.g. the slicer prices with infill and precision). Lead time is not a question here.
list_quotes
ChatGPTList this shop's quote requests or confirmed orders, newest first, paginated. READ-ONLY: fetches and lists data, does not contact a customer, change a status, or send an offer. TYPE — pick deliberately, the two are different stages: - QUOTES: requests the customer has sent but not yet paid for. This is the shop's work queue — what still needs pricing, an offer, or a reply. - ORDERS: demands that became real orders. This is revenue and production, not a to-do list. If the user says "quotes", "requests" or "leads" use QUOTES; for "orders", "sales" or "what did we sell" use ORDERS. When genuinely ambiguous, ask rather than guess — the two produce very different numbers. PAGINATION: returns { data, page, pageSize, total, totalPages }. total is the full count matching the type, NOT the length of data. Quote any count from total, and page through explicitly when the user wants more than one page. LOOKUP: pass orderNumber for "order 102" (the number customers see, not an ID), or email for one customer's demands, instead of paging through and matching yourself. An order number lives in one stage only: if QUOTES has no match, try ORDERS. Money fields are in each demand's own currency — never convert or re-label them. PRICES, in the demand's currency, as the dashboard shows them: - priceTotal: the parts, after discounts and coupon, with startup costs and the minimum order applied. No shipping, tax or fee. - priceDelivery: shipping. taxPaid: the tax amount (taxName, taxPercentage). - platformFee: the processing fee charged to the customer. - priceToClient: the FINAL price the customer pays at checkout, all of the above included. Give it as the total; never add the fields up yourself. - priceToManufacturer: what the shop receives. - additionalFees: charges the shop added later, each paid separately with its own tax. get_quote also gives the payment link of one demand. Line items carry the material's identity and prices but not its descriptions or colour list — get_quote returns those in full for the one demand that needs them. Only this shop's demands are ever returned — the API key decides which shop, so there is no businessId to pass and no way to see another shop's orders.
list_setup_profiles
ChatGPTThe ready setups SeekMake offers this shop (GET /api/public/v1/shop/{businessId}/ setup-profiles), as the pricing tools page lists them. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). READ-ONLY. Each profile: keyvalue, title, description, features, the service and the technologies it sets up (3D_PRINTING/SLA, CNC_MACHINING, ...). A profile brings machines, materials, pricing, questions and lead times ready to sell. enabled: false means the shop has none to offer yet (quick_pricing_setup offers presets instead).
list_technologies
ChatGPTThe shop's technologies and what it may add, as the pricing tools page shows them (GET /api/public/v1/pricing/{businessId}/technologies). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). READ-ONLY. Returns: - technologies: each one the shop offers, with its service, calculator, minimums, internalUseOnly (hidden from the instant quote) and the names of its machines. - canAdd: per service (3D_PRINTING, CNC_MACHINING, SHEET_METAL), the technologies suggested (SeekMake's own, and its machines' that have no pricing yet), and the calculator a new one starts on. Any other name may be added too. - presets: the quick start presets, the technologies each adds, and alreadyOffered: those the shop has, which the preset would add again as copies.
mark_setup_step_done
ChatGPTMark a step of the shop's setup guide done, as its Done button does (POST /api/public/v1/shop/{businessId}/setup/steps/{step}/done). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA. Only the plugin step (the instant quote put on the website) is marked by hand; the guide works the other steps out from the shop itself (get_setup_guide). It also works the shop's status out again, which can activate the shop and send it the activation email. Mark it only once the user says the widget is on their website. Returns the setup guide after the change.
measure_part
ChatGPTMeasure a 3D file the user attached, without pricing it: size, volume, surface. READ-ONLY. Creates nothing and stores nothing. Use it for "how big is this part", "will it fit on our printer" (compare with buildVolume from list_machines), or before choosing a material. To get a price, call estimate_price instead — it measures the file too. Send the file itself as { name, content, encoding }. STEP/STP and ASCII STL are text — send them as utf8, as they are. Binary files (binary STL, 3MF, GLB) go as base64. Up to 1.5 MB; formats: stl, step, stp, obj, 3mf, iges, igs, ply, glb. content is the file itself, never a path: SeekMake cannot open files on the user's computer. Returns width, height and depth (the bounding box), volume, surfaceArea and convexHullVolume, in the units of the file — mm for almost every 3D file. closed is false when the mesh has open edges, which can make a printed part fail; say so. A file that is not a readable 3D model is refused (FILE_NOT_MEASURABLE).
move_order_step
ChatGPTMove a production step on the production board, as its drag and drop does (PUT .../order-statuses/steps/{name}/position). position: zero-based, across the board. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA.
preview_setup_profile
ChatGPTWhat applying a setup profile would change, before anything is (GET /api/public/v1/shop/{businessId}/setup-profiles/{profile}/preview). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). READ-ONLY. changes: per part (machines, material_types, pricing, lead_time, data_collection, rules, shipping, tax), willWrite (how much it writes), inProfile, shopHasNow, conflicts and warnings. A held_back entry names what will not be applied (what would replace the shop's own settings). currency: the profile's prices are converted to the shop's. Show this to the user before apply_setup_profile.
quick_pricing_setup
ChatGPTAdd one of the pricing tools page's quick start presets (POST /api/public/v1/pricing/{businessId}/quick-setup). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the preset adds its technologies, priced, with ready machines and materials (prices converted from EUR to the shop currency). Show the preset from list_technologies (presets) and wait for the user to confirm first. - fdm-starter: FDM. multi-tech: FDM, SLA, SLS. metal-additive: SLM, DMLS. full-service: FDM, SLA, sheet metal, CNC. sheet-metal-only: sheet metal. - A technology the shop already has would be added again as a copy ("FDM 2"): that is refused (PRESET_TECHNOLOGIES_EXIST) unless allowCopies is true. Returns the technologies and machines it added.
remove_coupon
ChatGPTRemove a coupon code from this shop (DELETE /api/public/v1/pricing/{businessId}/coupons/{code}), as the dashboard does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA and cannot be undone from here: customers can no longer use it. To pause a code instead, set_coupon with isActive: false. It is the last step of the sales workflow in the server instructions, after the user has confirmed it. Returns the coupons as saved (COUPON_NOT_FOUND, with the codes, when it had none).
remove_material
ChatGPTRemove a material from one or more of this shop's machines (DELETE /api/public/v1/machines/{businessId}/{machineId}/materials/{materialId}). WRITES REAL DATA and cannot be undone from here: the material leaves the instant quote of those machines, with its price, colors and settings. It is the last step of the production workflow in the server instructions, after the user has confirmed which material comes off which machines. Removing it from every machine of a technology takes it out of the instant quote. targets: each machine's copy of the material to remove, as { machineId, materialId } from list_machines. Returns one result per machine: saved: true when it was removed, or saved: false with the reason (ERROR_MATERIAL_NOT_FOUND: that machine does not carry it).
remove_order_step
ChatGPTRemove a production step (DELETE .../order-statuses/{status}/steps/{name}). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). DELETES REAL DATA: the step's orders move to another step of the same status (ordersMoved says how many). A locked step is refused. Confirm with the user first.
remove_pricing_rule
ChatGPTDelete one of this shop's pricing rules (DELETE /api/public/v1/pricing/{businessId}/rules/{ruleId}). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). DELETES REAL DATA and cannot be undone; update_pricing_rule with enabled: false switches a rule off instead. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it.
remove_question
ChatGPTDelete one of a technology's questions (DELETE /api/public/v1/pricing/{businessId}/ technologies/{technology}/questions/{questionId}). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). DELETES REAL DATA and cannot be undone; update_question with disabled: true turns a question off instead. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. A locked question is refused.
remove_shipping_method
ChatGPTRemove the shipping method to one destination (DELETE /api/public/v1/pricing/{businessId}/shipping/methods), as the dashboard does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the shop no longer ships there, unless a continent or OTHERS method covers it. It is the last step of the sales workflow in the server instructions, after the user has confirmed it. Returns the shipping as saved (SHIPPING_METHOD_NOT_FOUND when there was none).
remove_tax_rate
ChatGPTRemove the tax rate of one location from this shop's tax table (DELETE /api/public/v1/taxes/{businessId}/locations/{location}), as the dashboard does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA and cannot be undone from here: customers in that location are then taxed with their continent or DEFAULT rate, or none. It is the last step of the tax workflow in the server instructions, after the user has confirmed it. appliesTo CUSTOMERS or BUSINESSES removes that side only, when the location has a rate for each (DISTINCT); the location goes once neither side has one. A location with one rate for everyone (SAME) is removed whole. Returns the tax settings as saved (TAX_LOCATION_NOT_FOUND when it had no rate).
remove_technology
ChatGPTStop offering a technology, as the pricing tools page deletes one (DELETE /api/public/v1/pricing/{businessId}/technologies/{technology}). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). DELETES REAL DATA and cannot be undone: the technology leaves the instant quote with its pricing, questions and lead times. withMachines: true deletes its machines too, with their materials (the dashboard ticks this by default); false keeps them. Restate the technology and its machines (list_technologies) and wait for the user to confirm, and to choose withMachines, before calling it. The answer names the machines removed or kept.
search_customers
ChatGPTFind this shop's customers: everyone who asked it for a quote or ordered (GET /api/public/v1/shop/{businessId}/customers), as its Customers page lists them. READ-ONLY, for an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). search matches the name or email. Answers { data, count }: each customer with _id, name, email, addresses and orderedFrom (totalOrders, totalModels, totalSpend). count is the total match count, not the page length. For one customer's quotes and orders, call get_customer with their _id.
set_coupon
ChatGPTAdd a coupon code to this shop, or change one (PUT /api/public/v1/pricing/{businessId}/coupons/{code}), as the dashboard does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: customers can use a new active code at once. It is the last step of the sales workflow in the server instructions, after the user has confirmed it. A code the shop has (in any case) is changed: only discount or isActive, as sent; it keeps its code and timesUsed. A new code needs its discount; it is 1 to 50 characters without spaces, and a shop below the Professional plan has at most 6 coupons (PLAN_LIMIT). isActive: false keeps a code but refuses it at checkout. Returns the coupons as saved.
set_lead_time_mode
ChatGPTSwitch between one lead time list for every technology (global) and one list per technology (per-technology), as the Lead time page does (PUT /api/public/v1/pricing/{businessId}/lead-times/mode). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the instant quote offers the other lists at once. Each mode keeps its own lists. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it.
set_lead_times
ChatGPTSet a lead time list, as the Lead time page saves it (PUT .../lead-times in global mode, .../technologies/{technology}/lead-times per technology). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. Send the WHOLE list from list_lead_times with the change made: keep a lead time by its id; one left out is removed (and the lead-time rules naming it with it). Leave technology out in global mode and name it per technology (LEAD_TIME_MODE otherwise). Names are unique, days and priceMultiplier 0.1 or more; with no default the first is.
set_minimum_prices
ChatGPTSet a technology's minimum prices (PUT /api/public/v1/pricing/{businessId}/ technologies/{technology}/minimums), as the Pricing tools page does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. - minOrderPrice: the least an order of this technology costs. - minPartPrice: the least one part costs. In the shop's currency, 0 for none. Send either or both; one left out is unchanged. They are the minimums of the technology's current calculator (each calculator has its own); a manual-quote technology has none (NO_MINIMUM_PRICES).
set_pricing_calculator
ChatGPTSwitch the calculator one of this shop's technologies is priced with (PUT /api/public/v1/pricing/{businessId}/technologies/{technology}/calculator), as the Pricing tools page does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: instant quotes are priced the new way at once. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. Calculators: formula (slicing-based), default (AI), pattern-matching (trained on the shop's own prices), custom (the shop's equation), metal-system (sheet metal), manual (no price: the shop quotes by hand). What a technology may use: - 3D_PRINTING: all but metal-system. formula only once the dashboard has set it up for that technology (FORMULA_NOT_SET_UP otherwise). - CNC_MACHINING: default, pattern-matching, custom, manual, metal-system. - SHEET_METAL: custom, manual, metal-system. Each calculator keeps its own settings and minimum prices; switching back finds them as they were. Returns the technology with its calculator and minimum prices.
set_shipping_method
ChatGPTAdd a shipping method to this shop, or change the one to the same destination (PUT /api/public/v1/pricing/{businessId}/shipping/methods), as the dashboard does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the instant quote offers it to customers from then on. It is the last step of the sales workflow in the server instructions, after the user has confirmed it. Prices are in the shop's currency (see get_shipping). A changed method keeps what is not sent: express is kept when left out, removed with null; freeShippingFrom likewise. Returns the shipping as saved.
set_tax_rate
ChatGPTSet the tax rate of one location in this shop's tax table (PUT /api/public/v1/taxes/{businessId}/locations), adding the location when it is not there yet, as the dashboard's tax editor does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: customers in that location are taxed at this rate from the next quote on. It is the last step of the tax workflow in the server instructions, after the user has confirmed the location, who it is for and the rate. taxValue is a percentage (20 for 20%). regions, for a country only: the regions (cities, as the dashboard lists them) with a rate of their own; every other region takes taxValue. Leave regions out for one rate in the whole country. Setting a rate replaces the one that location had for the same customers. Returns the tax settings as saved.
undo_setup_profile
ChatGPTUndo the shop's latest setup profile, from the backup taken when it was applied (POST /api/public/v1/shop/{businessId}/setup-profiles/rollback/{jobId}). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: it puts back the machines, pricing, shipping and taxes the shop had before that apply, whole, so any change made to them since is lost too. Say so, and wait for the user to confirm. Only the latest profile applied can be undone (SETUP_PROFILE_NOT_LATEST otherwise), once.
update_discounts
ChatGPTChange this shop's discounts, as the dashboard's Automation page saves them (PUT /api/public/v1/pricing/{businessId}/discounts). For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: the shop's instant quote discounts with it from the next quote on. It is the last step of the sales workflow in the server instructions, after the user has confirmed the change. Each list sent REPLACES that list whole, inactive rows included; a list left out is not touched. So send every row of the list as get_discounts returned it, with the change made: a list of one row leaves the shop with that row only. [] clears a list. - quantityDiscounts: { fromQuantity, toQuantity, discount, isActive }. - volumeDiscounts: { fromVolumeMm3, toVolumeMm3, discount, isActive }, in mm³ (1 cm³ = 1000 mm³). - promotions: { from, to, discount, isActive }, whole days as YYYY-MM-DD. As in the dashboard: a range starts above 0 and ends after it starts, ranges of a list never overlap, a discount is a whole % from 1 to 100, and a shop below the Professional plan has at most 6 promotions (PLAN_LIMIT). A refused list changes nothing. Material discounts are changed with update_material (discount). Returns the discounts as saved.
update_machine
ChatGPTChange one of this shop's machines: its name, build volume, hourly rate, ... (PUT /api/public/v1/machines/{businessId}/{machineId}). WRITES REAL DATA: the shop's instant quote prices with it from the next quote on. It is the last step of the production workflow in the server instructions, after the user has confirmed the change (current -> new value). changes: only the fields that change, as the dashboard's machine form edits them: - mark: the machine's name. - surfaceMachine: the build volume, "XxYxZ" in the machine's unit (e.g. "250x210x210"); "XxY" for sheet metal. unit: mm, cm or inch. - pricePerHour: the hourly rate, in the machine's currency. currency; power; description. - 3D printing slicer settings: numWalls, nozzleDiameter, supportDensity, maxVolumetricFlow, flowRateOverride, supportDepthPerArea, supportsEnabled, infillPattern. - typeMachine (the service) and technology move the machine to another process and its pricing. Not here: materials (use the material tools); business, machineOwner, status, marginMachine. A machine is added with add_machine and deleted with delete_machine. Returns the machine as saved.
update_material
ChatGPTChange a material of this shop's machines: price, colors, startup cost, density, name, ... (PUT /api/public/v1/machines/{businessId}/{machineId}/materials/{materialId}). WRITES REAL DATA: the shop's instant quote prices with it from the next quote on. It is the last step of the production workflow in the server instructions, after the user has confirmed the change (current -> new value, on which machines). targets: each machine's copy of the material to change, as { machineId, materialId } from list_machines. A material the shop runs on several machines is changed on each machine listed, as the dashboard saves the machines ticked together. changes: only the fields that change; the rest of the material is kept. - name; price: a number, per the unit, in the currency; currency: ISO code; unit: what the price is per (cm3, g, kg, lb; m2 for CNC; cm2, m2 or kg for sheet metal). - colors: [{ name, hex, isDefault? }]. The WHOLE list: it replaces the current one, so a color left out of it is removed. - startupCost: { price, currency }, charged once per order line, not per piece. - density: { value, unit: "g/cm3" }; discount; description; keyFeatures; materialType; isPublic. - thicknesses (sheet metal, CNC priced per thickness): the whole list, it replaces the current one. Renaming a material renames it on the shop's existing quotes and orders too, as the dashboard does. Which material is the default, and their order, are not set here. Returns one result per machine: saved: true with the material as saved, or saved: false with the reason, which the same call would meet again.
update_order_step
ChatGPTRename or recolour a production step, or change who sees it (PATCH .../order-statuses/{status}/steps/{name}). Fields left out stay as they are. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: a rename also renames the step on the shop's orders. A locked step is refused (STEP_LOCKED). Confirm with the user first.
update_pricing_rule
ChatGPTChange one of this shop's pricing rules (PATCH /api/public/v1/pricing/{businessId}/rules/{ruleId}), as the Pricing rules page does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. Only the fields sent change, and the whole rule must still make sense afterwards (same grammar as add_pricing_rule); send enabled: false to switch a rule off without deleting it.
update_profile
ChatGPTChange the shop's business profile, as its profile page saves it (PATCH /api/public/v1/shop/{businessId}/profile). Fields left out stay as they are. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: customers see it on quotes, invoices and the shop page. Read get_profile first, restate each change (old -> new) and wait for the user to confirm. - address: address, zip and country are needed together (ADDRESS_INCOMPLETE); country by name or ISO code, saved by name. - lang: the language of the shop's customer emails and PDFs, one the site offers. - vatNumber: on the payments page, so it needs the payments permission too. The currency, the logo and the public link name are changed in the dashboard.
update_question
ChatGPTChange one of a technology's questions, its options included (PATCH /api/public/v1/pricing/{businessId}/technologies/{technology}/questions/{questionId}), as the Data collection page's question editor does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA. It is the last step of the pricing workflow in the server instructions, after the user has confirmed it. Only the fields sent change. To change options, send the whole list from list_questions with the change made: an option left out is removed. Changing type to one answered differently drops the defaults, as the editor does. A locked question (see list_questions) is refused (QUESTION_LOCKED).
update_quote
ChatGPTChange one of this shop's demands (PUT /api/public/v1/demand/{demandId}). WRITES REAL DATA. Only the fields passed in change — status, prices, delivery dates, tracking, remarks and the other documented fields. STATUS: send changes.demandStatusInfo = { status, substatus }, by NAME as listed in the demand's availableStatuses (get_quote), e.g. { status: "completed", substatus: "delivered" }. A substatus alone changes only the substatus. A name this shop does not use is refused with the list of the ones it does — pick from it, ask the user when it is unclear, never invent one. The reply carries the updated statusHistory. EMAILS: sendOffer emails the customer the offer; sendAdditionalFeeMail emails them about additional fees. Both default to false. Only the shop that owns the demand can change it — a partner's own demands are readable but not editable. Ownership fields (business, machineOwner, client) cannot be changed here.
update_shipping
ChatGPTTurn this shop's pickup options on or off (PUT /api/public/v1/pricing/{businessId}/shipping), as the dashboard does. For an assistant connected through OAuth only (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA. It is the last step of the sales workflow in the server instructions, after the user has confirmed it. Only the options sent change; the pickup points themselves are managed in the dashboard. Returns the shipping as saved.
update_tax_settings
ChatGPTChange this shop's tax mode, default tax name or what the tax is charged on (PUT /api/public/v1/taxes/{businessId}). Only the settings sent change. For an assistant connected through OAuth only: as in the dashboard, the change is made by the user who signed in (NEEDS_SIGNED_IN_USER otherwise). WRITES REAL DATA: quotes made from then on are taxed this way. It is the last step of the tax workflow in the server instructions, after the user has confirmed it. Switching taxType to STRIPE needs a paid plan (STRIPE_TAX_NEEDS_PAID_PLAN). Returns the tax settings as saved.