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 Procedure Parameter Planned Value API

Stores the expected or planned value for a parameter, set during procedure setup or run planning.Used to specify anticipated inputs before execution begins—for example, the target concentrationfor a reagent, the expected sample to use, or the equipment to employ. Scientists can laterconfirm these values (`ProcedureParameterConfirmationValue`) during execution or record actualresults (`ProcedureParameterMeasuredValue`). For material inputs, `amount` and `container` fieldsspecify planned quantities and storage locations. Links to `ProcedureParameterVersion` for theparameter definition and optionally to a `ProcedureMethodExecutionInstance` when associated witha specific run.

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

Tagged areas include ProcedureParameterPlannedValue. 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 8 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 8 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 Procedure Parameter Planned Value 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.

ProcedureParameterPlannedValue 2

Stores the expected or planned value for a parameter, set during procedure setup or run planning. Used to specify anticipated inputs before execution begins—for example, the targe…

GET
/procedure-parameter-planned-value/items
List ProcedureParameterPlannedValue items
ProcedureParameterPlannedValue.List 18 params → 200400403404429500
GET
/procedure-parameter-planned-value/{procedure_parameter_planned_value_id}
Get ProcedureParameterPlannedValue by ID
ProcedureParameterPlannedValue.Get 4 params → 200400403404429500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ProcedureParameterPlannedValue (11 properties), InternalServerError (6 properties), GeneralError (5 properties), ProcedureParameterValueLinkedPlateWell (3 properties). Each schema is shown below with its type and property counts.

InternalServerError
object
6 properties 5 required
ProcedureParameterValueLinkedPlateWell
object
Associates a parameter value with a specific well on a laboratory plate. Used within ProcedureParameterPlannedValue, ProcedureParameterConfirmationValue, and P…
3 properties
ProcedureMethodExecutionInstanceRef
object
2 properties
PrincipalRef
object
2 properties
ProcedureParameterPlannedValuePaginatedList
object
2 properties
ProcedureParameterPlannedValue
object
Stores the expected or planned value for a parameter, set during procedure setup or run planning. Used to specify anticipated inputs before execution begins—fo…
11 properties
ProcedureParameterVersionRef
object
2 properties
GeneralError
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

benchling-procedureparameterplannedvalue-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 Procedure Parameter Planned Value 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.