Introduction

REST Data Access Web Service Reference Specification

Page Contents

A summary of specific versions, resources, and XML namespaces is provided below.

• Supported Versions
• Changes in Current Revision
• Requesting an API Version
• REST
• API Data Types
  • API Data Type Schemas
• XML Data Elements
• XML Data Types

The REST Data Access Web Service is the fundamental interface in the GenoLogics Rapid Scripting API. Data is provided in XML with data access methods via HTTP.

*REST* (Representational State Transfer) is an architectural design style, not a specification. The term REST was incorporated into the API's name because the RESTful design style is perfect for research lab data access: self-descriptive, self-contained data representation in formats widely applicable to general scripting languages and the internet.

This REST reference section contains specifics and details on each resource, supported methods, and XML elements. For details on any resource click on the *REST resources* tree view at the left of this page. For details on the XML used by each resource method, use the *XML Namespaces* tree view.

A good place to start is in the REST General Concepts section. To help navigate the resources, the following diagram highlights the methods available and the major resource relationships.

Supported Versions

API changes are tracked with the combination of a version number and a revision number.

The version number indicates forwards and backwards compatibility, while the revision number within the version describes features added to the API that will not negatively affect current functionality. Only the version number is referenced as part of the request; the revision number simply tracks incremental enhancements to the API.

The following version is described in this section of the web site:

For details on previous versions, see the Previous REST Versions page.

Changes in Current Revision

• Added Role POST for custom role support via API.
• Improved support for External endpoint. Now supports external IDs on Researchers, Accounts, Samples, and Projects.
• Added support for downloading files via the Files endpoint.
• Added support for uploading files via the Files endpoint.

Requesting an API Version

The version number is a path parameter in each resource URI in the API. The desired API version is substituted into the following request URI:

/{version}/{resource}

The following example would request version 2 of the containers resource:

• /v2/containers

REST

This API supports a Representational State Transfer (REST) model for accessing a set of resources through a fixed set of operations. The following resources are accessible through the RESTful model:

• /{version}
• /{version}/{version}
• /{version}/artifactgroups
• /{version}/artifactgroups/{experimentid}
• /{version}/artifacts
• /{version}/artifacts/{limsid}
• /{version}/artifacts/batch/retrieve
• /{version}/artifacts/batch/update
• /{version}/configuration/protocols
• /{version}/configuration/protocols/{protocolid}
• /{version}/configuration/protocols/{protocolId}/steps/{stepId}
• /{version}/configuration/udfs
• /{version}/configuration/udfs/{udfid}
• /{version}/configuration/udts
• /{version}/configuration/udts/{udtid}
• /{version}/configuration/workflows
• /{version}/configuration/workflows/{workflowid}
• /{version}/configuration/workflows/{workflowid}/stages/{stageid}
• /{version}/containers
• /{version}/containers/{limsid}
• /{version}/containers/batch/create
• /{version}/containers/batch/retrieve
• /{version}/containers/batch/update
• /{version}/containertypes
• /{version}/containertypes/{containertypeid}
• /{version}/controltypes
• /{version}/controltypes/{controltypeid}
• /{version}/external/{externalid}
• /{version}/files
• /{version}/files/{limsid}
• /{version}/files/{limsid}/download
• /{version}/files/{limsid}/upload
• /{version}/files/batch/retrieve
• /{version}/files/batch/update
• /{version}/glsstorage
• /{version}/instruments
• /{version}/instruments/{instrumentid}
• /{version}/labs
• /{version}/labs/{labid}
• /{version}/permissions
• /{version}/permissions/{permissionId}
• /{version}/processes
• /{version}/processes/{limsid}
• /{version}/processtemplates
• /{version}/processtemplates/{limsid}
• /{version}/processtypes
• /{version}/processtypes/{processtypeid}
• /{version}/projects
• /{version}/projects/{limsid}
• /{version}/queues/{protocolStepId}
• /{version}/reagentkits
• /{version}/reagentkits/{reagentkitid}
• /{version}/reagentlots
• /{version}/reagentlots/{reagentlotid}
• /{version}/reagenttypes
• /{version}/reagenttypes/{reagenttypeid}
• /{version}/researchers
• /{version}/researchers/{researcherid}
• /{version}/roles
• /{version}/roles/{roleId}
• /{version}/route/artifacts
• /{version}/samples
• /{version}/samples/{limsid}
• /{version}/samples/batch/create
• /{version}/samples/batch/retrieve
• /{version}/samples/batch/update
• /{version}/steps
• /{version}/steps/{limsid}
• /{version}/steps/{limsid}/actions
• /{version}/steps/{limsid}/advance
• /{version}/steps/{limsid}/details
• /{version}/steps/{limsid}/placements
• /{version}/steps/{limsid}/pools
• /{version}/steps/{limsid}/programstatus
• /{version}/steps/{limsid}/reagentlots
• /{version}/steps/{limsid}/reagents
• /{version}/steps/{limsid}/setup
• /{version}/steps/{limsid}/trigger/{programid}

There is also a WADL document describing the REST API.

API Data Types

All endpoints act on a common set of data. The data can be represented in different data formats (i.e. MIME types), depending on the endpoint that consumes and/or produces the data. The data can described by XML Schema, which definitively describes the XML representation of the data, but is also useful for describing the other formats of the data, such as JSON.

This document will describe the data using terms based on XML Schema. Data can be grouped by namespace, with a schema document describing the elements and types of the namespace. Generally speaking, types define the structure of the data and elements are instances of a type. For example, elements are usually produced by (or consumed by) a REST endpoint, and the structure of each element is described by its type.

API Data Type Schemas

XML Data Elements

• namespace ri
  • index
  • links
• namespace art
  • artifact
  • artifacts
  • details
• namespace artgr
  • artifactgroup
  • artifactgroups
• namespace cnf
  • field
  • type
  • udfconfig-link
  • udfs
  • udtconfig-link
  • udts
• namespace con
  • container
  • containers
  • details
• namespace ctp
  • container-type
  • container-types
• namespace ctrltp
  • control-type
  • control-types
• namespace exc
  • exception
• namespace file
  • details
  • file
  • files
• namespace inst
  • instrument
  • instruments
• namespace ns1
  • instrument-type
  • instrument-types
• namespace lab
  • lab
  • labs
• namespace perm
  • permission
  • permissions
• namespace prc
  • process
  • processes
• namespace prx
  • process
• namespace ptm
  • process-template
  • process-templates
• namespace ptp
  • process-type
  • process-types
• namespace prj
  • project
  • projects
• namespace prop
  • properties
• namespace protcnf
  • protocol
  • protocols
• namespace que
  • queue
• namespace kit
  • reagent-kit
  • reagent-kits
• namespace lot
  • reagent-lot
  • reagent-lots
• namespace rtp
  • reagent-type
  • reagent-types
• namespace res
  • researcher
  • researchers
• namespace role
  • role
  • roles
• namespace rt
  • routing
• namespace smp
  • details
  • sample
  • samplecreation
  • samples
• namespace stg
  • stage
• namespace stp
  • actions
  • details
  • lots
  • placements
  • pools
  • program-status
  • reagents
  • setup
  • step
  • step-creation
• namespace protstepcnf
  • step
• namespace ver
  • version
  • versions
• namespace wkfcnf
  • workflow
  • workflows

XML Data Types

• namespace ri
  • address
  • container
  • externalid
  • index
  • link
  • links
  • location
  • page
• namespace art
  • artifact
  • artifactgroup
  • artifact-link
  • artifacts
  • control-type
  • details
  • parent-process
  • qc-flag
  • reagent-label
  • sample
  • status
  • workflow-stage
• namespace artgr
  • artifactgroup
  • artifactgroup-link
  • artifactgroups
  • artifacts
• namespace cnf
  • field
  • field-link
  • field-type
  • type
  • type-definition
  • udfconfig-link
  • udfs
  • udtconfig-link
  • udts
• namespace con
  • container
  • container-link
  • containers
  • container-type
  • details
  • placement
• namespace ctp
  • calibrant-well
  • container-type
  • container-type-link
  • container-types
  • dimension
  • unavailable-well
• namespace ctrltp
  • control-type
  • control-type-link
  • control-types
• namespace exc
  • exception
• namespace file
  • details
  • file
  • file-link
  • files
• namespace inst
  • instrument
  • instrument-link
  • instruments
• namespace ns1
  • instrument-type
  • instrument-type-link
  • instrument-type-process-type
  • instrument-types
• namespace lab
  • lab
  • lab-link
  • labs
• namespace perm
  • permission
  • permission-link
  • permissions
• namespace prc
  • artifact
  • input-output-map
  • instrument
  • output-generation-type
  • parameter
  • parent-process
  • process
  • processes
  • process-link
  • process-type
  • technician
• namespace prx
  • artifactbase
  • input
  • input-output-map
  • instrument
  • output
  • parameter
  • process
  • qc-flag
  • technician
• namespace ptm
  • instrument
  • parameter
  • process-template
  • process-template-link
  • process-templates
  • process-type
  • technician
• namespace ptp
  • invocation-type
  • output-generation-type
  • parameter
  • process-input
  • process-output
  • process-type
  • process-type-attribute
  • process-type-link
  • process-types
  • type-definition
  • variability-type
• namespace prj
  • project
  • project-link
  • projects
  • researcher
• namespace prop
  • properties
  • property-link
• namespace protcnf
  • protocol
  • protocol-link
  • protocol-property
  • protocols
• namespace que
  • artifact-link
  • queue
• namespace kit
  • reagent-kit
  • reagent-kit-link
  • reagent-kits
• namespace lot
  • reagent-kit-link
  • reagent-lot
  • reagent-lot-link
  • reagent-lots
  • researcher
• namespace rtp
  • attribute
  • reagent-type
  • reagent-type-link
  • reagent-types
  • special-type
• namespace res
  • credentials
  • lab
  • researcher
  • researcher-link
  • researchers
  • role
• namespace role
  • permission-link
  • researcher-link
  • role
  • role-link
  • roles
• namespace rt
  • artifact
  • extArtifactAssignments
  • routing
• namespace smp
  • artifact
  • biosource
  • controlType
  • details
  • project
  • sample
  • samplebase
  • samplecreation
  • sample-link
  • samples
  • submitter
• namespace stg
  • protocol
  • stage
  • step
  • workflow
• namespace stp
  • actions
  • actions-link
  • action-type
  • artifact
  • available-program
  • container
  • creation-input
  • details
  • details-link
  • escalated-artifact
  • escalation
  • escalation-request
  • escalation-review
  • file
  • input
  • input-output-map
  • instrument
  • next-action
  • output
  • output-generation-type
  • output-placement
  • placements
  • placements-link
  • pooled-inputs
  • pools
  • pools-link
  • program-status
  • program-status-link
  • reagent-label
  • reagent-lot-link
  • reagent-lots-link
  • reagents
  • reagents-link
  • reagents-lots
  • setup
  • setup-link
  • status
  • step
  • step-configuration
  • step-creation
  • user
• namespace protstepcnf
  • control-type-link
  • epp-trigger
  • field
  • file
  • next-step
  • process-type
  • queuefield
  • reagent-kit-link
  • step
  • step-property
  • step-setup
  • trigger-point
  • trigger-status
  • trigger-type
• namespace udf
  • field
  • type
• namespace ver
  • version
  • versions
• namespace wkfcnf
  • protocol-link
  • stage-link
  • status
  • workflow
  • workflow-link
  • workflows