Common ServiceTitan Gotchas
Avoid common pitfalls in API scoping, business unit mapping, and sync management.
API Scopes & 403 Errors
A "403 Forbidden" error is almost always caused by missing scopes in the ServiceTitan Developer Portal. IT Titan requires access to:
- • Settings (Read)
- • Capacity (Read)
- • Jobs (Read/Write)
- • Customers (Read/Write)
Business Unit Mapping
If your jobs aren't showing up on the board, check your BU mapping. IT Titan needs to know which ServiceTitan Business Units correspond to your website's service categories.
Check this in Portal → Rules & Logic
Sync Latency
ServiceTitan API data is highly accurate but not always "instant." There can be a 1-3 minute lag between a technician's status change in the field and the API reflectiing that availability.
Sandbox vs Production
Always test your rules in the ServiceTitan Sandbox environment first. ST Production data is "Real" and once a job is pushed, it affects your dispatchers' live board immediately.
Stuck on a technical error?
Our implementation engineers are ServiceTitan API experts. We can help you debug your connection in real-time.
Submit Technical Ticket