TrendyBuilders logoTrendyBuilders
Open workspace ↗

External integrations & API

Connect external tools to a bounded numeric calculation API, or convert a portfolio review into a flat CSV locally.

This first increment adds no account keys or third-party provider connection. Saved project endpoints retain existing owner-session protection. The public calculation endpoint reads only submitted numbers and batch labels; it does not read saved projects, send email, access private files, create payments or forward data to another provider.

Versioned cutting-plan API

POST https://trendybuilders.com/api/v1/cutting-plan · API version 1.0.0 · request version: 1 · uncompressed application/json.

OpenAPI 3.1 JSON contract ↗ · API discovery & limits ↗ · Interactive cutting planner ↗

No credentials required. Browser clients use credentials: "omit"; public CORS allows POST and Content-Type without credentialed access. Never send tokens, passwords, personal data, customer records, project names or external URLs. Unknown request fields are rejected.

Errors use an API version, request ID, code and message: 400 JSON, 405 method, 408 body timeout, 413 size, 415 content type/encoding, 422 input/candidate, 429 quota, 500 internal. The application does not persist request bodies or results; ordinary hosting access metadata still applies. Send only non-sensitive numeric inputs.

Run the numeric API example

This sends only the fixed illustrative numbers below. Account cookies and credentials are omitted.

{
  "version": 1,
  "stocks": [
    {
      "id": "N1",
      "length": 6000,
      "quantity": 2
    },
    {
      "id": "N2",
      "length": 4500,
      "quantity": 1
    }
  ],
  "offcuts": [
    {
      "id": "O1",
      "length": 2100,
      "quantity": 2
    }
  ],
  "kerf": 3,
  "minimumReusable": 250,
  "demands": [
    {
      "length": 2400,
      "quantity": 1
    },
    {
      "length": 1800,
      "quantity": 2
    }
  ]
}

Supplier catalogue & RFQ CSV exchange ↗ supports local exact-SKU commercial review without a provider account or saved-project writes. · Regional rate dataset importer ↗ reviews declared licence/region/date permissions locally; no commercial dataset supplied.

Portable clients — no new service

These readable Node.js scripts use built-in modules only, with Node 18 or later. Existing project tooling uses Node 24. They refuse to overwrite an existing output file. Running the cutting client makes one request to the fixed TB endpoint; the portfolio adapter performs no network requests.

node tb-cutting-client.mjs numeric-request.json new-response.json
node tb-portfolio-csv.mjs portfolio-review.json new-portfolio.csv

Portfolio review → CSV for spreadsheets / BI

  1. Use Portfolio analytics, select project scopes, confirm scope review and export portfolio JSON.
  2. Run the local adapter with that review and a new CSV output path. It validates the export, ignores supplied group totals and recomputes separate groups from selected rows.
  3. Import the flat UTF-8 CSV into your spreadsheet or BI tool. Keep Currency, Estimate type, Mode and partial-coverage columns. Group only compatible currency/type rows; the CSV contains selected project rows, not repeated group totals.

This is a file-format bridge, not a native live Power BI, Excel, supplier or accounting connector. It does not fetch TB account data, authenticate another app, import changes, convert currencies or certify amounts. Source fingerprints are references, not signatures. The adapter cannot independently revalidate source project documents. Keep exported names and amounts private. Additional providers, private external credentials, write APIs and automated synchronization remain separate work.

Contract policy: use the documented v1 endpoint and explicit request version. The current finite-supply method and limits are declared in the response/docs; do not depend on globally optimal patterns or an undocumented property. No paid resource or subscription is added by this increment.