Service Application Management API

[kmoll]

Current Limitation

Service applications can currently only be managed through the UI. There's no API endpoint to programmatically update application settings like FQDN, Docker image, or proxy configuration.

Impact:

• No automation of domain changes
• Manual updates required

Proposed Solution

Add two API endpoints to enable programmatic service application management:

GET  /api/v1/services/{uuid}/applications
PATCH /api/v1/services/{uuid}/applications/{app_uuid}

Updatable Fields

• fqdn - Domain(s) with validation and conflict detection
• human_name - Display name
• description - Description text
• image - Docker image
• exclude_from_status - Monitoring exclusion
• is_log_drain_enabled - Log drain (validates server support)
• is_gzip_enabled - Gzip compression
• is_stripprefix_enabled - Path prefix stripping

Key Features

• FQDN Validation: Format checking, normalization (lowercase, dedupe, trim)
• Conflict Detection: Prevents duplicate domains across resources
• Auto-Regeneration: Updates docker-compose automatically when needed
• Security: Field whitelisting, team-based authorization

Use Cases

1. Automated Deployments: Update application domains during CI/CD
2. Multi-Environment Management: Script-based configuration across staging/production
3. DNS Integration: External tools can update Coolify domains programmatically
4. Bulk Operations: Update multiple service apps via scripts

Implementation

See PR: #[NUMBER]

API Examples

List applications:

GET /api/v1/services/{service-uuid}/applications
Authorization: Bearer {token}

Update FQDN:

PATCH /api/v1/services/{service-uuid}/applications/{app-uuid}
Authorization: Bearer {token}
Content-Type: application/json

{
  "fqdn": "app.example.com:8080"
}

Update multiple fields:

PATCH /api/v1/services/{service-uuid}/applications/{app-uuid}
{
  "human_name": "Production API",
  "fqdn": "api.example.com:8080",
  "is_gzip_enabled": true
}

Questions for Feedback

1. Field Coverage: Are there other fields that should be updatable via API?
2. Validation: Any additional validation rules needed for specific fields?
3. Naming: Do the endpoint paths follow Coolify API conventions?
4. Documentation: Is the implementation guide clear enough?

[muslimanim]

I opened a pull request #9249 for that plus some useful end points to stop/start/restart/deploy/logs for a Service Application