Benchling Workflow Task API
Represents a unit of work within a `WorkflowTaskGroup`. Each task has a `status` that progressesthrough a configurable lifecycle (see `WorkflowTaskStatusLifecycle`), an optional `assignee`and `responsibleParties` for ownership, and a `scheduledOn` date for planning.Tasks may or may not produce `WorkflowOutput` instances upon completion. In flowchart workflows, tasks canhave upstream dependencies (`flowchartPreviousItems`) and downstream dependents(`flowchartNextItems`), with `rootWorkflowTask` pointing to the flowchart's entry point.Tasks support schema-defined custom fields via `schemaFields` and can be linked to `Study`entities for research coordination.
Benchling Workflow Task API is one of 203 APIs that Benchling publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Workflow Task. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, rate-limit docs, and a changelog.
This API exposes 10 operations across 9 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.
Requests are made against a single base URL, /api/v3.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Benchling Workflow Task API declares
3 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicApiKeyAuth).
It accepts HTTP basic authentication (basicClientIdSecretAuth).
It supports OAuth 2.0 (oAuth) using the clientCredentials flow.
By default, every request must be authenticated.
basicApiKeyAuth— Use issued API key for standard access to the APIbasicClientIdSecretAuth— Auth used as part of client credentials OAuth flow prior to receiving a bearer token.oAuth— OAuth2 Client Credentials flow intended for service access
Paths & Operations 10
Across 9 paths, the API surfaces 10 operations — 4 GET, 3 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Represents a unit of work within a WorkflowTaskGroup. Each task has a status that progresses through a configurable lifecycle (see WorkflowTaskStatusLifecycle), an optional assign…
Schemas 31
The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are WorkflowTask (21 properties), UpdateWorkflowTaskInputWithPathParams (6 properties), InternalServerError (6 properties), GeneralError (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Benchling 12
Other APIs Benchling publishes across the network.
This is an independent, third-party profile of Benchling Workflow Task API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.