Benchling · Schema

OligoBaseRequest

Life SciencesBiotechR&DMolecular BiologyLaboratory Information ManagementElectronic Lab NotebookAssay ManagementInventory ManagementSequence ManagementExperiment WorkflowsRESTWebhooks

Properties

Name Type Description
aliases array Aliases to add to the Oligo
authorIds array IDs of users to set as the Oligo's authors.
bases string Base pairs of the oligo.
customFields object Custom fields to add to the Oligo. Every field should have its name as a key, mapping to an object with information about the value of the field.
fields object Fields to set on the Oligo. Must correspond with the schema's field definitions. Every field should have its name as a key, mapping to an object with information about the value of the field.
folderId string ID of the folder containing the Oligo.
name string Name of the Oligo.
schemaId string ID of the oligo's schema.
View JSON Schema on GitHub

JSON Schema

OligoBaseRequest.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://api-evangelist.github.io/benchling/json-schema/OligoBaseRequest.json",
  "title": "OligoBaseRequest",
  "properties": {
    "aliases": {
      "description": "Aliases to add to the Oligo",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "authorIds": {
      "description": "IDs of users to set as the Oligo's authors.",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "bases": {
      "description": "Base pairs of the oligo.\n",
      "type": "string"
    },
    "customFields": {
      "allOf": [
        {
          "$ref": "#/components/schemas/CustomFields"
        }
      ],
      "description": "Custom fields to add to the Oligo. Every field should have its name as a key, mapping to an object with information about the value of the field.\n"
    },
    "fields": {
      "allOf": [
        {
          "$ref": "#/components/schemas/Fields"
        }
      ],
      "description": "Fields to set on the Oligo. Must correspond with the schema's field definitions. Every field should have its name as a key, mapping to an object with information about the value of the field.\n"
    },
    "folderId": {
      "description": "ID of the folder containing the Oligo.\n",
      "type": "string"
    },
    "name": {
      "description": "Name of the Oligo.\n",
      "type": "string"
    },
    "schemaId": {
      "description": "ID of the oligo's schema.\n",
      "type": "string"
    }
  },
  "type": "object"
}