Make computer files available to a team
POST
/v1/environments/{environmentId}/files/share-with-teamShare selected files from one computer workspace with a workspace team. Source files remain in place.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| environmentId | path | string | Yes | Environment ID |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| teamId | string | Yes | — |
| paths | string[] | Yes | — |
| accessLevel | use | edit | manage | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Files made available to teamapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| success | boolean | No | Whether the request succeeded. |
| environmentId | string | No | Computer ID. |
| teamId | string | No | — |
| files | object[] | No | — |
| files[].shareId | string | No | — |
| files[].path | string | No | Workspace-relative file path. |
| files[].size | integer | No | — |
| files[].accessLevel | string | No | — |
Make computer files available to a team
Loading...
Response 200
Loading...