> ## Documentation Index > Fetch the complete documentation index at: https://docs.withsplendor.com/llms.txt > Use this file to discover all available pages before exploring further. # Complete a hosted upload > Completes a multipart upload after all parts are uploaded and enqueues the uploaded object for ingestion. Track progress with the upload readiness endpoint or ingest runs. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/ingest/sources/{source_key}/uploads/complete openapi: 3.1.0 info: description: >- Splendor is a search and retrieval API for your operational data. Ingest datasets — logs, documents, and structured records — and query them through one consistent interface that spans full-text, SQL, and semantic (vector) search. Every request authenticates with a bearer token and selects a workspace with the `X-Splendor-Tenant-Id` header. Read and query operations are available to any member; operations that create, change, or delete data require an admin role. All search modes return one shared envelope, and every result carries provenance back to the exact source object it came from. title: Splendor API version: 1.0.0 servers: - description: Production url: https://api.withsplendor.com security: - bearerAuth: [] tags: - description: Resolve the authenticated user and the tenants they can access. name: Identity - description: >- Build on Splendor as a platform: authenticate with a platform API key to provision an isolated tenant per end-customer and manage your platform keys. name: Platform - description: >- List datasets, inspect inferred schemas and readiness, and manage dataset lifecycle including deletion and schema rebuilds. name: Datasets & schema - description: >- Run full-text, SQL, and semantic search over your datasets, stream results, and resolve object media. name: Search & query - description: Save queries and materialize result sets for repeatable analysis. name: Views - description: >- Define named, versioned, parameterized SQL queries and manage their versions. name: Query Endpoints - description: Create and manage asynchronous exports of search results. name: Exports - description: >- Configure data sources, upload data through hosted multipart uploads, stream logs, and track ingest runs. name: Sources & ingest - description: >- Connect third-party systems by managing connector instances in the selected tenant. name: Connectors - description: Define and test detection rules that run against incoming data. name: Detections - description: Inspect discovered fields and promote them to fast, aggregatable fields. name: Fields - description: >- Operational visibility and recovery: audit logs, usage, dead-letter queue, reindex jobs, and data-deletion jobs. name: Operations paths: /v1/ingest/sources/{source_key}/uploads/complete: post: tags: - Sources & ingest summary: Complete a hosted upload description: >- Completes a multipart upload after all parts are uploaded and enqueues the uploaded object for ingestion. Track progress with the upload readiness endpoint or ingest runs. operationId: completeUpload parameters: - in: path name: source_key required: true schema: title: Source Key type: string - $ref: '#/components/parameters/SplendorTenantId' requestBody: content: application/json: schema: $ref: '#/components/schemas/HostedUploadCompleteRequest' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/HostedUploadResponse' description: Successful Response '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The requested resource was not found. '409': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The request conflicts with the current state of the resource. '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error components: parameters: SplendorTenantId: description: Selects the tenant (workspace) the request acts within. in: header name: x-splendor-tenant-id required: true schema: type: string schemas: HostedUploadCompleteRequest: properties: parts: items: $ref: '#/components/schemas/HostedMultipartPart' title: Parts type: array upload_session_id: maxLength: 64 minLength: 1 title: Upload Session Id type: string required: - upload_session_id title: HostedUploadCompleteRequest type: object HostedUploadResponse: example: bucket: acme-uploads dataset_id: app-logs etag: '"abc123"' image_reference: s3://acme-uploads/uploads/ups_01H8Z3/data.jsonl key: uploads/ups_01H8Z3/data.jsonl source: app-logs source_id: 12 tenant_id: acme properties: bucket: title: Bucket type: string dataset_id: title: Dataset Id type: string etag: anyOf: - type: string - type: 'null' title: Etag image_reference: title: Image Reference type: string key: title: Key type: string source: title: Source type: string source_id: anyOf: - type: integer - type: 'null' title: Source Id tenant_id: title: Tenant Id type: string required: - bucket - key - etag - tenant_id - source_id - dataset_id - source - image_reference title: HostedUploadResponse type: object ApiError: description: >- Error envelope returned by every Splendor API endpoint. ``detail`` is either a plain message string (most errors) or a structured ``{code, message}`` object (validation and capacity errors that carry a stable machine-readable code). examples: - detail: Dataset not found - detail: code: semantic_search_capacity_exhausted message: Semantic search capacity is temporarily exhausted; retry shortly. properties: detail: anyOf: - type: string - $ref: '#/components/schemas/ErrorBody' title: Detail required: - detail title: ApiError type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object HostedMultipartPart: properties: etag: maxLength: 255 minLength: 1 title: Etag type: string part_number: maximum: 10000 minimum: 1 title: Part Number type: integer required: - part_number - etag title: HostedMultipartPart type: object ErrorBody: description: Structured error detail returned by validation and capacity errors. examples: - code: semantic_query_text_required message: Semantic vector search requires non-empty text. properties: code: title: Code type: string message: title: Message type: string required: - code - message title: ErrorBody type: object ValidationError: properties: ctx: title: Context type: object input: title: Input loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object responses: Unauthorized: content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The bearer token is missing, malformed, or expired. Forbidden: content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The token lacks access to the tenant or the role required. securitySchemes: bearerAuth: bearerFormat: JWT description: API token issued from the Splendor console. scheme: bearer type: http ````