# Create/update measurements for storages in bulk

Submits up to 10000 measurements in one request, each naming its own location and storage. Any invalid record rejects the whole batch and stores nothing. Accepted records are applied to the storages by a daily process, so they are not immediately queryable — which is why a successful submission is 202 rather than 200.

Endpoint: POST /fuel/measurements/bulk
Version: 1.0.0
Security: M2X_auth_application

## Request fields (application/json):

  - `id` (string, required)
    Your identifier for the measurement
    Example: "D001"

  - `locationId` (string, required)
    The M2X id of the location holding the storage
    Example: "L001"

  - `storageId` (string, required)
    The M2X id of the storage the measurement was taken from
    Example: "S001"

  - `type` (string, required)
    Enum: "STANDARD_DIP", "PRE_DIP", "POST_DIP"

  - `timestamp` (string, required)
    RFC3339 date time of the measurement

  - `quantityLitres` (number, required)

## Response 202 fields (application/json):

  - `success` (boolean)

  - `accepted` (integer)
    Number of measurements accepted for deferred application

  - `results` (array)

  - `results.index` (integer)
    Position of the measurement in the submitted batch

  - `results.id` (string)
    Identifier the measurement is stored under

  - `results.status` (string)
    accepted where the measurement was accepted for deferred application, valid where the measurement was not itself at fault but the batch was rejected over another measurement, error where the measurement itself was at fault
    Enum: "accepted", "valid", "error"

  - `results.code` (string)
    The code for the issue

  - `results.message` (string)
    The issue description