---
title: "Upload a supporting document to a facility workflow"
method: POST
path: "/facility-credentialing-workflows/{workflowId}/supporting-documents"
tags: ["FacilityCredentialingWorkflow"]
---

# Upload a supporting document to a facility workflow

`POST /facility-credentialing-workflows/{workflowId}/supporting-documents`

Uploads a new file as a supporting document and appends it to the facility credentialing workflow's supporting documents list. **When to use:** Use to add a single supporting document without affecting existing documents. To replace the entire supporting documents list, use `PUT /facility-credentialing-workflows/{workflowId}/supporting-documents`. For attachments scoped to a specific section row rather than the whole workflow, use `POST /facility-credentialing-workflows/{workflowId}/attachments`. **Request:** Multipart form data. Fields: `file` (binary, required), `fileType` (required), `state` (optional), `expirationDate` (optional). **Side effects:** File is stored in Cloud Storage. **Returns:** `201 Created` with the created supporting document record.

## Path parameters

- `workflowId` string, required

## Headers

- `tenant-id` string, required

## Response `201`

Supporting document created successfully

- object

## Other responses

- `400` — Bad request - Invalid input, e.g., file is missing
- `401` — Unauthorized - Authentication required
- `403` — Forbidden - Insufficient permissions
- `404` — Facility credentialing workflow not found
- `500` — Internal server error

---

[API](https://skmtc.net/certifyos/apis/certify-api-layer.md) · [All operations](https://skmtc.net/certifyos/apis/certify-api-layer/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/certifyos/certify-api-layer/revisions/563848e0ecc0/schema)
