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 Protein Version API

A historical snapshot of an `Protein` at a specific point in time, preserving the completestructural state including domains, chains, and HELM notation. Protein versions form alineage that tracks changes over time. Each version records its creator and creation time.The parent field links to the version this one was derived from. Versions may become out ofsync with their constituent entities if underlying sequences change.

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

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

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

2 operations 2 paths 12 schemas 2 GET

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 Protein Version 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 2

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

ProteinVersion 2

A historical snapshot of an Protein at a specific point in time, preserving the complete structural state including domains, chains, and HELM notation. Protein versions form a lin…

GET
/protein-version/items
List ProteinVersion items
ProteinVersion.List 11 params → 200400403404429500
GET
/protein-version/{protein_version_id}
Get ProteinVersion by ID
ProteinVersion.Get 4 params → 200400403404429500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are ProteinVersion (11 properties), ProteinChain (6 properties), InternalServerError (6 properties), ProteinDomain (5 properties). Each schema is shown below with its type and property counts.

ProteinFormatChainPosition
object
Defines each instance of a polypeptide chain within a ProteinFormat, specifying the chain type and its constituent domains. Each chain position has a unique re…
4 properties
ProteinFormatRef
object
2 properties
InternalServerError
object
6 properties 5 required
ProteinVersion
object
A historical snapshot of an Protein at a specific point in time, preserving the complete structural state including domains, chains, and HELM notation. Protein…
11 properties
ProteinDomain
object
Represents a domain within an Protein, containing the actual amino acid sequence for a specific label. Unlike ProteinFormatDomain which is a template, ProteinD…
5 properties
AaSequenceRef
object
2 properties
ProteinVersionPaginatedList
object
2 properties
PrincipalRef
object
2 properties
ProteinVersionRef
object
2 properties
ProteinFormatDomainPosition
object
Defines a domain position within a1 ProteinFormat, specifying the domain type and identity of each physical domain in the protein format. Each domain position…
4 properties
GeneralError
object
5 properties 5 required
ProteinChain
object
Represents a polypeptide chain within an Protein, containing the domain composition. Each chain has a computed label derived from the format.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

benchling-proteinversion-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 Protein Version 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.