> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Register Portal Upload > Register uploaded media before using it in a listing field, guide, or offer. ## OpenAPI ````yaml POST /v1/workspaces/{workspace_id}/portal-uploads openapi: 3.0.0 info: title: Conduit API version: 1.0.0 description: Public API for Conduit. servers: - url: https://api.conduit.ai description: Production security: [] tags: - name: meta description: Discovery and API metadata endpoints. - name: agents description: >- Chat agent configuration, including instructions, skills, triggers, and automation behavior. - name: contacts description: >- Contact profile and contact-scoped related resources such as tickets and calls. - name: workspaces description: Workspaces accessible to the current API token. - name: escalations description: >- Chat escalations that require operator review, including message, proposed response, and disposition context when available. - name: conversations description: >- Canonical message threads. Use these endpoints to list threads, inspect conversation state, read transcripts, and send replies. - name: conversation-tags description: >- Conversation labels, root topics, and subtopics used for classification and topic analytics. - name: tickets description: >- Operational queue items tied to conversations, including ticket-scoped transcripts and replies. - name: calls description: Phone call records, transcripts, summaries, and recordings when available. - name: reservations description: >- PMS reservations synced from the workspace's integrations (Hostaway, Guesty, Airbnb, etc.), including guest identity, payment status, and stay dates. - name: appointments description: >- Scheduled appointments (bookings) backed by the Conduit booking service. Exposes allocation context and the upstream booking-service `external_id`. - name: helpdesk_tickets description: >- Helpdesk tickets mirrored from external helpdesk integrations (Zendesk, Pylon, Plain), including requester identity and upstream metadata. - name: kb description: >- Knowledge base search and node management. Nodes represent knowledge base entries (files or directories), chunks are the indexed retrieval units used by search. - name: skills description: >- Workspace agent skills that can be attached to chat agents. Sidebar/global-assistant skills are intentionally excluded. - name: custom_tools description: >- Custom code tools: user-authored Python/JavaScript functions executed in a sandbox when an agent calls them. Includes a runtimes endpoint describing the entrypoint signature, return shape, and available dependencies per language. - name: inbox_types description: >- Workspace inbox types. Each id is stable and usable as a message trigger's `inbox_type_id` and as the `inbox_type_id` filter on list conversations. - name: workflows description: >- Workspace automation workflows: definitions, executions, and per-execution event timelines. - name: insights description: Aggregated workspace analytics, such as conversation automation rate. paths: /v1/workspaces/{workspace_id}/portal-uploads: post: tags: - portals summary: Register Portal Upload description: >- Validate and register an uploaded image or video. Pass storage_id from the upload response with the scope used to create the upload URL. For listing_field, reference the returned storage_id as storageId in update_portal_listing_field's document. For guide and offer, use the returned url in create_portal_guide, patch_portal_guide, create_portal_offer, or patch_portal_offer: as cover_image_url or image_url, a guide media item's imageUrl, or a guide video embed's url with uploaded set to true. Media already registered to another workspace or scope is rejected. listing_field requires ManageProperties; guide and offer require ManagePortals. Requires Portals access and write access. operationId: registerPortalUpload parameters: - schema: type: string minLength: 1 description: Workspace identifier required: true description: Workspace identifier name: workspace_id in: path requestBody: required: true content: application/json: schema: type: object properties: scope: type: string enum: - listing_field - guide - offer description: >- Where the media will be used: listing_field for a portal listing field document, guide for a portal guide, or offer for a portal offer. listing_id: type: string minLength: 1 description: >- PMS listingId from list_listings. Required for listing_field and rejected for guide and offer. storage_id: type: string required: - scope - storage_id responses: '200': description: Register Portal Upload content: application/json: schema: type: object properties: data: type: object properties: storage_id: type: string url: type: string required: - storage_id - url required: - data '400': description: Invalid request content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '404': description: Not found content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '409': description: Conflict content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Token description: >- Conduit API token. Use `Authorization: Bearer `. Read/write endpoints require a token with write access. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.