---
title: "Get all taxations"
method: POST
path: "/api/connector/v1/taxations/getAll"
tags: ["Taxations"]
---

# Get all taxations

`POST /api/connector/v1/taxations/getAll`

Returns all taxations supported in tax environments.

## Request body

- Parameters
  - `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.

## Response `200`

OK

- TaxationResult
  - `Taxations` Taxation[], required — The supported taxations.
    - `Code` string, required — Code of the taxation.
    - `Name` string, required — Name of the taxation.
    - `LocalName` string, required — Local name of the taxation.
  - `TaxRates` TaxRate[], required — The supported tax rates.
    - `Code` string, required — Code of the tax rate. To be used when posting revenue items which should be accompanied by the tax rate(s) applicable to the nature of the item and the tax environment.
    - `TaxationCode` string, required — Code of the `Taxation` the rate is part of.
    - `Value` number, double — Tax rate, e.g. `0.21` in case of 21% tax rate.
    - `ValidityInvervalsUtc` DateTimeIntervalUtc[], nullable — Validity intervals in UTC.
      - `StartUtc` string, nullable
      - `EndUtc` string, nullable
    - `Strategy` object, required — Tax strategy type, e.g. relative, flat or dependent.
      - `Discriminator` 'Relative' | 'Flat' | 'Dependent'
      - `Value` union
        - RelativeTaxRateStrategy
          - `Value` number, double, required — Tax rate, e.g. `0.21` in case of 21% tax rate.
        - FlatTaxRateStrategy
          - `CurrencyCode` string, required — Code of `Currency`.
          - `Value` number, double, required — Absolute value of tax.
        - DependentTaxRateStrategy
          - `Value` number, double, required — Tax rate, e.g. `0.1` in case of 10% tax rate.
          - `BaseTaxationCodes` string[], required — Codes of the taxations that are included in the base of calculation.

## 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/versions/81933a8ff730/schema)
