---
title: "Add outlet bills"
method: POST
path: "/api/connector/v1/outletBills/add"
tags: ["Outlet bills"]
---

# Add outlet bills

`POST /api/connector/v1/outletBills/add`

Adds new outlet bills with their items.

## Request body

- AddOutletBillsParameters
  - `ClientToken` string, required — Token identifying the client application.
  - `AccessToken` string, required — Access token of the client application.
  - `Client` string, required — Name and version of the client application.
  - `Bills` OutletBillParameters[], required — The new outlet bills.
    - `OutletId` string, uuid, required — Unique identifier of the `Outlet` where the bill was issued.
    - `Number` string, required — Number of the bill.
    - `ClosedUtc` string, required — Date and time of the bill closure in UTC timezone in ISO 8601 format.
    - `Items` OutletItemParameters[], required — The items on the bill.
      - `Name` string, required — Name of the item.
      - `UnitCount` integer, required — Unit count of the item.
      - `UnitAmount` AmountParameters, required — Price of the product that overrides the price defined in Mews.
        - `Currency` string, currency, required
        - `TaxCodes` string[], required
        - `NetValue` number, double, nullable
        - `GrossValue` number, double, nullable
      - `ConsumedUtc` string, date-time, required — Date and time of the item consumption in UTC timezone in ISO 8601 format.
      - `Type` 'Revenue' | 'NonRevenue' | 'Payment', required — Type of the outlet item.
      - `ExternalIdentifier` string, nullable — An identifier of this item from another system.
      - `Notes` string, nullable — Additional notes of the item.
      - `AccountingCategoryId` string, uuid, nullable — Unique identifier of an `AccountingCategory` to be assigned to the item.
    - `AccountId` string, uuid, nullable — Unique identifier of the `Account` to be assigned to the bill.
    - `Notes` string, nullable — Additional notes on the bill.

## Response `200`

OK

- AddOutletBillsResult
  - `OutletBillIds` string[], required — Array of unique identifiers of the added Outlet bills.

## Other responses

- `204` — Server has successfully fulfilled the request and there is no additional information to send back.
- `400` — Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
- `401` — Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
- `403` — Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
- `408` — Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
- `429` — Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
- `500` — Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).

---

[API](https://skmtc.net/mews/apis/connector-api.md) · [All operations](https://skmtc.net/mews/apis/connector-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mews/connector-api/revisions/4bf95cbc375f/schema)