A workflow request submitted from a `RequestV2Definition` (known as "Request Template" in the UI).When a request is submitted (status transitions to SENT), a `WorkflowTaskGroup` is automaticallycreated to fulfill the request, containing tasks defined by the template's workflow task schema.Requests are authored in a `Document` and stored within `Folder`s. The `status` field tracksthe request lifecycle: requests start as DRAFT while being composed, become SENT when submitted,and transition to FULFILLED when all associated workflow tasks reach terminal status. Requestscan also be DISCARDED (before submission) or CANCELLED (after submission). Users canbe added as `watchers` to receive notifications about request status changes. Requests can belinked to `Study` entities for research coordination (see `Studyable` interface).
Benchling Request V2 Submission API is one of 203 APIs that Benchling publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include RequestV2Submission. 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
3 operations
across 3 paths,
and defines 38 schemas.
It is described by OpenAPI 3.2.0, at version 2.0.0.
Requests are made against a single base URL, /api/v3.
3 operations3 paths38 schemas3 GET
Metadata
The identity and technical contract details declared by the specification.
Benchling Request V2 Submission 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 3
Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.
RequestV2Submission 3
A workflow request submitted from a RequestV2Definition (known as "Request Template" in the UI). When a request is submitted (status transitions to SENT), a WorkflowTaskGroup is a…
The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are RequestV2Submission (17 properties), LegacyAppInstallation (17 properties), AppInstallation (10 properties), User (9 properties). Each schema is shown below with its type and property counts.
LegacyAppInstallation
object
Represents a legacy (pre-App Store) Benchling App installation on a tenant. Legacy apps are configured directly with webhook URLs and configuration specs rathe…
17 properties
JsonAppConfigSpec
object
Specifies that an app configuration field should accept a JSON value.
2 properties
DateAppConfigSpec
object
Specifies that an app configuration field should accept a date value.
2 properties
CanvasFeatureSpec
object
Defines a canvas feature for a Benchling App, which provides an embedded UI surface within entries or templates. Canvases allow apps to render custom interacti…
4 properties
AppMessageSubscription
object
Represents an app's subscription to a specific event type, specifying the event type and how notifications should be delivered (see DeliveryMethod).
3 properties
RequestV2Submission
object
A workflow request submitted from a RequestV2Definition (known as "Request Template" in the UI). When a request is submitted (status transitions to SENT), a Wo…
17 properties
DropdownAppConfigSpec
object
Specifies that an app configuration field should be a dropdown with predefined options.
3 properties
ArrayAppConfigSpec
object
Specifies that an app configuration field should accept an array of values.
5 properties
PrincipalUnpaginatedList
object
1 property
AppInstallation
object
Represents an installed Benchling App on a tenant, created from an AppDefinitionVersion. App installations store tenant-specific configuration values and featu…
10 properties
ServicePrincipal
object
Represents a non-human identity used for system integrations and automated processes within Benchling. Service principals act as the identity for service accou…
4 properties
AssayRunFeatureSpec
object
Defines an assay run feature for a Benchling App, allowing the app to process or generate lab automation run data.
3 properties
User
object
Represents a human user in Benchling who can log in, perform actions, and own data. Users belong to one or more Organizations and may be members of Teams withi…
9 properties
AppHomepageFeatureSpec
object
Defines a homepage feature for a Benchling App, providing a dedicated landing page within the Benchling application for the app's functionality.
3 properties
Principal
object
InternalServerError
object
6 properties5 required
AppConfigWorkflowTaskSchemaOutput
object
Defines the output field structure for a workflow task schema configuration.
2 properties
ResourceAppConfigSpec
object
Specifies that an app configuration field should reference a Benchling object instance. The type field identifies the kind of object required, matching the Ben…
3 properties
RequestV2DefinitionRef
object
2 properties
IntegerAppConfigSpec
object
Specifies that an app configuration field should accept an integer value.
3 properties
AppConfigOption
object
Defines a configuration option in an app's configuration schema. Each option has a name, optional description, and a configSpec defining the expected value typ…
4 properties
BooleanAppConfigSpec
object
Specifies that an app configuration field should accept a boolean value.
2 properties
PrincipalRef
object
2 properties
TextAppConfigSpec
object
Specifies that an app configuration field should accept a text string.
3 properties
FolderRef
object
2 properties
FloatAppConfigSpec
object
Specifies that an app configuration field should accept a floating-point number.
3 properties
AssayRunFeatureValue
object
Links an app's assay run feature to a specific resource (typically a run schema) on a tenant. The featureId identifies the feature from the app definition, and…
3 properties
WorkflowTaskGroupRef
object
2 properties
AppConfigDropdownOption
object
Defines an option within a dropdown-type app configuration field.
4 properties
WorkflowTaskSchemaAppConfigSpec
object
Specifies that an app configuration field should reference a workflow task schema. Kept separate from SchemaAppConfigSpec because it supports output field defi…
4 properties
ArrayAppConfigOption
object
A config option nested within an array-type app configuration field. Structurally identical to AppConfigOption — it has a name and a configSpec — but its confi…
4 properties
EntitySchemaAppConfigSpec
object
Specifies that an app configuration field should reference an entity schema. Kept separate from SchemaAppConfigSpec because it carries a subtype constraint.
4 properties
AppConfigFieldDefinition
object
Defines a field within an app configuration that references schema fields. Specifies the field name, type, whether it accepts multiple values, and whether it i…
7 properties
DateTimeAppConfigSpec
object
Specifies that an app configuration field should accept a datetime value.
2 properties
SchemaAppConfigSpec
object
Specifies that an app configuration field should reference one of the schema types that share a common structure: containerschema, plateschema, locationschema,…
4 properties
SecureTextAppConfigSpec
object
Specifies that an app configuration field should accept secure (encrypted) text. Used for sensitive data like API keys or credentials.
2 properties
GeneralError
object
5 properties5 required
RequestV2SubmissionPaginatedList
object
2 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Benchling Request V2 Submission 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.
