How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Benchling Workflow Output API

Represents the result or product of completing a `WorkflowTask`. Each output is associatedwith a single task. Outputs can contain schema-definedfields that capture structured data from task execution. In flowchart workflows, outputscan serve as inputs to downstream tasks, enabling data flow between workflow steps.The output schema is defined by the `WorkflowOutputSchema` associated with the parent task's schema.

Benchling Workflow Output API is one of 203 APIs that Benchling publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include WorkflowOutput. 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 8 operations across 7 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, /api/v3.

8 operations 7 paths 14 schemas 2 GET3 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://{tenant}.benchling.com/api/v2
Authentication
HTTP Basic, HTTP Basic, OAuth 2.0
License
Resource Areas
1

Authentication & Security 3

Benchling Workflow Output 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 API
  • basicClientIdSecretAuth — 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 8

Across 7 paths, the API surfaces 8 operations — 2 GET, 3 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

WorkflowOutput 8

Represents the result or product of completing a WorkflowTask. Each output is associated with a single task. Outputs can contain schema-defined fields that capture structured data…

POST
/workflow-output
Create WorkflowOutput
WorkflowOutput.Create 1 param body → 201400403404429500
GET
/workflow-output/items
List WorkflowOutput items
WorkflowOutput.List 17 params → 200400403404429500
GET
/workflow-output/{workflow_output_id}
Get WorkflowOutput by ID
WorkflowOutput.Get 4 params → 200400403404429500
PATCH
/workflow-output/{workflow_output_id}
Update WorkflowOutput
WorkflowOutput.Update 2 params body → 200400403404429500
POST
/workflow-output:batch-create
Batch create WorkflowOutput
WorkflowOutput.BatchCreate 1 param body → 201400403404429500
PATCH
/workflow-output:batch-update
Batch update WorkflowOutput
WorkflowOutput.BatchUpdate 1 param body → 200400403404429500
POST
/workflow-output:bulk-create
Bulk create WorkflowOutput
WorkflowOutput.BulkCreate 1 param body → 202400403404429500
PATCH
/workflow-output:bulk-update
Bulk update WorkflowOutput
WorkflowOutput.BulkUpdate 1 param body → 202400403404429500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are WorkflowOutput (11 properties), InternalServerError (6 properties), GeneralError (5 properties), WorkflowOutputSchemaRef (2 properties). Each schema is shown below with its type and property counts.

FieldValueInput
object
1 property 1 required
AnyType
WorkflowOutput
object
Represents the result or product of completing a WorkflowTask. Each output is associated with a single task. Outputs can contain schema-defined fields that cap…
11 properties
UpdateWorkflowOutputInputWithPathParams
object
2 properties 1 required
InternalServerError
object
6 properties 5 required
AsyncTaskLink
object
2 properties
BulkImport
object
1 property 1 required
PrincipalRef
object
2 properties
WorkflowOutputSchemaRef
object
2 properties
WorkflowOutputPaginatedList
object
2 properties
UpdateWorkflowOutputInput
object
1 property
CreateWorkflowOutputInput
object
2 properties 1 required
WorkflowTaskRef
object
2 properties
GeneralError
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

benchling-workflowoutput-api-openapi.yml Raw ↑

Other APIs Benchling publishes across the network.

Benchling AA Sequences API
Benchling Apps API
Benchling Assay Results API
Benchling Assay Runs API
Benchling Audit API
Benchling Authentication API
Benchling Blobs API
Benchling Boxes API
Benchling Codon Usage Tables API
Benchling Connect API
Benchling Containers API
Benchling Custom Entities API
Where this information came from

This is an independent, third-party profile of Benchling Workflow Output 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.