> ## Documentation Index > Fetch the complete documentation index at: https://docs.msportal.ai/llms.txt > Use this file to discover all available pages before exploring further. # Finalize documentation file upload > Register the bytes PUT to uploadUrl as a file document in the documentation library. The stored size and type must match the body. Retrying with the same documentId returns the same document, so a timeout is safe to retry. The file is then listed by GET /api/public/v1/documentation/documents (source custom, documentKind file) and opens for that company's portal users under Documentation. Requires `documentation.write` and the linked user's write_settings_documentation permission; staff API keys only. ## OpenAPI ````yaml /openapi.json post /api/public/v1/documentation/files/{id}/finalize openapi: 3.0.3 info: title: MSPortal Public API version: 1.0.0 description: >- Public API for MSPortal - provides programmatic access to tenant data. ## Authentication All endpoints require authentication via API key passed as a Bearer token: ``` Authorization: Bearer ``` API keys can be created in the MSPortal dashboard under Settings → Integrations → API Access. **Important:** Do not include cookies in API requests. The public API uses stateless authentication only. ## Scopes API keys are granted specific scopes that determine what operations they can perform. Each endpoint documents its required scope(s). ## Rate Limiting API calls are rate limited per API key. Rate limit information is returned in response headers: - `X-RateLimit-Limit`: Maximum requests per minute - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: When the rate limit resets (ISO 8601) ## Request ID All responses include an `X-Request-Id` header for debugging and support. You can also pass your own `X-Request-Id` header to correlate requests. contact: name: MSPortal Support email: support@msportal.ai license: name: Proprietary servers: - url: https://app.msportal.ai description: Production (US) - url: https://eu.msportal.ai description: Production (EU) security: - BearerAuth: [] tags: - name: Budgets description: >- Budget management - create, track, and forecast budgets with line items, categories, and products - name: Calendar description: Calendar and meeting management - events, participants, and meeting types - name: Companies description: Company management endpoints - name: Company Users description: Company user management - client portal contacts (read-only, paginated) - name: Compliance description: Compliance check management - runs, assigned checks, and status updates - name: Dashboards description: Dashboard management - external iframe resources and internal dashboards - name: Devices description: Device management - inventory, types, and locations - name: Goals description: Goal management - create, track, and manage goals with tasks and updates - name: NPS Surveys description: >- NPS survey management - Net Promoter Score surveys, responses, and analytics - name: Reports description: >- Report management - create, manage, and schedule reports with templates and types - name: Planner description: >- Planner item management - tasks, roadmap items, and project planning with linked goals, compliance, and projects - name: Surveys description: >- General survey management - multi-question surveys, responses, and statistics - name: Tickets description: Ticket management - view and filter tickets from PSA integrations - name: Training description: >- Training management - courses, enrollments, certificates, and progress tracking - name: Users description: Tenant user management - internal staff and team members (read-only) - name: Automation Rules description: >- Automation rule management - create, configure, and monitor automation rules with triggers, conditions, and actions - name: Analytics description: >- Analytics and reporting - company audit data, training analytics, user activity, and portfolio metrics - name: Client Onboarding description: >- Client onboarding - portals (phases, tasks, contacts, activation), templates, checklist templates, forms and documentation pages - name: Backup description: >- Backup - summaries, protected devices, alerts and SaaS protection (Datto, Axcient, Slide, Kaseya) - name: Microsoft 365 description: Microsoft 365 - licenses, users, domains and Secure Score - name: Security description: >- Security - posture summary, EDR incidents, vulnerabilities, email threats, firewalls, DNS filtering and security awareness - name: Financial description: Financial - quotes, invoices and revenue summaries - name: Integrations description: Integrations - status, sync health, pause and resume (never credentials) - name: Documentation description: >- Documentation - pages, folders and articles synced from Hudu or IT Glue, plus built-in pages - name: Broadcasts description: Broadcasts - emergency broadcasts, recipients and groups - name: Notifications description: Notifications - the linked user's in-app notifications - name: Standards description: >- Standards - technology standards catalog, service plans, applicability, deployment statuses, compliance rollups, white space and costs - name: Customer Success description: >- Customer success - client health scores, trends, benchmarks and Traffic Light Reviews - name: Tasks description: Tasks - the linked user's personal task list - name: Tenant Setup description: Tenant setup - profile, branding and portal settings (never secrets) - name: Roles description: Roles - staff and client roles and their permission grants - name: Ticket Templates description: Ticket templates - reusable ticket definitions - name: Readiness description: Client readiness - account readiness assessments - name: Projects description: >- Projects - PSA projects with health overlays (deliverables, milestones, client actions, weekly updates), phases, tickets, time entries, PSA status/owner/priority write-through, ticket notes, task controls, display settings and the document library paths: /api/public/v1/documentation/files/{id}/finalize: post: tags: - Documentation summary: Finalize documentation file upload description: >- Register the bytes PUT to uploadUrl as a file document in the documentation library. The stored size and type must match the body. Retrying with the same documentId returns the same document, so a timeout is safe to retry. The file is then listed by GET /api/public/v1/documentation/documents (source custom, documentKind file) and opens for that company's portal users under Documentation. Requires `documentation.write` and the linked user's write_settings_documentation permission; staff API keys only. parameters: - schema: type: string format: uuid description: documentId from the prepare call required: true description: documentId from the prepare call name: id in: path requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DocumentationFileUploadRequest' responses: '201': description: File document created content: application/json: schema: type: object properties: data: type: object properties: id: type: string format: uuid name: type: string companyId: type: string format: uuid folderId: type: string nullable: true format: uuid fileName: type: string contentType: type: string fileSize: type: integer required: - id - name - companyId - folderId - fileName - contentType - fileSize required: - data '400': description: Validation error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: >- Forbidden - missing scope (documentation.write) or the linked user lacks the permission named in the endpoint description content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Company or folder not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: This documentId already holds a different file content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - BearerAuth: [] components: schemas: DocumentationFileUploadRequest: type: object properties: name: type: string minLength: 1 maxLength: 255 description: Title shown in the documentation library, e.g. 'Invoice 2026-1042' example: Invoice 2026-1042 fileName: type: string minLength: 1 maxLength: 255 description: 'File name with its extension: .pdf, .docx, .xlsx, .xls or .csv' example: invoice-2026-1042.pdf fileSize: type: integer minimum: 0 exclusiveMinimum: true maximum: 52428800 description: Exact size in bytes, at most 50 MiB example: 48213 contentType: type: string minLength: 1 maxLength: 200 description: >- MIME type of the file. The response's contentType is the one to send on the PUT. example: application/pdf companyId: type: string format: uuid description: >- Company (client) the document belongs to; its portal users can open it. Required unless folderId is a folder pinned to a company: a file without a company would be visible to every client, so it is refused. folderId: type: string format: uuid description: >- Custom folder ID (the UUID of a custom: key from the folders endpoint), e.g. an 'Invoices' folder. A folder pinned to a company only accepts that company. required: - name - fileName - fileSize - contentType description: >- Send the same body to prepare and finalize; finalize checks the stored bytes against it. ErrorResponse: type: object properties: error: type: string description: Error message requestId: type: string description: Request correlation ID details: nullable: true description: Additional error details code: type: string description: Error code required: - error securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: API Key description: >- Use your API key as a Bearer token. API keys can be generated in Settings → Integrations → API Access. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.