# Upload list of inventory snapshots

**POST** `https://api.zoined.com/inventorySnapshots?dryRun=false&separator=%3B&encoding=utf-8`

Endpoint: POST /inventorySnapshots
Security: bearerAuth

## Security:

  - `bearerAuth` (unknown)
    http bearer token

## Query parameters:

  - `dryRun` (boolean, required)
    Only validate the request without storing the data

  - `separator` (string, required)
    Column separator used when loading CSV data

  - `encoding` (string, required)
    Character encoding used in the CSV data (default is utf-8)

## Request fields (application/json):

  - `organisation_id` (string, required)
    Organisation / Store ID
    Example: 540

  - `snapshot_date` (string, required)
    Date of snapshot (yyyy-mm-dd)
    Example: 2016-01-01

  - `snapshot_time` (string)
    Time of snapshot (HH:mm:ss). Needed if inter-day inventory saldos are tracked.
    Example: 15:00:00

  - `product_id` (string, required)
    Product ID
    Example: My product ID

  - `supplier_id` (string)
    Supplier ID
    Example: 221

  - `quantity` (number, required)
    On hand quantity in inventory
    Example: 100

  - `available_quantity` (number)
    Available quantity in inventory (after pending/reserved orders)
    Example: 90

  - `reorder_point` (number)
    Quantity threshold for this item to order more into inventory
    Example: 5

  - `max_reorder_quantity` (number)
    Max quantity threshold for this item after reordering
    Example: 10

  - `unit_purchase_price` (number)
    Unit purchase price
    Example: 12.4

  - `unit_purchase_price_wo_vat` (number)
    Unit purchase price without tax
    Example: 10

  - `unit_sales_price` (number)
    Unit sales price
    Example: 22.4

  - `unit_sales_price_wo_vat` (number)
    Unit sales price without tax
    Example: 20

  - `currency` (string)
    Currency for the purchase price as ISO 4217 currency code. Required if multiple currencies are used.
    Example: EUR

  - `source_system` (string)
    Identifier of the source system this data is from. Needed when mapping between source system identifiers and master identifiers are used.
    Example: ABCDEF

## Response 200:

  - `200` (unknown)
    Request has been processed successfully.
**Headers**
- `Content-Type: application/json`

## Response 200 fields (application/json):

  - `status` (string, required)
    Status of the operation OK / Not OK
    Example: OK

  - `msg` (string, required)
    Message describing result of operation
    Example: 1 entity added

## Response 400:

  - `400` (unknown)
    Invalid, malformed or missing JSON-data in request
**Headers**
- `Content-Type: application/json`

## Response 400 fields (application/json):

  - `status` (string, required)
    Status of the operation OK / Not OK
    Example: Not OK

  - `msg` (string, required)
    Message describing result of operation
    Example: Reason for error

## Response 401:

  - `401` (unknown)
    Missing or invalid authorization token in header
**Headers**
- `Content-Type: application/json`

## Response 401 fields (application/json):

  - `status` (string, required)
    Status of the operation OK / Not OK
    Example: Not OK

  - `msg` (string, required)
    Message describing result of operation
    Example: Unauthorized

## Response 500:

  - `500` (unknown)
    Internal error or exception
**Headers**
- `Content-Type: application/json`

## Response 500 fields (application/json):

  - `status` (string, required)
    Status of the operation OK / Not OK
    Example: Not OK

  - `msg` (string, required)
    Message describing result of operation
    Example: Reason for error

## Response 200 examples:

  - `response` (unknown)

## Response 400 examples:

  - `response` (unknown)

## Response 401 examples:

  - `response` (unknown)

## Response 500 examples:

  - `response` (unknown)