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

Mixtures are solutions comprised of multiple ingredients where the exact quantities of each ingredient are important to track. Each ingredient is uniquely identified by its component entity.

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

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

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

8 operations 6 paths 33 schemas 2 GET1 PATCH5 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 Mixtures 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 6 paths, the API surfaces 8 operations — 2 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Mixtures 8

Mixtures are solutions comprised of multiple ingredients where the exact quantities of each ingredient are important to track. Each ingredient is uniquely identified by its compon…

GET
/mixtures
List mixtures
listMixtures 22 params → 200400
POST
/mixtures
Create a mixture
createMixture body → 201400503
GET
/mixtures/{mixture_id}
Get a mixture
getMixture 1 param → 200400
PATCH
/mixtures/{mixture_id}
Update a mixture
updateMixture 1 param body → 200400
POST
/mixtures:archive
Archive mixtures
archiveMixtures body → 200400
POST
/mixtures:bulk-create
Bulk Create mixtures
bulkCreateMixtures body → 202400
POST
/mixtures:bulk-update
Bulk Update mixtures
bulkUpdateMixtures body → 202400
POST
/mixtures:unarchive
Unarchive mixtures
unarchiveMixtures body → 200400

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Mixture (21 properties), MixtureUpdate (11 properties), Ingredient (10 properties), IngredientWriteParams (8 properties). Each schema is shown below with its type and property counts.

MixtureBulkUpdate
EntityLabels
object
3 properties
MixturesArchive
object
The request body for archiving mixtures.
2 properties 2 required
Fields
object
MixturesBulkUpdateRequest
object
1 property
CustomField
object
1 property
BadRequestError
object
1 property
MixturesArchivalChange
object
IDs of all mixtures that were archived or unarchived.
1 property
SchemaFieldsQueryParam
object
BaseError
object
3 properties
ArchiveRecord
object
1 property
IngredientMeasurementUnits
string
FieldType
string
NamingStrategy
string
Specifies the behavior for automatically generated names when registering an entity. - NEWIDS: Generate new registry IDs - IDSFROMNAMES: Generate registry IDs…
MixturesBulkCreateRequest
object
1 property 1 required
UserSummary
Mixture
object
21 properties
ContainerLabels
object
3 properties
Field
object
5 properties 1 required
PartySummary
object
3 properties
MixtureCreate
AsyncTaskLink
object
1 property
CustomFields
object
MixtureUpdate
object
11 properties
MixturesUnarchive
object
The request body for unarchiving mixtures.
1 property 1 required
MixturesPaginatedList
object
2 properties
IngredientWriteParams
object
8 properties 8 required
RegistrationOrigin
object
2 properties
CreateEntityIntoRegistry
object
4 properties
MixtureMeasurementUnits
string
Ingredient
object
10 properties
SchemaSummary
object
2 properties
EntityArchiveReason
string
The reason for archiving the provided entities. Accepted reasons may differ based on tenant configuration.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

benchling-mixtures-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 Mixtures 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.