---
title: "Add voucher codes"
method: POST
path: "/api/connector/v1/voucherCodes/add"
tags: ["Voucher codes"]
---

# Add voucher codes

`POST /api/connector/v1/voucherCodes/add`

Adds voucher codes to the specified [Vouchers](https://mews-systems.gitbook.io/connector-api/operations/vouchers/#voucher). Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).

## Request body

- MultipleVoucherCodeAddParameters
  - `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.
  - `EnterpriseId` string, uuid, nullable — Unique identifier of the enterprise. Required when using [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property), ignored otherwise.
  - `VoucherCodeParameters` VoucherCodeAddParameters[], required — Voucher codes to be added.
    - `VoucherId` string, uuid, required — Unique identifier of [Voucher](#voucher) the code belongs to.
    - `Value` string, required — Value of voucher code used by customers.
    - `ValidityStartUtc` string, date-time, nullable — If specified, marks the beginning of interval in which the code can be used.
    - `ValidityEndUtc` string, date-time, nullable — If specified, marks the end of interval in which the code can be used.

## Response `200`

OK

- VoucherCodeResult
  - `VoucherCodes` VoucherCode[], required — Information about voucher codes used by customers.
    - `Id` string, uuid, required — Unique identifier of the voucher code.
    - `VoucherId` string, uuid, required — Unique identifier of `Voucher` the code belongs to.
    - `Value` string, nullable — Value of voucher code used by customers.
    - `ValidityStartUtc` string, nullable — If specified, marks the beginning of interval in which the code can be used.
    - `ValidityEndUtc` string, nullable — If specified, marks the end of interval in which the code can be used.
    - `CreatedUtc` string, nullable — Creation date and time of the voucher in UTC timezone in ISO 8601 format.
    - `UpdatedUtc` string, nullable — Last update date and time of the voucher in UTC timezone in ISO 8601 format.
    - `ActivityState` 'Deleted' | 'Active', required — Deleted Active
    - `IsActive` boolean, required — Whether the voucher code is still active.
  - `Cursor` string, uuid, nullable — Unique identifier of the item one newer in time order than the items to be returned. If Cursor is not specified, i.e. null, then the latest or most recent items will be returned.

## 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/f37f136ed35a/schema)