> ## Documentation Index > Fetch the complete documentation index at: https://docs.mavera.io/llms.txt > Use this file to discover all available pages before exploring further. # Get presigned upload URL > Generate a presigned URL for direct file upload. This allows clients to upload files directly to storage without passing through the API server. After uploading, call `POST /files` to create the database record. ## OpenAPI ````yaml /openapi.json post /files/upload-url openapi: 3.0.3 info: title: Mavera API version: 1.0.0 description: >- # Getting Started The Mavera Responses API provides persona-powered AI responses using the **OpenAI Responses API format**. Use `client.responses.create()` with the OpenAI SDK — just set the base URL to `https://app.mavera.io/api/v1`. ## Authentication All API requests require a Bearer token. Create an API key in **Settings > Developer > API Keys**. ``` Authorization: Bearer mvra_live_your_key_here ``` ## Quick Start ### Step 1: Get a Persona ID Every response request requires a `persona_id`. First, list available personas: ```bash curl https://app.mavera.io/api/v1/personas \ -H "Authorization: Bearer mvra_live_your_key_here" ``` This returns personas you can use. Copy the `id` field from any persona. ### Step 2: Create a Response Use the persona ID in your request: ```bash curl https://app.mavera.io/api/v1/responses \ -H "Authorization: Bearer mvra_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{ "model": "mavera-1", "persona_id": "YOUR_PERSONA_ID", "input": "Hello!" }' ``` ## Rate Limits Per-key sliding window limits based on your subscription tier: | Tier | Requests / min | |------|---------------| | Starter | 60 | | Basic | 120 | | Professional | 240 | | Enterprise | 600 | When rate limited, the response includes a `Retry-After` header indicating how many seconds to wait. ## Credits Each API call consumes credits from your subscription. The `usage.credits_used` field in the response shows the cost of each request. contact: name: Mavera Support url: https://mavera.io x-logo: url: /Mavera_Logo_Full.png altText: Mavera servers: - url: https://app.mavera.io/api/v1 description: Production - url: https://dev.mavera.io/api/v1 description: Development security: - BearerAuth: [] tags: - name: System description: Health checks and operational status. - name: Responses description: >- Generate persona-powered AI responses using the OpenAI Responses API format. Use `client.responses.create()` with the OpenAI SDK. - name: Models description: Discover available models and their capabilities. - name: Personas description: >- Browse available personas to inject specialized intelligence into responses via `persona_id`. - name: Custom Personas description: >- Create, manage, and customize AI-powered personas. Supports three creation pipelines: North Star (AI-generated from minimal input), Intermediate (guided 3-step process), and Advanced (full B2B/B2C customization with psychographics and purpose packs). 300 credits per persona. - name: Brand Voice description: >- Create, manage, and retrieve brand voice profiles for AI-powered content generation. Upload URLs and documents to analyze, and the AI will generate tone guidelines, vocabulary preferences, and writing style recommendations. - name: Generations description: >- Generate AI-powered content using pre-built templates with optional brand voice styling. Browse available generation apps, create content, and manage your generation history. Supports streaming responses. - name: Mave description: >- Mave is Mavera's AI-powered research and analysis agent. Send messages to conduct comprehensive investigations using multiple data sources, personas, and fact-checking. Mave uses a multi-phase orchestration process (Triage, Planning, Research, Execution, Validation) to deliver well-researched responses with sources. - name: Workspaces description: >- Manage workspaces for organizing your work. Workspaces contain projects, threads, personas, and other resources. Invite team members with role-based access control. Set budget alerts and usage limits. - name: Projects description: >- Organize work within workspaces using projects. Projects contain threads, generations, and other resources. Track usage and set per-project budget controls. - name: Meetings description: >- Access meeting recordings, transcripts, and AI-powered analysis. List meetings, retrieve transcripts in multiple formats (segments, text, SRT), get AI analysis with summaries, tasks, decisions, highlights, and coaching metrics. Run custom schemas to extract structured data from transcripts. - name: Schemas description: >- Create and manage meeting schemas for structured data extraction. Schemas define fields to extract from meeting transcripts, with support for various field types (text, enum, list, boolean, etc.), evidence tracking, and scoring. - name: Files description: >- Upload, manage, and retrieve files/assets. Use presigned URLs for direct uploads to avoid passing files through the API. Supports images, videos, documents, and more. File uploads count against your storage quota. - name: Folders description: >- Create and manage folders to organize your files. Folders can be favorited and shared with workspace members. - name: Video Analysis description: >- AI-powered video and advertisement analysis. Submit videos for comprehensive emotional, cognitive, behavioral, and technical analysis. Chat with AI about the results. - name: Focus Groups description: >- AI-powered synthetic focus group research. Create focus groups with personas to gather market research, product feedback, and audience insights. Supports 12 question types including NPS, Likert scales, and open-ended responses. - name: News description: >- AI-powered news intelligence. Browse trending stories, get AI analysis from persona perspectives, and manage scheduled news digests. Story analysis uses credits based on token usage. - name: Usage description: >- Monitor your subscription usage including credits, transcription minutes, storage, and API request metrics. Get real-time statistics on your billing period usage. paths: /files/upload-url: post: tags: - Files summary: Get presigned upload URL description: >- Generate a presigned URL for direct file upload. This allows clients to upload files directly to storage without passing through the API server. After uploading, call `POST /files` to create the database record. operationId: createUploadUrl requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CreateUploadUrlRequest' responses: '200': description: Presigned upload URL generated content: application/json: schema: $ref: '#/components/schemas/UploadUrlResponse' '400': description: Validation error (e.g., file too large, storage quota exceeded) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Authentication error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Workspace or folder not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' x-codeSamples: - lang: curl label: cURL source: |- curl -X POST https://app.mavera.io/api/v1/files/upload-url \ -H "Authorization: Bearer mvra_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{ "file_name": "image.png", "file_type": "image/png", "file_size": 524288, "workspace_id": "ws_abc123" }' - lang: python label: Python source: |- import requests import hashlib def upload_file(file_path, workspace_id, api_key): # Read file and compute checksum with open(file_path, "rb") as f: content = f.read() checksum = hashlib.sha256(content).hexdigest() file_name = file_path.split("/")[-1] file_type = "application/octet-stream" # Or detect from extension headers = {"Authorization": f"Bearer {api_key}"} # Get presigned URL response = requests.post( "https://app.mavera.io/api/v1/files/upload-url", headers=headers, json={ "file_name": file_name, "file_type": file_type, "file_size": len(content), "checksum": checksum, "workspace_id": workspace_id } ).json() # Upload to presigned URL requests.put( response["upload_url"], data=content, headers={"Content-Type": file_type} ) # Create file record file = requests.post( "https://app.mavera.io/api/v1/files", headers=headers, json={ "name": file_name, "type": file_type, "url": response["public_url"], "workspace_id": workspace_id, "file_size": len(content) } ).json() return file components: schemas: CreateUploadUrlRequest: type: object required: - file_name - file_type - file_size - workspace_id properties: file_name: type: string description: Name of the file to upload file_type: type: string description: MIME type of the file (e.g., 'image/png', 'application/pdf') file_size: type: integer minimum: 1 description: >- File size in bytes. Maximum 10MB for regular files, 2GB for video files. checksum: type: string description: SHA256 checksum of the file for integrity verification (optional) workspace_id: type: string description: Workspace to upload the file to folder_id: type: string description: Optional folder ID to organize the file UploadUrlResponse: type: object description: Response containing the presigned upload URL and instructions properties: object: type: string enum: - upload_url upload_url: type: string format: uri description: Presigned URL for uploading the file (PUT request) public_url: type: string format: uri description: Public URL where the file will be accessible after upload key: type: string description: Storage key for the file expires_in: type: integer description: Seconds until the upload URL expires (3600 = 1 hour) method: type: string enum: - PUT description: HTTP method to use for uploading headers: type: object description: Headers to include when uploading to the presigned URL properties: Content-Type: type: string description: The file's MIME type x-amz-checksum-sha256: type: string description: SHA256 checksum if provided next_step: type: object description: Instructions for completing the upload properties: description: type: string endpoint: type: string body: type: object ErrorResponse: type: object description: >- All error responses follow this format. The `type` field indicates the category of error, and `code` provides a machine-readable error code. properties: error: type: object properties: message: type: string description: A human-readable error message. example: Invalid API key. type: type: string enum: - invalid_request_error - authentication_error - insufficient_credits - not_found - rate_limit_error - api_error description: The category of error. example: authentication_error code: type: string description: A machine-readable error code. example: invalid_api_key param: type: string nullable: true description: The request parameter that caused the error, if applicable. example: null example: error: message: Invalid API key. type: authentication_error code: invalid_api_key param: null securitySchemes: BearerAuth: type: http scheme: bearer description: >- API key prefixed with `mvra_live_`. Create keys at **Settings > Developer > API Keys**. ````