> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcliq.io/llms.txt > Use this file to discover all available pages before exploring further. # Upload team files > Multipart: a JSON `payload` part (`team_id`, `version_id?`) and the files as attachments, each filename being its path in the team (PLAN-team-bundle §2.6). Requires a signed-in user token (`Authorization: Bearer cliq_tok_…`). Results are limited to what that user can see. ## OpenAPI ````yaml /openapi/hub-by-tag/hub-teams.yaml post /v1/teams/files/upload openapi: 3.0.3 info: title: 'CliqHub API: Teams' version: 1.0.0 description: >- The CliqHub team registry. A team is published under a scope (`@acme/code-review`) as numbered versions. Create a draft, change it (each change can mint the next version), publish it to make it installable, then install it on daemons. List teams with a `realm_id` to see a realm's roster and where each team is installed, or with a `daemon_id` to see what one daemon has. Build a team with AI drafts a team from a description. Changing a team (update, publish, withdraw a version, unpublish, delete) needs its author, or the publish permission in the organization that owns its scope. servers: - url: https://{host} variables: host: default: cliqhub.io description: CliqHub host security: [] tags: - name: Teams description: >- The CliqHub team registry. A team is published under a scope (`@acme/code-review`) as numbered versions. Create a draft, change it (each change can mint the next version), publish it to make it installable, then install it on daemons. List teams with a `realm_id` to see a realm's roster and where each team is installed, or with a `daemon_id` to see what one daemon has. Build a team with AI drafts a team from a description. Changing a team (update, publish, withdraw a version, unpublish, delete) needs its author, or the publish permission in the organization that owns its scope. paths: /v1/teams/files/upload: post: tags: - Teams summary: Upload team files description: >- Multipart: a JSON `payload` part (`team_id`, `version_id?`) and the files as attachments, each filename being its path in the team (PLAN-team-bundle §2.6). Requires a signed-in user token (`Authorization: Bearer cliq_tok_…`). Results are limited to what that user can see. operationId: POST_v1_teams_files_upload requestBody: required: true content: application/json: schema: type: object properties: team_id: type: string format: uuid description: The team the files belong to version_id: type: string format: uuid description: The draft to add them to; omit to start a new draft based_on_version_id: type: string format: uuid description: >- A new draft's: the published version of this team it starts from (shown as 'Draft · based on 1.2.0'); ignored with version_id required: - team_id responses: '200': description: Success content: application/json: schema: allOf: - $ref: '#/components/schemas/HubOk' - type: object properties: data: type: object additionalProperties: true description: Present on success (`data`) nullable: true '401': description: >- `unauthorized`: No `Authorization` header, or the token is malformed, expired or revoked. content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: unauthorized: summary: unauthorized value: ok: false error: code: unauthorized message: Authentication required '403': description: '`forbidden`: A daemon token was used; this route needs a user token.' content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: forbidden: summary: forbidden value: ok: false error: code: forbidden message: You do not have access to do this '422': description: >- `invalid_params`: The body fails the request schema: a required field is missing or a value has the wrong type or format. The message lists every issue as `field: problem`. content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: invalid_params: summary: invalid_params value: ok: false error: 'team_id: Required' code: invalid_params '500': description: >- `internal_error`: An unexpected server fault. Retry later; if it persists, report it with the time of the request. content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: internal_error: summary: internal_error value: ok: false error: Internal server error code: internal_error security: - BearerAuth: [] components: schemas: HubOk: type: object required: - ok properties: ok: type: boolean description: Always true on success description: Success envelope. Additional data fields vary by route. HubErr: type: object required: - ok - error description: >- Every failure. Route-policy denials (401/403/404, and 400 when neither realm_id nor org_id was sent) answer `error` as `{ code, message }`; errors raised by the endpoint answer `error` as the message with the code beside it in `code`. Every error has a code. See [Errors](/hub-api/errors). properties: ok: type: boolean description: Always false on error error: description: The message, or `{ code, message }` for an access denial. oneOf: - type: string - type: object required: - code - message properties: code: type: string message: type: string code: type: string description: Stable error code of an endpoint error. details: type: object additionalProperties: true description: Structured detail, when there is some. securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: cliq_tok_* | cliq_dt_* description: >- User PAT (`cliq_tok_…`, including session-scoped) or realm token (`cliq_dt_…`). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.