xPlantAPI

Overview

What the xPlant API is for, how it's shaped, and where to start.

The xPlant API connects your lab's own systems to your xPlant workspace: schedulers and spreadsheets, bench stations and label scanners, sensors and gateways, and storefronts. Anything your integration can do, it does inside one workspace, with only the permissions you gave its key.

The shape of every call

  • One host. Everything lives under https://app.xplantpro.com/api/v1. (www.xplantpro.com is the marketing site; API calls there are refused.)
  • One header. Authorization: Bearer <key>. Workspace keys start with xpk_; device tokens start with xpd_.
  • One envelope. Success is { "ok": true, "data": … }. Failure is { "ok": false, "data": null, "error": "…", "code": "STABLE_CODE" }. Branch on code.
  • Scopes you choose. A key can do exactly what its scopes allow, and nothing else. There is no default set.
  • Bounded by your plan and your role. Teams and Enterprise include the whole API; Hobby and Pro Lab keys can connect devices only. A key never does more than its owner can in xPlant. See Plans and access.

Start here

What you can build

Help

Email support@xplantpro.com, or see xPlant support. For what each plan includes, see plans and pricing. For security issues, see the repository's security policy.

Edit on GitHub

On this page