Skip to main content

Access, limits and support

Getting access​

Contact your Transit Technologies account manager for a client ID and client secret. We send the two separately, through a secure channel.

Tell us whether you need read-only access or also write access (driver assignment). Most integrations start with a read-only test.

The notification stream is optional, and set up separately on request. If you need it, ask for it, and we send you a queue SAS URL through a secure channel.

Limits​

  • Rate limits. We do not publish a fixed rate limit. Poll at a reasonable rate, for example once a minute per vehicle at most. For real-time data, use the notification stream instead of polling.
  • Pagination. GetAssets and GetDrivers return the full list in one reply. There is no pagination.
  • Tokens. Re-use a token until it is close to expiry. See Authentication.

History and backfill​

The gRPC API returns current status only. The one exception is diagnostic trouble codes, which you can query by date range. The API has no calls for historical GPS, trips or events.

To keep a full history, read the notification stream and store each update. For an initial backfill of past data, contact us with the vehicles, data types and date range you need, and we will confirm what we can export.

Media and footage​

  • An event's MediaUrl opens the media in VestigeView. The user must be signed in and must have access to the vehicle.
  • Body camera messages carry direct MP4 download links in Mp4Urls.

These links lead to footage of real people. Store and share them with the same care as the footage.

Support​

Contact your Transit Technologies account manager, or our support team, with your account name and, for API errors, the method, the time (UTC) and the status code you received.