Step Who does it Watch for
Turn on the two API permissions A ServiceTitan admin at the shop enables Generate API Application Key and Manage API Application Access for whoever will set this up. Without them, the developer portal won't offer the right options, and it looks like a login problem.
Create the app In the portal, My Apps, then +New App. Add the tenant ID and tick the API Scope the app needs. Ask for the scopes the integration actually uses. Each one is something the shop is agreeing to share.
Copy the app key Keys, then Application Key. This goes with every API call, in the ST-App-Key header. It identifies the app, not the shop. It's not the client secret.
Connect the app to the shop In ServiceTitan: Settings, search Integrations, API Application Access, Connect New App, then Allow Access. Only someone with Manage API Application Access can do this. It's the step owners don't expect to be theirs.
Generate the client ID and secret On the same connected app, copy the Client ID and click Generate next to Client Secret, then pass both to the developer securely. Credentials made in the integration environment don't work in production, and the other way round.
First call The developer requests an access token with the client ID and secret (OAuth 2.0 client credentials), then calls the API with the token and the app key. Most endpoints carry the tenant ID in the path, so a missing or wrong tenant fails even with a good token.