Skip to main content

How to Set Up Fleetio API Key Access for Bouncie

Setting up Fleetio API Key access

Written by Anthony

To connect Bouncie with Fleetio, you’ll need to generate an API Key and copy your Fleetio Account Token. These credentials allow Bouncie to securely sync vehicle and fleet data with Fleetio.

Follow the steps listed to complete the setup. If you need details about any step, tap it to expand the details.


Step 1: Log in to Fleetio

Log in to your Fleetio account using an admin account. You should see your Fleetio dashboard.


Step 2: Open Settings

From the left sidebar scroll down and tap Settings.


Step 3: Go to Manage API Keys

Inside Settings select Manage API Keys. This is where Fleetio stores API keys for external integrations like Bouncie.


Step 4: Create a New API Key

  1. Click the green Add API Key button in the top right corner.

  2. A pop up window will appear.


Step 5: Enter API Key Details

In the modal:

  • Label: Enter a name you will recognize later. (Example: Bouncie Integration)

  • API Version: Select the default version provided by Fleetio.

Then click Save. Fleetio will immediately generate your API token.


Step 6: Copy Your API Token

After saving:

  1. Find your new key in the list

  2. Copy the value under the Token column

Keep this token secure. It provides access to your Fleetio data.


Step 7: Copy Your Account Token

On the same page, scroll down to the Account Tokens section.

  1. Locate your account name

  2. Copy the value under Token

You will need both:

  • API Token

  • Account Token


Step 8: Add Credentials to Bouncie

Return to Bouncie and open the Fleetio integration setup.

Paste:

  • Fleetio API Token

  • Fleetio Account Token

Save your changes.

Once saved, Bouncie will begin syncing with Fleetio.


Troubleshooting

If the connection does not work, check the following:

  • The API key status shows Active

  • The full token was copied with no extra spaces

  • Your Fleetio account has Admin permissions


For your Security: Fleetio recommends creating a separate API key for each integration. If needed, you can revoke access at any time from the Manage API Keys page.

Did this answer your question?