Lifecycle management

Comprehensive app lifecycle management including HTTP-triggered execution, status monitoring, and app termination.

Authentication

None

No authentication required for lifecycle management endpoints. Source system credentials are provided in request body when needed.

Endpoints

Get app status

GET

/workflows/v1/status/{workflow_id}/{run_id}

Retrieve real-time execution status, progress metrics, and result data for a specific app run instance, including start/end timestamps and error details if the app failed.

Path Parameters

workflow_idstringREQUIRED

Unique identifier for the app

Example:"4b805f36-48c5-4dd3-942f-650e06f75bbc"

run_idstringREQUIRED

Unique identifier for a specific execution instance of the app

Example:"efe16ffe-24b2-4391-a7ec-7000c32c5893"

Response

200App status retrieved successfully

successbooleanREQUIRED

Boolean flag indicating whether the status request was processed successfully, regardless of app execution state

Example:

true

messagestringREQUIRED

Human-readable confirmation message indicating successful status retrieval operation

Example:"App status fetched successfully"

dataobjectREQUIRED

App execution state and metadata returned by the underlying client implementation

Error Codes

400

Bad Request

Invalid app ID or run ID format

401

Unauthorized

Missing or invalid authentication token

404

Not Found

App or app run not found

500

Internal Server Error

App operation failed

Code examples - Get app status

cURL

BASH Request (cURL)

curl -X GET "http://localhost:8000/workflows/v1/status/4b805f36-48c5-4dd3-942f-650e06f75bbc/efe16ffe-24b2-4391-a7ec-7000c32c5893"

Python

Python Request (Python)

import requests

response = requests.get(
  f"http://localhost:8000/workflows/v1/status/{workflow_id}/{run_id}"
)
status_data = response.json()