Labstep website screenshot

Labstep

Labstep is a cloud-based Electronic Lab Notebook (ELN) and research data management platform for life-science, chemistry and pharma R&D teams. It combines step-by-step interactive protocols, structured experiment data capture, inventory and sample management with QR scanning, order management, instrument/device integration, chemistry and sequence tooling, and integrated Jupyter Notebooks for analysis — all under an audit trail with electronic signatures and sample lineage. Labstep exposes a public REST API at api.labstep.com secured with a per-user API key, plus an officially maintained Python SDK (labstepPy) and an R package (labstepR) that wrap the same generic entity surface used by the application itself.

Labstep publishes 1 API on the APIs.io network. Tagged areas include Company, Electronic Lab Notebook, Life Sciences, Laboratory, and Research Data Management.

Labstep’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 22 more developer resources.

40.1/100 thin ▬ flat Agent 21/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs
CompanyElectronic Lab NotebookLife SciencesLaboratoryResearch Data ManagementScientific SoftwareInventory ManagementBiotechnologyChemistryCompliance

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 40.1/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 10.5 / 20
Operational Transparency 4.1 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 21/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/labstep: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Labstep API

The Labstep REST API exposes the same generic entity surface the Labstep application uses — experiments, protocols, resources, resource items, locations, devices, device data, o...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Labstep Authentication

apiKey/http · 2 schemes

SECURITY

Labstep Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: labstep
name: Labstep
description: Labstep is a cloud-based Electronic Lab Notebook (ELN) and research data management platform for life-science,
  chemistry and pharma R&D teams. It combines step-by-step interactive protocols, structured experiment data capture, inventory
  and sample management with QR scanning, order management, instrument/device integration, chemistry and sequence tooling,
  and integrated Jupyter Notebooks for analysis — all under an audit trail with electronic signatures and sample lineage.
  Labstep exposes a public REST API at api.labstep.com secured with a per-user API key, plus an officially maintained Python
  SDK (labstepPy) and an R package (labstepR) that wrap the same generic entity surface used by the application itself.
url: https://raw.githubusercontent.com/api-evangelist/labstep/refs/heads/main/apis.yml
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://www.labstep.com/favicon.ico
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Electronic Lab Notebook
- Life Sciences
- Laboratory
- Research Data Management
- Scientific Software
- Inventory Management
- Biotechnology
- Chemistry
- Compliance
apis:
- aid: labstep:labstep-api
  name: Labstep API
  description: The Labstep REST API exposes the same generic entity surface the Labstep application uses — experiments, protocols,
    resources, resource items, locations, devices, device data, orders, metadata, files, tags, collections, workspaces and
    users. Requests are authenticated with a per-user API key sent in an `apikey` header (an Authorization Bearer token form
    is also supported), and entities are read, filtered, created, edited and deleted under `/api/generic/<entity>` with a
    POST `/filter` endpoint for structured predicate queries.
  humanURL: https://help.labstep.com/en/collections/1913112-labstep-api
  baseURL: https://api.labstep.com
  tags:
  - Electronic Lab Notebook
  - Research Data
  - Laboratory
  properties:
  - type: Documentation
    url: https://help.labstep.com/en/collections/1913112-labstep-api
  - type: GettingStarted
    url: https://help.labstep.com/en/articles/1786226-getting-started-with-the-labstep-api
  - type: APIReference
    url: https://labsteppy.readthedocs.io/en/latest/
  - type: Authentication
    url: authentication/labstep-authentication.yml
  - type: Conventions
    url: conventions/labstep-conventions.yml
  - type: ErrorCatalog
    url: errors/labstep-error-codes.yml
  - type: DataModel
    url: data-model/labstep-data-model.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.labstep.com
- type: DeveloperPortal
  url: https://help.labstep.com/en/collections/1913112-labstep-api
- type: Documentation
  url: https://labsteppy.readthedocs.io/en/latest/
- type: APIReference
  url: https://labsteppy.readthedocs.io/en/latest/
- type: GettingStarted
  url: https://help.labstep.com/en/articles/1786226-getting-started-with-the-labstep-api
- type: Support
  url: https://help.labstep.com
- type: HelpCenter
  url: https://help.labstep.com
- type: Blog
  url: https://www.labstep.com/blogs/blog
- type: GitHubOrganization
  url: https://github.com/Labstep
- type: Pricing
  url: https://www.labstep.com/industry-pricing
- type: SignUp
  url: https://app.labstep.com/signup
- type: Login
  url: https://app.labstep.com/login
- type: TermsOfService
  url: https://www.labstep.com/terms-conditions
- type: PrivacyPolicy
  url: https://www.labstep.com/privacy-policy
- type: Security
  url: https://www.labstep.com/security
- type: Compliance
  url: https://www.labstep.com/security
- type: ChangeLog
  url: https://help.labstep.com/en/collections/945011-release-notes
- type: Packages
  url: packages/labstep-packages.yml
- type: SDKs
  url: packages/labstep-packages.yml
- type: WellKnown
  url: well-known/labstep-well-known.yml
- type: LLMsTxt
  url: llms/labstep-llms.txt
- type: Conformance
  url: conformance/labstep-conformance.yml
- type: Authentication
  url: authentication/labstep-authentication.yml
- type: Conventions
  url: conventions/labstep-conventions.yml
- type: ErrorCatalog
  url: errors/labstep-error-codes.yml
- type: Lifecycle
  url: lifecycle/labstep-lifecycle.yml
- type: ChangeLog
  url: changelog/labstep-changelog.yml
- type: DataModel
  url: data-model/labstep-data-model.yml
- type: DomainSecurity
  url: security/labstep-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence