Freightview is a cloud-based transportation management system (TMS) that allows businesses to streamline their shipping processes.
This video demonstrates creating a Freightview connection.
After you start the connection, configure it in the Create connection panel and complete all of the required * authentication settings:
Setting |
Instructions |
---|---|
Name your connection * |
Enter a clear and distinguishable name. Throughout integrator.io imports and exports, you will have the option to choose this new connection. A unique identifier will prove helpful later when selecting it from a list of the connections in your account. |
API type * |
Choose the API type, depending on the Freightview API type you're connecting to. The settings then become specific to the selected API type. The Freightview API has multiple versions, all of which are accessible at any time by using the defined base endpoint and version number. Version changes are made when backwards incompatible changes are made. |
Setting |
Instructions |
---|---|
Account type * |
Select the required account you are connecting to. If your account URL is If your account URL is |
API key * |
Enter your Freightview account API key/User API key. |
-
Sign in to your Freightview developers account.
-
Navigate to Settings > API integration.
-
V1 API window opens.
-
Copy Account API key / User API key.
Setting |
Instructions |
---|---|
Account type * |
Select the required account you are connecting to. If your account URL is If your account URL is |
OAuth 2.0 client * |
Select the OAuth 2.0 client that stores the API key (client ID and client secret) provided to you by Freightview.
To add an OAuth 2.0 client and configure your credentials, click the plus ( + ) button. Click the edit ( |
-
Sign in to your Freightview developers account.
-
Navigate to Settings > API integration.
-
V2 API window opens.
-
Copy Client ID.
-
Copy Client secret.
Tip
This connector documentation describes only the settings shown for the Simple view. For the corresponding HTTP settings, see OAuth 2.0 universal connector documentation.