Getting your API Access Token

đź“š API Token Information

API tokens allow you to authenticate with the Axscend API to access your fleet data programmatically. You can use API tokens to integrate Axscend with third-party systems, build custom reporting, or automate workflows.

Each token is unique to your account and should be treated like a password.

For more information on what's available via the API, see the Axscend API documentation.

Generating an API Token

đź“Ś

You’re logged into your Axscend Portal account.

  1. Click your Username in the top navigation bar.

  2. In the Dialog box:

    1. Click the API Access Tokens tab

    2. Click Create Token.

    3. Enter a descriptive Token Name. This helps you identify the token's purpose later (e.g. "Power BI Integration" or "Warehouse System").

    4. Select an expiry date for your token to automatically revoke.

    5. Click Create.

  3. Your new token will be displayed.

  4. Copy the token.
    For security reasons, the full token value is only shown once and cannot be retrieved after this step. A new token will need to be created if this token is lost or not copied.

  5. Click Close

Only store the token securely (e.g. in a password manager or secrets vault).

ScreenRecording2026-06-25at13.17.22-ezgif.com-video-to-gif-converter.gif

Revoking an API Token

If a token is no longer needed, or you suspect it has been compromised, you should revoke it immediately.

đź“Ś

You’re logged into your Axscend Portal account.

  1. Click your Username in the top navigation bar.

  2. In the Dialog box:

    1. Click the API Access Tokens tab

    2. Click Revoke

      1. You can also click Revoke All to revoke all listed tokens.

    3. When prompted to confirm the action, click Delete

ScreenRecording2026-06-25at13.22.29-ezgif.com-video-to-gif-converter.gif

The token will be invalidated immediately. Any system or integration using that token will lose access to the API until a new token is provided.

Best Practices

  • Using one token per integration makes it easy to revoke access for a single system without affecting others.

  • Rotate tokens regularly. Generate a new token and revoke the old one periodically as part of your security hygiene.

  • Never share tokens and avoid committing tokens to source code repositories or sharing them over email or chat.

  • Label tokens clearly by using descriptive names so you always know which system a token belongs to.

  • Choose sensible expiry dates.

âť“ Frequently Asked Questions

"My API requests are returning a 401 Unauthorised error"

Ensure the token is still active and has not been revoked. Then check that you are passing the token correctly in the request header.

Refer to the authentication section of the API docs for the correct format.

"I forgot to copy my token after generating it"

The full token value is only displayed once. If you didn't save it, you'll need to revoke the existing token and generate a new one.

"I need to audit which integrations are using the API"

Each token is listed by name in the API Access Tokens Tab, along with its creation date, expiry date, and last accessed date.

Use descriptive token names at creation time to make auditing straightforward, and a sensible expiry date.