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 Results API

Results represent the output of assays that have been performed. You can customize the schemas of results to fit your needs. Results can link to runs, entities, and other types.To learn more about creating results, [click here](https://docs.benchling.com/docs/example-creating-results).

Benchling Assay Results 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 Results. 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 11 operations across 10 paths, and defines 24 schemas. It is described by OpenAPI 3.0.1, at version 2.0.0.

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

11 operations 10 paths 24 schemas 3 GET8 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 Results 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 11

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

Assay Results 11

Results represent the output of assays that have been performed. You can customize the schemas of results to fit your needs. Results can link to runs, entities, and other types. T…

GET
/assay-results
List results
listAssayResults 20 params → 200
POST
/assay-results
Create 1 or more results.
createAssayResults body → 200400
GET
/assay-results/{assay_result_id}
Get a result
getAssayResult 1 param → 200400
POST
/assay-results:archive
Archive 1 or more results.
archiveAssayResults body → 200400
POST
/assay-results:bulk-create
Bulk create results
bulkCreateAssayResults body → 202400
GET
/assay-results:bulk-get
Gets multiple results specified by a list of IDs.
bulkGetAssayResults 1 param → 200400
POST
/assay-results:unarchive
Unarchive 1 or more results.
unarchiveAssayResults body → 200400
POST
/result-transactions
Create a transaction
createAssayResultsTransaction → 200
POST
/result-transactions/{transaction_id}/results
Create results in a transaction
createAssayResultsInTransaction 1 param body → 200400
POST
/result-transactions/{transaction_id}:abort
Abort a transaction
abortAssayResultsTransaction 1 param → 200
POST
/result-transactions/{transaction_id}:commit
Commit a transaction
commitAssayResultsTransaction 1 param → 200400

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are AssayResult (14 properties), Field (5 properties), AssayResultCreate (5 properties), BaseError (3 properties). Each schema is shown below with its type and property counts.

AssayResultIdsRequest
object
1 property 1 required
UserValidation
object
2 properties
Fields
object
AssayResultsBulkCreateInTableRequest
AssayResultsPaginatedList
object
2 properties
AssayResultCreate
object
5 properties 2 required
BadRequestError
object
1 property
BaseError
object
3 properties
ArchiveRecord
object
1 property
AssayResultsBulkGet
object
1 property
FieldType
string
AssayResultsCreateResponse
object
2 properties
AssayResultsArchive
AssayResultIdsResponse
object
1 property
UserSummary
AssayFieldsCreate
object
AssayResultTransactionCreateResponse
object
1 property
Field
object
5 properties 1 required
AssayResult
object
14 properties
PartySummary
object
3 properties
AssayResultsBulkCreateRequest
object
1 property 1 required
AsyncTaskLink
object
1 property
AssayResultsCreateErrorResponse
object
2 properties
SchemaSummary
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Benchling publishes across the network.

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

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