---
title: "Create a document"
method: POST
path: "/document"
tags: ["Documents"]
---

# Create a document

`POST /document`

Creates a document.

## Headers

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

## Request body

- object
  - `translated` object, required
    - `name` object, required — Name of the document. 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.
    - `description` object — Description of the document. 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.
  - `template` string, required — Slug of the document template to generate the document from.
  - `fileType` 'PDF' | 'Word' | 'accessible-pdf', required — File format to generate the document in. Use `accessible-pdf` to generate a tagged, accessible PDF.
  - `shared` boolean, required — Specifies whether the generated document is shared with the entrant.
  - `resource` 'user' | 'entry' | 'allocation' | 'grant-report', required — Type of resource to attach the generated documents to.
  - `selected` string[], required — Slugs of the resources, of the type given by `resource`, to attach the generated documents to.
  - `notification` string, nullable — Slug of the notification to send when the document is created. Omit or set to `null` to send no notification.

## Response `202`

Document creation accepted.

## 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-08** (v2) `72c39d7099a2` — 1 breaking
  - the request property `notification` became not nullable
- **2026-07-07** (v2) `9b9103538ceb` — 2 info
  - api tag `Documents` added
  - api tag `Document` removed
- **2026-07-01** (v2) `e96a96d4507e` — 6 info
  - added the media type `application/xml` for the response with the status `400`
  - added the media type `application/xml` for the response with the status `401`
  - added the media type `application/xml` for the response with the status `403`
  - added the media type `application/xml` for the response with the status `422`
  - …2 more
- **2026-06-30** (v2) `1d2a0b158b9c` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/tectonic/apis/award-force-api/changes/document/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/e2511e46f9f2/schema)