---
title: "Application of a voucher"
method: POST
path: "/vouchers/{voucher_id}/actions/apply-voucher"
tags: ["Vouchers"]
---

# Application of a voucher

`POST /vouchers/{voucher_id}/actions/apply-voucher`

Sets a voucher as applied.

## Path parameters

- `voucher_id` string, required

## Headers

- `Accept-Language` string

## Request body

- object
  - `store_id` string — The unique ID of the store where voucher was applied.
  - `date_applied` string, required — Date (ISO 8601) of voucher application. *(YYYY-MM-DD HH:MM:SS)*

## Response `204`

No Content

## Other responses

- `400` — Bad input parameter. The response body's `error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.
- `401` — The client has invalid credentials or auth token.
- `403` — The client does not exist or the client tried to access an unauthorized property or resource.
- `404` — The resource was not found.
- `405` — The resource does not support the specified HTTP method.
- `429` — Too many requests - more than the resource limit.
- `500` — Server is not working as expected.
- `503` — Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

---

[API](https://skmtc.net/crmcarecloud/apis/rest-api-reference.md) · [All operations](https://skmtc.net/crmcarecloud/apis/rest-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crmcarecloud/rest-api-reference/versions/329c06dbf8d9/schema)