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 Assay Runs API

Runs capture the details / parameters of a run that was performed. Results are usually nested under a run.

Benchling Assay Runs API is one of 58 APIs that Benchling publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Assay Runs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a changelog, and a status page.

This API exposes 9 operations across 7 paths, and defines 31 schemas. It is described by OpenAPI 3.0.1, at version 2.0.0.

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

9 operations 7 paths 31 schemas 5 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
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 Assay Runs 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 9

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

Assay Runs 9

Runs capture the details / parameters of a run that was performed. Results are usually nested under a run.

GET
/assay-runs
List runs
listAssayRuns 6 params → 200
POST
/assay-runs
Create 1 or more runs.
createAssayRuns body → 200400
GET
/assay-runs/{assay_run_id}
Get a run
getAssayRun 1 param → 200400
PATCH
/assay-runs/{assay_run_id}
Update a run
updateAssayRun 1 param body → 200400
GET
/assay-runs/{assay_run_id}/automation-input-generators
list AutomationInputGenerators by Run
listAutomationInputGenerators 3 params → 200400
GET
/assay-runs/{assay_run_id}/automation-output-processorsdeprecated
list AutomationOutputProcessors by Run
listAutomationOutputProcessorsDeprecated 2 params → 200400
POST
/assay-runs:archive
Archive Assay Runs
archiveAssayRuns body → 200400
GET
/assay-runs:bulk-get
Bulk get runs by ID
bulkGetAssayRuns 1 param → 200
POST
/assay-runs:unarchive
Unarchive Assay Runs
unarchiveAssayRuns body → 200400

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are AssayRun (14 properties), LabAutomationTransform (9 properties), AssayRunCreate (6 properties), Blob (5 properties). Each schema is shown below with its type and property counts.

SchemaSummary
object
2 properties
Fields
object
LabAutomationTransform
object
9 properties
Blob
object
5 properties
AssayRunsBulkCreateRequest
object
1 property 1 required
AssayRunsArchive
object
The request body for archiving Assay Runs.
2 properties 2 required
AutomationOutputProcessor
AssayRunsArchivalChange
object
IDs of all Assay Runs that were archived / unarchived.
1 property
AssayRunValidationStatus
string
Must be either VALID or INVALID
BadRequestError
object
1 property
BaseError
object
3 properties
ArchiveRecord
object
1 property
DeprecatedAutomationOutputProcessorsPaginatedList
object
Deprecated - A paginated list of automation output processors
2 properties
AssayRunUpdate
object
2 properties
FieldType
string
UserSummary
AssayFieldsCreate
object
AssayRunCreate
object
6 properties 2 required
AssayRunsPaginatedList
object
2 properties
Field
object
5 properties 1 required
PartySummary
object
3 properties
AutomationProgressStats
object
Processing progress information.
3 properties
AssayRun
object
14 properties
LabAutomationBenchlingAppErrors
object
1 property
AutomationFileInputsPaginatedList
object
2 properties
AssayRunsUnarchive
object
The request body for unarchiving Assay Runs.
1 property 1 required
AssayRunsBulkCreateResponse
object
2 properties
AutomationFile
object
5 properties
AutomationInputGenerator
AssayRunsBulkCreateErrorResponse
object
2 properties
AssayRunsBulkGet
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

benchling-assay-runs-api-openapi.yml Raw ↑

Other APIs Benchling publishes across the network.

Benchling AA Sequences API
Benchling Apps API
Benchling Assay Results 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
Benchling Custom Notations API
Where this information came from

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