v1
latestOpenAPI 3.1.02026-07-267418115.3 KBGET metadata
Path parameters
Response
OK
Arbitrary metadata is supported as part of a custom object. custom has two constraints: (1) it must have a depth of one (i.e., no nested records); and (2) only strings, numbers, boolean, and null values are supported as values. Example: {"lab_tech": "Linus Pauling", "amplicon_scheme": "V3-V4"}
Timestamp for when the sample was collected.
Timestamp for when the sample was sequenced.
An arbitrary external sample ID, e.g., an ID in a LIMS. Up to 60 characters.
Allowed types of SampleMetadata.library_type. Also used to populate form dropdown in the front-end
The latitude (-90.0-90.0) of the sample location. By convention, we recommend using this for the location in which the physical specimen was collected.
The longitude (-180.0-180.0) of the sample location.
Allowed values of SampleMetadata.platform.
Allowed values for SampleMetadata.sample_type. Used to populate values in the front-end dropdown
Whether the sample has been starred by the user within the One Codex web application.
Timestamp for when the object was last updated on the One Codex platform, encoded as a RFC 3339 timestamp.
Example response
{
"$uri": "/api/v1/metadata/0d77065796f8d173",
"external_sample_id": "LIMS-2024-00123",
"sample": {
"__DOLLAR_REF__": "/api/v1/samples/a1b2c3d4e5f67890"
}
}