Create samples
Records between 1 and 100 samples against animals on the study. The request is validated as a whole; if any item is invalid, none are created.
Authentication
OAuth authentication of the form <token>.
Path parameters
Headers
Request
Whether the sample has been collected. Only collected and planned are accepted; cancelled is rejected.
The sample type, an active entry in your team’s samples glossary. Required unless sample_definition_id is supplied, and rejected with it.
The sample definition to create the sample from. Required when status is planned.
When the sample was collected, as a full ISO-8601 UTC date-time: either an explicit UTC instant (offset Z or +00:00) or an offset-less date-time taken as UTC. Date-only values and non-UTC offsets are rejected. Required when status is collected, rejected when it is planned, and may not be before the animal’s date of birth.
When the sample is due relative to the study schedule, as an ISO-8601 duration such as P1D or PT4H, optionally negative. Without a sample definition its magnitude must be zero or between 1 minute and 365 days.
The measured attributes of the sample. Each key must be one of the sample type’s configured details and appear once, value must be a non-negative number, and unit must be one configured for the key.
Response headers
The number of requests still available in the current rate limit window. When several limits apply, this reflects the per-API-key limit, so a request can be rejected while this value is above zero.