---
title: "Create fee"
method: POST
path: "/fees"
tags: ["Fees"]
---

# Create fee

`POST /fees`

Create a **Fee** to be associated with an **Item**. **Fees** will add or subtract from the **Item** amount based on the **User**, payment type or Disbursement account type. **Fees** can be `Fixed` or `Percentage` based. **Fees** can be capped, have a maximum amount and/or a minimum amount.

## Request body

- FeeRequestBody
  - `name` string, required — Name
  - `fee_type_id` '1' | '2' | '3' | '4', required — Fee type: 1. Fixed 2. Percentage 3. Percentage with Cap 4. Percentage with Min
  - `amount` integer, required — Amount in cents; if the fee type is percentage, then this shows the percentage in hundredths (For example, an amount of 5 refers to 0.05% in fees.)
  - `cap` string — Cap the Fee
  - `min` integer — Minimum Fee
  - `max` integer — Maximum Fee
  - `to` 'buyer' | 'seller' | 'cc' | 'int_wire' — Who pays the Fee. Allowed values are (buyer or seller). If this field has a value of buyer, then the buyer will have to pay the fee on top of the actual payment (example for an item of 100 and a fee of 2, then the buyer would have to pay 102) If this field has a value of seller, then the seller will end up receiving the amount - the fee (example for an item of 100 and a fee of 2, then the seller would end up receiving 98)

## Response `201`

OK

- SingleFee
  - `fees` Fee
    - `id` string
    - `created_at` string, date-time
    - `updated_at` string, date-time
    - `name` string
    - `fee_type_id` string
    - `amount` string
    - `cap` string
    - `min` string
    - `max` string
    - `to` string
    - `calculated_fee` integer — This field is only shown in case an item amount is passed
    - `links` object
      - `self` string

---

[API](https://skmtc.net/hellozai/apis/assembly-api.md) · [All operations](https://skmtc.net/hellozai/apis/assembly-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hellozai/assembly-api/versions/60b528b2e015/schema)