---
title: "Create a fund"
method: POST
path: "/fund"
tags: ["Funds"]
---

# Create a fund

`POST /fund`

Creates a fund.

## Headers

- `Accept` 'application/vnd.Creative Force.v2.3+json' | 'application/vnd.Creative Force.v2.3+xml', required
- `x-api-language` string[]

## Request body

- object
  - `budget` number, required — Total budget of the fund, in the fund's currency.
  - `currency` string, required — ISO 4217 currency code of the fund's amounts.
  - `translated` object, required — Translated fund field values keyed by field name.
    - `description` object — Values keyed by existing and enabled language code.
    - `name` object — Values keyed by existing and enabled language code.

## Response `201`

Fund created.

- Fund — Fund holding a monetary budget, tracking the amounts allocated and still available. Carries the translated name and description, the currency, and the budget, allocated, and available amounts.
  - `allocated` number — Amount allocated from the budget, in the fund's currency.
  - `available` number — Amount still available to allocate, in the fund's currency. Equal to the budget minus the allocated amount.
  - `budget` number — Total budget of the fund, in the fund's currency.
  - `created` string, date-time — Date and time when the fund was created.
  - `currency` string — ISO 4217 currency code of the fund's amounts.
  - `description` object — Description of the fund. Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string.
  - `name` object — Name of the fund. Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string.
  - `slug` string — URL-safe identifier of the fund.
  - `updated` string, date-time — Date and time when the fund was last updated.

## Other responses

- `400` — Request was rejected before the endpoint could process it. Common causes: invalid `Accept` header, unsupported `x-api-language` code, empty request body on `POST` / `PUT`, invalid JSON in the request body, or an invalid slug format in a path parameter.
- `401` — Missing `x-api-key` header.
- `403` — Authenticated request denied. Common causes: invalid or unknown API key, suspended account, or `api` feature not enabled for the account.
- `422` — Request was syntactically valid but could not be processed. Returned in two scenarios: - **Field-level validation failure** — one or more request fields violated the endpoint's validation rules. The body includes an `errors` map keyed by field name with one or more validation messages each. - **Resource-state precondition failure** — the request fields were all valid, but the target resource was in a state that does not permit the requested operation. The body carries only `message` and `status_code`; no `errors` map.
- `429` — Rate limit of 60 requests per minute exceeded.
- `503` — Service is temporarily unavailable due to regional maintenance.

## Changes

- **2026-07-07** (v2) `9b9103538ceb` — 2 info
  - api tag `Funds` added
  - api tag `Fund` removed
- **2026-07-01** (v2) `473e2bc2cce3` — 1 info
  - added the media type `application/xml` for the response with the status `201`
- **2026-07-01** (v2) `0e03b185dcba` — 1 info
  - endpoint added
- **2026-07-01** (v2) `e96a96d4507e` — 1 breaking
  - api path removed without deprecation
- **2026-07-01** (v2) `4222031b277d` — 1 info
  - endpoint added

[Full history](https://skmtc.dev/tectonic/apis/award-force-api/changes/fund/post.md)

---

[API](https://skmtc.dev/tectonic/apis/award-force-api.md) · [All operations](https://skmtc.dev/tectonic/apis/award-force-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/tectonic/award-force-api/revisions/9b9103538ceb/schema)