Release Notes
- What's new
- Known issues
- Troubleshooting
- License reference
Get Started
- Welcome
- What is ADK?
- Getting started with the ADK
- Tutorials
- Environments
- Resources & Guides
Connections
Large Language Models (LLMs)
Tools
Orchestrate copilot
- Overview
- Starting and stopping copilot
- Prompt-Tune
Evaluation Framework
Web chats
watsonx Orchestrate Developer Edition
- Overview
- Installing the Developer Edition
- Managing watsonx Orchestrate Developer Edition
- watsonx Orchestrate Developer Edition APIs
- Orchestrate Agent
- Assistants Runs
- Custom Assistants
- watsonx Assistant
- External Chat Agents
- Message Threads
- Documents
- Vector Index
- Catalog Management
- Tenant Management
- Provisioning Lite
- Embed settings
- User Profiles
- Completions
- Background Tasks
- Auth
- Orchestrate Assistant
- Notifications
- IBM unique ID mapping
- Prompts
- Artifact Management
- Default Agent Settings
- all journey types
- Connections
- Tools
- Welcome Content
- LLM Analytics
- Internal Calls are listed over here
- Agents
- Agent Releases
- Agent Release Environments
- Agent Chat Starter Settings
- API Reference
- channel integration
- Knowledge-Bases
- Chat with Docs
- Toolkits
- Voice Configurations
- Models
- Model-Policy
- Credentials
- Teams Channel
- Twilio WhatsApp Channel
Legal notices
Alive
Copy
Ask AI
curl --request GET \
--url http://localhost/api/v1/health/aliveCopy
Ask AI
"<any>"API Reference
Alive
Get liveness status of the server. We are always assuming alive because of reconnection strategies
GET
/
health
/
alive
Alive
Copy
Ask AI
curl --request GET \
--url http://localhost/api/v1/health/aliveCopy
Ask AI
"<any>"Response
200 - application/json
Success
The response is of type any.
Assistant
Responses are generated using AI and may contain mistakes.