# Ingest content with a workflow Triggers workflow execution for a specific content item and returns the complete workflow execution object. The system automatically selects the first available agent for the user's account. Workflow Ingestion Process: 1. Validates that the content item exists 2. Validates that the specified workflow exists 3. Automatically selects the first available agent for the user's account 4. Creates a workflow execution record 5. Executes all tasks in the workflow sequentially in the background using the selected agent 6. Returns the complete workflow execution object immediately Response Object: The endpoint returns a complete workflow execution object containing: - id: Unique identifier for this workflow execution - workflowId: ID of the workflow being executed - contentId: ID of the content being processed - dataspaceId: ID of the dataspace - status: Current status ('started', 'completed', or 'failed') - startedAt: Timestamp when execution began - completedAt: Timestamp when execution finished (null if still running) - errorMessage: Error details if execution failed (null if successful) Features: - Asynchronous workflow execution - Comprehensive validation before execution - Automatic agent selection for the user's account - Detailed logging and error handling - Database tracking of workflow and task executions - Complete workflow execution object response Example Usage: POST /api/content/sds-12345678/550e8400-e29b-41d4-a716-446655440000/ingest?workflowId=8a0667a8-a35e-4b0a-8a95-07b4fd5ac7de The workflow will execute in the background, and you can monitor its progress using the returned workflow execution object. Endpoint: POST /content/{dataspaceId}/{contentId}/ingest Version: 1.0.0 Security: bearerAuth ## Path parameters: - `dataspaceId` (string, required) Dataspace ID with sds- prefix Example: "sds-abc12345" - `contentId` (string, required) UUID of the content item Example: "123e4567-e89b-12d3-a456-426614174000" ## Query parameters: - `workflowId` (string, required) UUID of the workflow to execute Example: "123e4567-e89b-12d3-a456-426614174002" ## Response 202 fields (application/json): - `id` (string, required) Example: "123e4567-e89b-12d3-a456-426614174000" - `workflowId` (string, required) Example: "987fcdeb-51a2-43d1-9c4e-5f6e7d8c9a0b" - `primaryScopeObjectId` (string, required) Example: "456e7890-e89b-12d3-a456-426614174001" - `primaryScopeDataspaceId` (string, required) Short dataspace ID with sds- prefix Example: "sds-abc12345" - `status` (string, required) Enum: "started", "completed", "failed" - `startedAt` (string, required) Example: "2025-01-15T10:30:00Z" - `completedAt` (string,null, required) Example: "2025-01-15T10:35:00Z" - `errorMessage` (string,null, required) Example: "Workflow execution failed at step 3" ## Response 400 fields ## Response 401 fields ## Response 404 fields