---
title: "Create a task upload link"
method: POST
path: "/companies/{company}/tasks/{task}/upload-links"
tags: ["Tasks"]
---

# Create a task upload link

`POST /companies/{company}/tasks/{task}/upload-links`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/tasks/{task}/upload-links`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Create a single-use link to upload files to a task from a phone or by someone without an account. The link expires after 30 minutes and works once; the response includes the `url` (shown only now). `target` and `note` behave as in the attachment upload.

## Path parameters

- `company` string, uuid, required
- `task` string, uuid, required

## Headers

- `Idempotency-Key` string
- `Factuarea-Version` string, date

## Request body

- CreateTaskUploadLinkV1Request
  - `target` 'description' | 'comment': Where the uploads received through the link are delivered: `comment` (default) or `description`.
  - `note` string, nullable: Note for whoever uploads the files.

## Response `201`

- object
  - `data` TaskUploadLink, required: A single-use link to upload files to a task without an account. It expires after 30 minutes.
    - `id` string, uuid, required: UUID v7 of the upload link.
    - `object` 'task_upload_link', required: Stripe-like discriminator. Always `task_upload_link` for this resource.
    - `task_id` string, uuid, required: UUID of the task.
    - `url` string, uri, required: Public upload page. It carries the secret token and is shown only in this response.
    - `target` 'description' | 'comment', required: Where the uploaded files are attached.
    - `note` string, nullable, required: Text of the comment created with the files, or `null`.
    - `expires_at` string, date-time, required: When the link stops working.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `409`: The request conflicts with data that already exists or with a request running at the same time. `resource_conflict`: another request was reserving identifiers for the same kind of record at that moment and this one could not complete its reservation. Nothing was written; send the request again after a few seconds.
- `422`: Validation failed. The `error.param` field identifies which input is invalid.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)