# DEPRECATION of Build Trigger API on 'www' subdomain (use 'app' subdomain or the public API instead) **URL:** \ **Category:** Changelog\ **Tags:** announcements\ **Created:** [April 5, 2018, 10:49am UTC](https://discuss.bitrise.io/t/deprecation-of-build-trigger-api-on-www-subdomain-use-app-subdomain-or-the-public-api-instead/4721 "2018-04-05T10:49:29Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\ **Post date:** [April 26, 2018, 11:29am UTC](https://discuss.bitrise.io/t/deprecation-of-build-trigger-api-on-www-subdomain-use-app-subdomain-or-the-public-api-instead/4721/2 "2018-04-26T11:29:22Z")
**Important update** based on your feedback: if you roll your own automation built for [bitrise.io](http://bitrise.io) **please use [api.bitrise.io](http://api.bitrise.io) directly**, for everything, including the build triggering! Build Trigger endpoint is now available for [api.bitrise.io](http://api.bitrise.io) : [Bitrise API: build trigger, bitrise.yml](http://discuss.bitrise.io/t/bitrise-api-build-trigger-bitrise-yml/4860) > _Important note: [api.bitrise.io](http://api.bitrise.io) right now does not support the App’s own API Token, the one which is on the `Code` tab of the app on [bitrise.io](http://bitrise.io) , it only supports Personal Access Token auth as the rest of [api.bitrise.io](http://api.bitrise.io)_ In short, **all API endpoints which are expected to be used publicly are moving into [api.bitrise.io](http://api.bitrise.io), we’re deprecating all other endpoints.** Please don’t use those for any integration, instead migrate to [api.bitrise.io](http://api.bitrise.io) which is designed to provide the public API endpoints. --- _[View the full topic](https://discuss.bitrise.io/t/deprecation-of-build-trigger-api-on-www-subdomain-use-app-subdomain-or-the-public-api-instead/4721)._