Unisson customer-files API
The customer-files API from Unisson — 3 operation(s) for customer-files.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/unisson-customer-files-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Unisson agent-evals Customer Files API
version: 1.0.0
servers:
- url: https://api.unisson.ai
description: Base URL declared by the provider in apis.yml (roadmap#122).
tags:
- name: customer-files
paths:
/api/v1/customers/{customer_id}/files:
get:
tags:
- customer-files
summary: List Customer Files
description: 'List the generated workspace files linked to this customer, newest first.
Each file carries a presigned download URL plus source attribution (the
conversation that produced it and, for agent-workspace files, the owning
agent). Metadata comes straight from the provenance row — no per-file S3
HEAD — so this stays a pure DB read + URL signing (cf. documents.py).'
operationId: list_customer_files_api_v1_customers__customer_id__files_get
security:
- HTTPBearer: []
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
format: uuid
title: Customer Id
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/CustomerFileListResponse'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/api/v1/customers/{customer_id}/files/{file_id}/content:
get:
tags:
- customer-files
summary: Get Customer File Content
description: 'Stream a customer file''s bytes through the backend for the in-app viewer.
Going through the backend (instead of the presigned URL) sidesteps S3 CORS
and serves the guessed mime type so the previewer renders inline rather
than forcing the attachment download the presigned URL carries.'
operationId: get_customer_file_content_api_v1_customers__customer_id__files__file_id__content_get
security:
- HTTPBearer: []
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
format: uuid
title: Customer Id
- name: file_id
in: path
required: true
schema:
type: string
format: uuid
title: File Id
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/api/v1/customers/{customer_id}/files/{file_id}:
delete:
tags:
- customer-files
summary: Delete Customer File
description: 'Delete a generated file from the customer.
Members only — the guest write guard blocks this DELETE (it is not in
``deps.py::_GUEST_WRITE_ALLOWLIST``). The provenance row keys the single
physical object, so deleting here also removes it from the originating
agent/conversation workspace.'
operationId: delete_customer_file_api_v1_customers__customer_id__files__file_id__delete
security:
- HTTPBearer: []
parameters:
- name: customer_id
in: path
required: true
schema:
type: string
format: uuid
title: Customer Id
- name: file_id
in: path
required: true
schema:
type: string
format: uuid
title: File Id
responses:
'204':
description: Successful Response
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
components:
schemas:
CustomerFileListResponse:
properties:
files:
items:
$ref: '#/components/schemas/CustomerFileResponse'
type: array
title: Files
type: object
required:
- files
title: CustomerFileListResponse
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
CustomerFileResponse:
properties:
id:
type: string
format: uuid
title: Id
name:
type: string
title: Name
path:
type: string
title: Path
created_at:
anyOf:
- type: string
format: date-time
- type: 'null'
title: Created At
download_url:
anyOf:
- type: string
- type: 'null'
title: Download Url
source_conversation_id:
anyOf:
- type: string
format: uuid
- type: 'null'
title: Source Conversation Id
source_conversation_title:
anyOf:
- type: string
- type: 'null'
title: Source Conversation Title
source_agent_id:
anyOf:
- type: string
format: uuid
- type: 'null'
title: Source Agent Id
source_agent_name:
anyOf:
- type: string
- type: 'null'
title: Source Agent Name
source_agent_icon:
anyOf:
- type: string
- type: 'null'
title: Source Agent Icon
source_agent_gradient:
anyOf:
- type: string
- type: 'null'
title: Source Agent Gradient
type: object
required:
- id
- name
- path
title: CustomerFileResponse
description: 'A generated workspace file linked to a customer (see
``models.workspace_file_customer``). ``id`` is the provenance row''s PK —
used to address the file in the content/delete endpoints.'
securitySchemes:
HTTPBearer:
type: http
scheme: bearer