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

A hierarchical container for organizing entities, notebook entries, and other items withina Project. Folders support nested structures through parent-child relationships (see`parent`), enabling users to create logical groupings that mirror laboratory organizationor experimental workflows. Folders belong to a Project (see `project`) and inherit accesscontrol through collaborations (see `Collaboration`). Items stored in folders implementthe FolderItem interface. Folders can be starred for quick access (via `Starrable`) andarchived with lineage tracking that affects contained items (via `ArchivableWithLineage`).

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

Tagged areas include Folder. 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 12 operations across 10 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.

12 operations 10 paths 14 schemas 1 DELETE3 GET3 PATCH5 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 Folder 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 12

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

Folder 12

A hierarchical container for organizing entities, notebook entries, and other items within a Project. Folders support nested structures through parent-child relationships (see par…

POST
/folder
Create Folder
Folder.Create 1 param body → 201400403404429500
GET
/folder/items
List Folder items
Folder.List 17 params → 200400403404429500
DELETE
/folder/{folder_id}
Delete Folder
Folder.Delete 2 params → 204400403404429500
GET
/folder/{folder_id}
Get Folder by ID
Folder.Get 4 params → 200400403404429500
PATCH
/folder/{folder_id}
Update Folder
Folder.Update 2 params body → 200400403404429500
GET
/folder/{folder_id}/children/items
List Folder items
Folder.children.List 2 params → 200400403404429500
POST
/folder/{folder_id}:move
Move a Folder into another Folder
Folder.Move 2 params body → 200400403404429500
POST
/folder:batch-create
Batch create Folder
Folder.BatchCreate 1 param body → 201400403404429500
POST
/folder:batch-delete
Batch delete Folder
Folder.BatchDelete 1 param body → 200400403404429500
PATCH
/folder:batch-update
Batch update Folder
Folder.BatchUpdate 1 param body → 200400403404429500
POST
/folder:bulk-create
Bulk create Folder
Folder.BulkCreate 1 param body → 202400403404429500
PATCH
/folder:bulk-update
Bulk update Folder
Folder.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 Folder (11 properties), InternalServerError (6 properties), UpdateFolderInputWithPathParams (5 properties), GeneralError (5 properties). Each schema is shown below with its type and property counts.

UpdateFolderInputWithPathParams
object
5 properties 1 required
ProjectRef
object
2 properties
Folder
object
A hierarchical container for organizing entities, notebook entries, and other items within a Project. Folders support nested structures through parent-child re…
11 properties
InternalServerError
object
6 properties 5 required
AsyncTaskLink
object
2 properties
BulkImport
object
1 property 1 required
FolderPaginatedList
object
2 properties
DeleteFolderInputWithPathParams
object
1 property 1 required
FolderRef
object
2 properties
UpdateFolderInput
object
4 properties
FolderUnpaginatedList
object
1 property
CreateFolderInput
object
3 properties 2 required
MoveFolderInput
object
1 property 1 required
GeneralError
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

benchling-folder-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 Folder 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.