The key is scoped to the SKUs on the invite and to this one customer relationship. It cannot read your systems, and it cannot touch anything beyond stock numbers for those SKUs. Keys are stored hashed on our side, and either side can revoke at any time.

What if we stop wanting to share?

Ask your customer to revoke the key, or simply stop sending reports. Your numbers go stale, and your customer sees exactly that: last reported N days ago, not a false current figure.

Do we need a TuringDock account?

No. The key from the invite email is all you need. No signup, no login, no software to install.

How often should we send?

Whenever your stock changes, or on whatever schedule suits you. Daily is plenty. Each report replaces the last, so sending more often never causes problems.

TuringDock supplier link

Share stock levels with your customer in five minutes.

Your customer uses TuringDock to plan their production. This link shares your on-hand quantities for only the parts they buy from you, so they can plan without emailing you.

What is shared (and what is not)

The key in your invite is scoped to a fixed list of SKUs: the parts your customer buys from you. It reports stock numbers for that list and nothing else.

Shared

On-hand quantity for the SKUs on the list.
Optionally, the input parts you build those SKUs from and their quantities, so your customer can see build capacity. Only if you choose to include them.

Never shared

Your prices or costs.
Your other customers.
Anything else in your books. The key has no read access to your systems; you send numbers, it stores them.

How to connect

Find your key. The invite email from your customer contains a key that starts with tdsl_. Keep it private. Your customer can revoke it at any time, and it only covers this one relationship.
Check your scope. Call GET https://api.turingdock.com/supplier-link/v1/scope with the header Authorization: Bearer <your key>. It returns the list of SKUs you are being asked to report, so you can confirm the scope before sending anything.
Report stock. Send POST https://api.turingdock.com/supplier-link/v1/stock with the same header plus Content-Type: application/json. The body is an array of SKUs with on-hand quantities. inputs is optional: include it only if you want your customer to see build capacity. Send whenever stock changes or on a schedule; each report replaces the last.

curl -X POST https://api.turingdock.com/supplier-link/v1/stock \
  -H "Authorization: Bearer tdsl_your_key_here" \
  -H "Content-Type: application/json" \
  -d '[{
    "sku": "LIFEPO4-CELL-100AH",
    "onHand": 400,
    "inputs": [
      { "sku": "CELL-RAW-3.2V", "qtyPerAssembly": 4, "onHand": 3600 }
    ]
  }]'

From Sage 50 or QuickBooks?

Export your inventory report and have whoever runs your systems map it to the call above. Direct QuickBooks and email connections are coming.

Common questions from suppliers

Is this secure?: The key is scoped to the SKUs on the invite and to this one customer relationship. It cannot read your systems, and it cannot touch anything beyond stock numbers for those SKUs. Keys are stored hashed on our side, and either side can revoke at any time.
What if we stop wanting to share?: Ask your customer to revoke the key, or simply stop sending reports. Your numbers go stale, and your customer sees exactly that: last reported N days ago, not a false current figure.
Do we need a TuringDock account?: No. The key from the invite email is all you need. No signup, no login, no software to install.
What does it cost?: Nothing, ever, for suppliers.
How often should we send?: Whenever your stock changes, or on whatever schedule suits you. Daily is plenty. Each report replaces the last, so sending more often never causes problems.