PSTrax API Library & Integrations

Overview

PSTrax offers a robust API (Application Programming Interface) and a growing library of integrations designed to help you centralize your operations. By connecting PSTrax with your other critical software systems—such as RMS, CAD, and supply vendors—you can automate data workflows, reduce manual entry, and ensure real-time accuracy across your department.

Accessing the API Documentation

Getting Authorized for the PSTrax API

Before you can pull data from PSTrax, you'll need an API token — and you can generate one yourself in about a minute.

Overview

Access to the PSTrax API library is free and self-service. There's no request form to submit, no separate developer account to create, and no need to contact PSTrax Support to be set up. You use your existing PSTrax username and password to generate a token, and that token is what authorizes your requests.

Everything below happens on the developer portal, which doubles as an interactive testing tool — you can authorize yourself and run live requests against your own department's data right in your browser before writing any code.

Before You Begin

You'll need an active PSTrax user account, and you'll need to be logged in. The developer portal sits behind the platform login, so if you open it without an active session, you'll be redirected to your station home page instead of the documentation.

Log in to PSTrax first, then open the portal in a new tab in the same browser.

Requesting Your API Token

To generate a token:

1. Log in to your PSTrax platform.
2. Visit the developer portal at: https://app1.pstrax.com/api/v1/developer/docs
3. Click Authentication to expand the section.
4. Click POST /api/v1/developer/core/auth/grant.
5. Click Try it out.
6. In the request body, replace the sample username and password with your own PSTrax credentials, keeping the quotation marks and formatting in place.
7. Click Execute.

Your token appears in the Server response section below, in the token field:

{ "token": "12345678|ExampleTokenString1234" }

Copy the value of the token field — the text between the quotation marks, without the quotation marks themselves.

Copy the entire value, including the numbers and the vertical bar at the front. That leading number is part of your token, not a line number. If you begin copying after the vertical bar, you'll end up with a token that looks correct but fails on every request.

Authorizing Your Session

Once you have the token, apply it to the portal:

1. Click Authorize at the top of the page.
2. In the token field, type the word Bearer, add a single space, then paste your token.
3. Click Authorize, then Close.

The completed entry looks like this:

Bearer 12345678|ExampleTokenString1234

The word Bearer and the space after it are required, and you have to type them yourself. The portal sends this field exactly as you enter it, so a token pasted on its own will be rejected. Don't add quotation marks around any of it.

To confirm authorization worked, expand Core - Department and run GET /api/v1/developer/core/department. If your department name and ID come back, you're authorized, and every other endpoint on the page will work the same way for the rest of your browser session.

Using Your Token Outside the Browser

If your technical team is building an integration rather than testing by hand, the same two calls apply. Request a token with a POST to the grant endpoint:

https://app1.pstrax.com/api/v1/developer/core/auth/grant

Send the credentials as a JSON body:

{ "username": "your.username", "password": "your-password" }

Then send the token on every request in the Authorization header, with the same Bearer prefix:

Authorization: Bearer 12345678|ExampleTokenString1234

A few things worth knowing:

• The token is tied to the user account that generated it and carries that account's permissions. It isn't tied to a browser session, so closing your browser doesn't invalidate it.
• Treat the token like a password. Don't commit it to source control, don't put it in a URL, and don't share it.
• Build your integration to request a fresh token when calls start coming back unauthorized, rather than storing one indefinitely.
• You'll only ever see data for your own department, limited to what the account that generated the token can access.

Troubleshooting

• You're redirected to your station home page instead of the documentation. You aren't logged in to PSTrax in that browser. Log in first, then reopen the portal link.
• "Failed to load API definition." Usually the same cause — log in and reload the page. If it continues while you're logged in, contact PSTrax Support.
• Your credentials are rejected when requesting a token. Check the username and password, and confirm you can log in to PSTrax with them.
• Every endpoint is rejected after you authorize. The Bearer prefix is missing, or quotation marks were included. Reopen Authorize and re-enter it as Bearer + space + token.
• The token looks right but still isn't accepted. Confirm the leading numbers and vertical bar are still at the front of the token. Copying from after the bar is a common slip.
• Requests worked before and now don't. Your token is no longer valid. Generate a new one using the steps above.

Featured Integrations

PSTrax currently supports native integrations with several industry-leading partners to streamline your fleet and logistics management:

• First Arriving: Visualize vehicle status, equipment alerts, and station logs directly on your digital dashboards. More Info here

• Life-Assist: Automatically sync supply catalogs, view real-time pricing, and submit purchase orders directly through the Procurement module. More info here.

• Bound Tree: Automatically sync supply catalogs, view real-time pricing, and submit purchase orders directly through the Procurement module. More info here
• Fleetio: Create a Fleetio issue and track that issue's progress from a Fleet Dashboard inside PSTrax—no need to log in to Fleetio to see where things stand. More Info here.

 Key Differences