The plumbing behind the tiles

How ServiceTitan Data Reaches a Custom Dashboard, and the Places It Can Go Missing on the Way

Every tile on a custom ServiceTitan dashboard is the end of a short journey: a request, a response, a calculation, a check. Owners never need to see the pipes. They do deserve to know where the pipes can leak, and who is watching them.

November 13, 2026 · 10 min read

dash.acmeelectric.com · overnight sync log
Reads from ServiceTitan, checked before they reach a tile
One column went missing; the tile held its last good value
Sample
  1. 05:00 token issued, expires in 900 s
  2. 05:00 export/jobs from continueFrom token: 412 rows
  3. 05:01 export/invoices: 388 rows, fields validated
  4. 05:01 report query returned 202, polling
  5. 05:02 expected column missing from report fields
  6. 05:02 revenue tile held at 04:00 value, office alerted
Illustrative: a sample overnight sync log for a fictional electrical contractor

The short answer

A custom dashboard gets ServiceTitan data in two ways: it pulls raw records such as jobs, invoices, calls and memberships through export feeds, or it runs ServiceTitan's own reports through the Reporting API. As of November 2026, export data appears 15 minutes after a change by default, the Reporting API allows one run of the same report per minute per tenant, and the API Terms limit how long content may be stored.

On this page
  1. Two roads out of ServiceTitan, each with a toll
  2. The records a dashboard actually reads, field by field
  3. The Reporting API after ServiceTitan's July 2026 change
  4. Fifteen minutes, one report a minute, and a fifteen-minute token
  5. Section 5.2 is the clause that draws the architecture
  6. What breaks between ServiceTitan and the screen, and the checks that catch it
  7. Who switches it on, and how fast it goes live

Two roads out of ServiceTitan, each with a toll

There are two ways to feed a dashboard from ServiceTitan, and most builds use some of each. The choice is not technical trivia. It decides whether your close rate matches the one on ServiceTitan's screen, how fresh it can be and what happens when ServiceTitan changes something. This is our reading of ServiceTitan's published documents, labeled as inference, not a statement from ServiceTitan.

Rebuild from raw records

  • Read jobs, invoices, estimates and calls, then count them with your own written rules
  • Uses ServiceTitan's own fields, such as a job type's soldThreshold and a call's callType, to mirror its logic where you want it mirrored
  • Fits the general rate limit, generous for a dashboard
  • Risk: your count can differ from ServiceTitan's screen unless the rule is written to match

Run ServiceTitan's reports

  • Ask the Reporting API for a report's output, already calculated the ServiceTitan way
  • Columns arrive with the same labels the reporting screens use
  • Limited to one run of the same report per minute per tenant
  • Risk: ServiceTitan warns the columns may change, and it does not say whether the output matches the on-screen report exactly

For an owner's screen, we lean toward rebuilding the core counts from raw records with definitions agreed in writing, then tie them out against a ServiceTitan report once a month. The tie-out method is the one in our guide to why ServiceTitan reports disagree. The general mechanics of ServiceTitan's API, from app registration to bookings, are on our ServiceTitan API integration guide, and this page does not repeat them.

The records a dashboard actually reads, field by field

ServiceTitan's API reference lists 25 families. A dashboard reads perhaps eight. The fields below come from ServiceTitan's public OpenAPI documents on its Developer Portal, downloaded November 11, 2026, and each one maps to a number covered elsewhere in this section.

ServiceTitan API records a custom dashboard reads, with field names from ServiceTitan's OpenAPI documents, November 2026
RecordFields a dashboard usesNumbers it feeds
JobscompletedOn, businessUnitId, jobTypeId, campaignId, noCharge, recallForId, leadCallId, soldById, totalRevenue, callback rate, lead source
Job typessoldThreshold ("A job is considered as converted if subtotal meets or exceeds this threshold") and noChargeConversion and close rate logic
Invoices and itemsinvoiceDate, dueDate, subTotal, balance, adjustmentToId; items carry generalLedgerAccount, soldHours, technicianIdRevenue, receivables, revenue per hour
EstimatessoldOn, status, subtotal, businessUnitIdSales, unsold estimates
Calls (Telecom v3)receivedOn, duration, direction, callType, reason with its lead flag, campaign, agentBooking rate, lost calls
Membershipsstatus, from, to, nextScheduledBillDate; a feed of membership status changesActive, renewing and lapsing members on the memberships dashboard
Payroll timesheets and splitsarrivedOn, doneOn, technicianId; splits carry splitHours on the job, credit on the technician scorecard
Campaign costsPer campaign: year, month, dailyCost; a cost summary with totalCostCost per booked job on the marketing ROI dashboard
Glowing cyan and blue lines flowing from left to right into a row of rising bars on a deep blue and violet field over a thin data grid
Raw records go in one side; counted, checked numbers come out the other.

One gap is worth knowing in advance. ServiceTitan's Accounting document, as read in November 2026, has no accounts receivable aging endpoint. A receivables screen therefore builds its aging buckets from invoice fields such as dueDate and balance, which is our inference from the fields listed. The cash and receivables dashboard page covers what that screen shows.

The Reporting API after ServiceTitan's July 2026 change

ServiceTitan's Reporting API lives at api.servicetitan.io/reporting/v2, with a twin on the integration domain for testing. Its OpenAPI description is short: "Dynamic value sets, reports, report categories." Release ST-78 on July 2, 2026 changed how data comes out. Per the release note, the new query "Returns result inline (200 OK) for fast reports (~10s), or a token + status (202) if still running," and it replaces the deprecated synchronous data endpoint.

  • Polling is safe. The release note calls polling "Safe to retry without re-running the report," and canceling a query frees "its concurrency slot." How many slots a tenant has is not stated.
  • Pages are large. Report data pages run from 1 to 25,000 rows, with 1,000 as the default, per the Reporting API document.
  • Filters come from the report. Each report describes its parameters, with a name, a data type and whether it is required; lists such as business units come from dynamic value sets.
  • Columns can change. The document warns: "Beware that report columns may be changed. Result field names are listed alongside the data in the response to validate that all the requested columns are there."

Two questions remain open in ServiceTitan's public documents as of November 2026: whether a tenant's own custom reports can be run through the Reporting API, and whether its output matches the on-screen report to the cent. Neither is stated. A build that depends on either gets tested on your account before anyone signs off.

Fifteen minutes, one report a minute, and a fifteen-minute token

A dashboard's freshness is set by three clocks, all published by ServiceTitan and all current as of November 2026. Knowing them ends the hunt for a perfectly live screen, which does not exist on any platform and is not needed for a morning decision.

Export feeds: 15 minutes

ServiceTitan's transactional and export guide says export data becomes available 15 minutes after a change unless includeRecentChanges is true. Feeds page through records with from and continueFrom tokens.

Rate limits per tenant

The developer FAQ allows "600 calls per 10 seconds per application per tenant for all APIs except reporting APIs," and reporting APIs "1 of the same report per minute per tenant."

Tokens: 15 minutes

ServiceTitan supports only OAuth 2.0 client credentials. Access tokens expire in 15 minutes and no refresh tokens are issued, so the server requests and caches new ones.

No push, so the clock asks

ServiceTitan's FAQ says "V2 webhooks are currently being developed" and new subscriptions to current webhooks are restricted. A dashboard therefore reads on a schedule rather than waiting to be told.

There is a tension worth reading for yourself. ServiceTitan's API Terms of Use, last updated April 15, 2026, bar sending "more request messages to ServiceTitan's servers than a human could reasonably produce in the same period using a conventional web browser," and bar any attempt to "exceed or attempt to circumvent any rate limits." The same company documents export feeds built to pull large volumes. We do not reconcile the two for you; read your agreement and ask ServiceTitan how they apply.

Section 5.2 is the clause that draws the architecture

Where data may live matters more than how fast it moves. The API Terms say developers "must not store or cache any Content obtained from the APIs for longer than 24 hours, except to the extent expressly permitted by these Terms or the Documentation." Content must be stored so it can be identified, segregated and selectively deleted, and when a customer disconnects, the content obtained from that customer must be deleted.

  • Display. Section 5.1: "Content that pertains to a particular customer may only be displayed to that customer."
  • Deletion on request. Section 5.3 requires removing and destroying content "within twenty-four (24) hours upon email or other written request from ServiceTitan."
  • Least data. Section 2.4 asks for "only the minimum API scopes, endpoints, permissions, and data access necessary," and 3.4(26) bars using more than the minimum the app needs.
  • Undefined edges. The terms do not say whether a total calculated from API data, such as last March's revenue, counts as Content.

What breaks between ServiceTitan and the screen, and the checks that catch it

Integrations fail in ordinary ways. ServiceTitan ships API releases often: ST-78 came on July 2, 2026, and its release notes list ST-82, dated November 3, 2026, as the latest when we checked on November 11. Its API Terms say updates "may or may not be accompanied by notice" and that it "does not promise any particular uptime or provide SLAs." A dashboard has to assume something will change on a Tuesday. These are the checks we build in, as our own practice:

  1. 1

    Validate every response

    Compare the returned field names with the ones the screen expects. A missing column stops the tile from updating rather than letting it show a wrong total.

  2. 2

    Stamp every read

    Each tile shows when it last read ServiceTitan successfully. Stale is acceptable; silently stale is not.

  3. 3

    Hold the last good value

    When a read fails, the tile keeps its last good number, marked with the time, and someone is alerted.

  4. 4

    Tie out monthly

    Pick one ServiceTitan report per core number and match dates and business unit filters, the method ServiceTitan's own mismatch article recommends.

  5. 5

    Log settings changes

    A retroactive sold threshold edit can move last quarter's numbers. A dated note saves an afternoon of suspicion.

Those checks run under the hosting and maintenance plan. The human version of the last two happens in the monthly numbers review, where a moved number gets explained before anyone acts on it.

Who switches it on, and how fast it goes live

Two ServiceTitan permissions govern API access: "Generate API Application Key" to register apps, and "Manage API Application Access" to create client IDs and secrets. The customer's admin approves the app under Settings > Integrations > API Application Access. ServiceTitan's Customer Integration Paths page says customer-built apps need "the Works or Ent Plus package." Customers also have an integration environment that, per ServiceTitan's access guide, "contains a copy of their production data," which is the right place to test.

Once your admin approves the app, the API connection goes live the same day. The dashboard itself is from $575 to build, as of November 2026, with a fixed written estimate, plus hosting from $55 a month; our custom ServiceTitan dashboards page has the offer and our API integrations page the general approach. No ServiceTitan data warehouse or BI connector appears in ServiceTitan's public documentation as of November 2026. The ServiceTitan dashboards hub maps every role screen and explainer, and you can reach us at (210) 346-0848.

Questions owners ask about ServiceTitan dashboards and numbers

Not quite. ServiceTitan's export feeds make a change available 15 minutes after it happens by default, as of November 2026, and its FAQ says new webhook subscriptions are restricted while V2 webhooks are developed. A dashboard reads on a schedule instead. For a morning owner's screen, minutes-old data is plenty, and the screen shows when it last read ServiceTitan.

ServiceTitan's public documents do not say. The Reporting API lists report categories and the reports in each, describes a report's parameters and returns its data, but whether a tenant's custom reports appear there is not stated as of November 2026. We test it on your account before relying on it, and rebuild the count from raw records if needed.

None appears in ServiceTitan's public documentation as of November 2026, and neither Microsoft's Power BI pricing page nor Google's Data Studio page, formerly Looker Studio, lists one. As of November 2026, Google says Data Studio "is available at no charge for creators and report viewers." Getting ServiceTitan data into either tool still takes an API connection someone has to build and maintain.

ServiceTitan's developer FAQ allows "600 calls per 10 seconds per application per tenant" for regular APIs and "1 of the same report per minute per tenant" for reporting APIs, as of November 2026. Its API Terms also bar exceeding or circumventing rate limits and request volumes beyond what a human could produce in a browser. Read your agreement on how those apply.

That depends on your agreement. ServiceTitan's published API Terms limit storing API content to 24 hours unless the terms or documentation allow more, and do not say whether calculated totals count as content. We design around that clause and ask you to confirm with your own agreement and ServiceTitan before the build. It is the first design question, not the last.

ServiceTitan's API Terms say that when a customer disconnects, the content and data obtained from that customer through the APIs must be deleted. A dashboard reading ServiceTitan stops showing new numbers at that point, and the stored content goes with it. Reading resumes only if your admin approves the app again, so plan any pause with that clause in mind.

Keep reading

Free · No obligation

Ask how your numbers would travel

Tell us which numbers you want on screen and your ServiceTitan package. A person at DataCram replies with the records and reports we would read, the refresh you can expect, and the questions to settle with your agreement first.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote