Web trigger lifecycle APIs now available for Forge Container Services

You can now manage web trigger URLs programmatically from within your Forge Container Services environment. These new REST API endpoints provide parity with the @forge/api package and the Forge CLI, allowing your container-based apps to create, list, and delete web trigger URLs.

What's changing We’ve added the following HTTP endpoints to the Forge Container Services REST API:

• POST /forge/webtrigger/url: Create a new web trigger URL or retrieve an existing one.
• GET /forge/webtrigger/urls: Retrieve all web trigger URLs associated with the app.
• DELETE /forge/webtrigger/url: Delete a specific web trigger URL.

These endpoints enable containerized apps to handle their own web trigger lifecycle dynamically without relying on external CLI commands.

What you need to do If your container-based app requires dynamic web trigger management, you can start using these endpoints immediately. Refer to the Forge Container Services REST API documentation for detailed request and response schemas.