---
title: "Add Share Asset"
method: POST
path: "/asset/{asset_id}/share/add"
---

# Add Share Asset

`POST /asset/{asset_id}/share/add`

## Request

- Base URL: `https://api.tellers.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.tellers.ai/asset/{asset_id}/share/add`
- Auth: none declared

Add one share for the asset (SSE): grant ``right`` (READ by default) to either a group
(group_id) or a user (email).
If the asset is a folder, applies to the folder and all underlying assets. Caller must be able
to share it (ADMIN, or a share with can_share); only ADMIN can set can_share.

## Path parameters

- `asset_id` string, uuid, required

## Headers

- `x-api-key` string, nullable
- `authorization` string, nullable

## Request body

- ShareAddRequest: Add one share: provide exactly one of group_id or email.
  - `group_id` string, uuid, nullable
  - `email` string, nullable
  - `can_share` boolean: Let the grantee share the asset onward too. Only an admin of the asset can set it.
  - `right` string, nullable: VIEW, READ, WRITE or ADMIN; null means READ. VIEW sees the file and everything about it except its comments. Below ADMIN, a sharer hands out at most their own right. An existing share keeps its right: change it with share/update_right.

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/tellers/apis/tellers-api.md) - [All operations](https://skmtc.dev/tellers/apis/tellers-api/llms.txt) - [OpenAPI document](https://skmtc.dev/tellers/apis/tellers-api/revisions/fdaa0fa44a26?raw)