2026 API Upgrade

in august 2025, we began upgrading our developer api to a more efficient platform as part of this upgrade, existing client credentials will be revoked on the 31st january 2026 and no longer provide access to the api existing customers will need to generate new client credentials and update their api clients to use our new api endpoints prior to this deadline to ensure a smooth transition key dates 1st july 2026 x sine team id header becomes mandatory see new request header requirement docid\ bsjtf4z0spl h639ho jr for more details 31st january 2026 the legacy api will be decommissioned any api clients that have not been updated to use the new domain and new credentials will no longer function 11th august 2025 our new api platform is launched and customers can login to their sine accounts to generate a new set of client credentials to use in their api clients the legacy api domain and credentials will continue to work during this transition period required changes new request header requirement a x sine team id header will be required for all requests as of july 1, 2026 you can find your team id in the sine dashboard under sine admin > settings > team details new api platform changes are my credentials affected? if you already have credentials for the legacy api, when you log in to the sine admin client and navigate to your public api credentials, a warning will appear (see below) generating new credentials until the 31st january 2026 deadline, the legacy api and the new api will operate side by side your existing credentials will continue to work unless you revoke them in the admin app log in to the sine dashboard click on the link to the admin app click on settings in the side menu click on the api keys tab generate a second credential for use with the new api update your integrations to point to the new api and use your new credentials once you are satisfied that your integration is working with the new api, revoke the old credential new api endpoint for more information on generating credentials, see the authentication section any integrations or software that accesses the public api must be updated to point to the new api url and use your new credentials to generate an access token legacy api new api https //api forge connected honeywell com https //api forge connected honeywell com https //openapi sine co https //openapi sine co