---
title: "Upload Supporting Document"
method: POST
path: "/providers/{id}/supporting-documents"
tags: ["providers"]
---

# Upload Supporting Document

`POST /providers/{id}/supporting-documents`

Uploads a supporting document for a provider by ID. This endpoint accepts a multipart/form-data request with a file and metadata.

    - The uploaded document is associated with the provider and saved in the system.
    - Only valid files and supported document metadata will be processed.
    - Returns a confirmation once the document is uploaded successfully.

    Authorization:
    - Requires an Bearer access token.

    Possible Errors:
    - `400 Bad Request`: If the file or metadata is invalid.
    - `404 Not Found`: If the provider with the given ID does not exist.

## Path parameters

- `id` string, required

## Headers

- `organization-id` string

## Response `201`

The supporting document was successfully uploaded.

## Other responses

- `400` — Bad request. Invalid input or file.
- `401` — Unauthorized if authorization token is not provided or invalid.
- `403` — Forbidden if user access is not right.
- `404` — Provider not found.

---

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