> ## Documentation Index > Fetch the complete documentation index at: https://docs.kodelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Upload base64 attachments > Uploads up to 10 base64-encoded files to a work order. Use it when your integration already holds file content as base64. ## OpenAPI ````yaml /openapi/kode-api.yaml post /api/v1/buildings/{buildingId}/assetops/work-orders/{workOrderId}/attachments/base64 openapi: 3.1.0 info: title: KODE API version: 1.0.0 summary: Programmatic access to KODE OS resources and operations. description: > Use the KODE API to work with buildings, data sources, connectors, devices, points, virtual devices, timeseries data, schedules, the ontology, templating, mass writes, spaces, space assignments, tenants, meters, users, actions, and AssetOps work orders. license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.kodelabs.com/kodeos description: KODE API security: - bearerAuth: [] tags: - name: Authentication description: OAuth 2.0 discovery, token, and revocation endpoints. - name: Buildings description: Buildings and their areas. - name: Data sources description: Data sources connected to a building. - name: Devices description: Devices and their points. - name: Points description: Point queries and point writes. - name: Timeseries description: Current and historical point values. - name: Actions description: Actions exposed by building data sources. - name: Work orders description: AssetOps work orders, lookups, comments, and attachments. - name: Connectors description: KODE API connectors and the devices and points ingested through them. - name: Schedules description: Schedules discovered on building data sources. - name: Templating description: Apply ontology templates to groups of points. - name: Virtual devices description: Virtual devices that group points from other devices. - name: Ontology description: Canonical types, fields, units, and connections of the KODE ontology. - name: Users description: Users of the organization and their app access. - name: Mass write description: Write values to many points across buildings, and follow each run. - name: Spaces description: Levels and space units of a building, and the meters located in them. - name: Space assignments description: Assign tenants to leasable spaces of a building for a period. - name: Tenants description: Tenants of a building, the people or companies that lease its spaces. - name: Meters description: >- Meters of a building, their space assignments, parent and child links, and readings. paths: /api/v1/buildings/{buildingId}/assetops/work-orders/{workOrderId}/attachments/base64: post: tags: - Work orders summary: Upload base64 attachments description: >- Uploads up to 10 base64-encoded files to a work order. Use it when your integration already holds file content as base64. operationId: uploadBase64WorkOrderAttachments parameters: - $ref: '#/components/parameters/BuildingId' - $ref: '#/components/parameters/WorkOrderId' requestBody: required: true content: application/json: schema: type: object required: - attachments properties: attachments: type: array maxItems: 10 x-mint: post: - max 10 items: $ref: '#/components/schemas/Base64Attachment' responses: '200': $ref: '#/components/responses/AttachmentList' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/TooManyRequests' components: parameters: BuildingId: name: buildingId in: path required: true description: Building identifier from List buildings. schema: type: string example: 67c960faffaa42223163099e WorkOrderId: name: workOrderId in: path required: true description: Work order identifier. schema: type: string example: 6702c4e1b8a3f21d9c0e4a17 schemas: Base64Attachment: type: object required: - name - contentType - content properties: name: type: string example: fan-belt.jpg contentType: type: string description: MIME type of the file. example: image/jpeg content: type: string contentEncoding: base64 description: >- Base64 file content. A data URI prefix such as `data:image/jpeg;base64,` is accepted. Attachment: type: object properties: id: type: string example: 6702d1bb2a3b4c5d6e7f8091 createdAt: type: string example: 2026-10-07T15:25:00+0000 name: type: string example: fan-belt.jpg uploadedBy: $ref: '#/components/schemas/UserSummary' workOrder: type: object properties: id: type: string example: 6702c4e1b8a3f21d9c0e4a17 identifier: type: string example: WO-1042 UserSummary: type: object properties: id: type: string example: 64f1a2b3c4d5e6f708192a3b firstName: type: string example: Dana lastName: type: string example: Ruiz email: type: string format: email example: dana.ruiz@example.com responses: AttachmentList: description: Uploaded attachments. content: application/json: schema: type: array items: $ref: '#/components/schemas/Attachment' BadRequest: description: The request is invalid. Check required fields, types, and limits. Unauthorized: description: The access token is missing, invalid, or expired. Request a new token. Forbidden: description: The service account lacks permission for this building or operation. NotFound: description: The resource does not exist or is not assigned to the service account. TooManyRequests: description: >- A rate-limit window is exhausted. Wait, then retry with increasing delays. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: > Paste an access token from [Create an access token](/products/kode-api/api-reference/authentication/create-an-access-token). Tokens expire, so request a new one if you receive `401`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.