Skip to main content

Freightview

Freightview is a web-based LTL (less-than-truckload) freight management platform that enables shippers to compare carrier rates, book shipments, print labels and bills of lading, and track freight in real time from a single interface. The platform aggregates quotes from multiple LTL carriers simultaneously, giving businesses visibility into pricing and transit times before committing to a booking. Freightview integrates with ERPs, e-commerce platforms, shopping carts, and other business systems through its RESTful API, enabling teams to automate rate shopping, shipment creation, and tracking data retrieval. Its API supports both retrieving freight data (rates, shipments, tracking events) and initiating actions (booking shipments), making it suitable for building end-to-end logistics workflows.

Freightview icon

Power end-to-end data operations for your Freightview API with Nexla. Our bi-directional Freightview connector is purpose-built for Freightview, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Freightview or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Freightview workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

To connect Nexla to Freightview, you need an active Freightview account and an API key. Freightview's API uses HTTP Basic Authentication, where the API key serves as the username and the password field is left empty. The API is available at https://www.freightview.com/api/v1.0/.

Freightview offers two API keys per account: an Account API key and a secondary key. The Nexla connector uses the Account API key for authentication. For additional information about Freightview's API, see the Freightview Developer Documentation.

Obtain a Freightview API Key​

Freightview API keys are managed from within your Freightview account settings. To locate your API key:

  1. Sign in to your Freightview account at freightview.com.

  2. Click your username (or name) in the top-right corner of the screen to open the account menu.

  3. On the account page, locate the Account Settings sidebar on the left side and click API Keys (also referred to as Api Integration in some versions of the interface).

  4. You will see two API keys listed. Copy the key labeled Account API key — this is the key required for Nexla integration.

Important

Treat your API key like a password. Do not share it publicly, store it in source code, or expose it in client-facing applications. If your key is ever compromised, return to this page and regenerate it immediately.

For step-by-step guidance on locating your API key, see the How to Get Your Freightview API Key guide on the Freightview blog.

Authenticate​

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your Freightview Account API key in the API Key field. Nexla will use this key as the username in HTTP Basic Authentication headers when making requests to the Freightview API. No password is required — the Freightview API expects the key as the username with an empty password.

    The API key is transmitted securely and stored encrypted within Nexla. Freightview's API authenticates requests using the HTTP Basic Auth standard, with the API key in the username position and no value in the password position.

  4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Freightview connector tile, then select the credential that will be used to connect to the Freightview instance, and click Next; or, create a new Freightview credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Freightview endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get Shipments

Retrieves a list of LTL shipments from your Freightview account. Use this endpoint to ingest historical or ongoing shipment records for reporting, analysis, or syncing shipment data with other business systems. The Freightview API returns shipment details including carrier, status, origin, destination, weight, and tracking information.

  • No additional parameters are required to use this template. Nexla will automatically retrieve all shipment records accessible to your Freightview account and handle pagination.
  • Each shipment record includes fields such as shipment ID, carrier name, pro number, pickup date, origin and destination addresses, total weight, freight charges, and current status.

The Freightview API returns shipment data in JSON format. For additional information about the shipment data structure and available fields, see the Freightview API Reference.

Get Rates

Retrieves LTL freight rates from carriers configured in your Freightview account. Use this endpoint to pull rate quote data for cost analysis, carrier benchmarking, or feeding rate information into downstream pricing or procurement workflows.

  • To use this endpoint, provide the shipment details required to generate a rate quote. Common required parameters include:

    • Origin ZIP: The ZIP code of the shipment's origin location.
    • Destination ZIP: The ZIP code of the shipment's destination location.
    • Weight: The total weight of the shipment in pounds.
    • Freight Class: The NMFC (National Motor Freight Classification) freight class for the shipment commodity.
  • Freightview will return rate quotes from all configured carriers in your account, along with transit times, accessorial charges, and total estimated costs.

Rate results are based on the carrier contracts configured in your Freightview account. Ensure your carrier accounts are active and connected in Freightview before using this endpoint. For information about connecting carriers, see the Freightview Developer Documentation.

Get Tracking Events

Retrieves tracking event history for LTL shipments in your Freightview account. Use this endpoint to monitor shipment progress, build shipment visibility dashboards, or trigger automated workflows based on shipment status changes such as pickup, in-transit, delivered, or exception events.

  • Tracking events are associated with specific shipments. To retrieve tracking information, the source will query Freightview for tracking updates across your active shipments.
  • Each tracking event record includes the shipment ID, pro number, event timestamp, event description, and current delivery status.

Tracking data availability depends on the carrier and whether the carrier provides electronic tracking updates to Freightview. For the most accurate tracking information, ensure that your carrier accounts are properly configured and that electronic tracking is enabled. For additional details, see the Freightview API Reference.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Freightview data sources can also be manually configured to ingest data from any valid Freightview API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

All Freightview API URLs use the base https://www.freightview.com/api/v1.0/ followed by the resource path — for example, https://www.freightview.com/api/v1.0/shipments, /rates, or /tracking. If no version is specified, the API defaults to version 1.0. Freightview responses typically include a top-level array named data, so the path to data is commonly set to $.data[*].

You do not need to add authentication headers manually — the Freightview API's Authorization header (HTTP Basic Auth) is added automatically based on your Freightview credential.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Freightview data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Freightview destination, and select the Send to Destination option from the menu. Select the Freightview connector from the list of available destination connectors, then select the credential that will be used to connect to the Freightview organization, and click Next; or, create a new Freightview credential for use in this flow.

Manual configuration​

Freightview destinations are manually configured to send data to any valid Freightview API endpoint, enabling workflows such as programmatically booking LTL shipments, requesting rate quotes, or creating new shipment records directly from your Nexla data flows. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks. Common methods for Freightview write operations include:

  • POST: For creating new shipment records, booking shipments, or submitting rate requests
  • PUT: For updating existing shipment records
  • PATCH: For partial updates to existing shipment data

The Freightview API accepts and returns data in JSON format, so JSON is the recommended Content Format for every Freightview destination. All Freightview API URLs use the base https://www.freightview.com/api/v1.0/ — common destination paths include https://www.freightview.com/api/v1.0/shipments for creating or booking shipments and https://www.freightview.com/api/v1.0/rates for submitting rate requests. For update or upsert operations targeting a specific shipment record, include the shipment ID at the end of the URL, for example https://www.freightview.com/api/v1.0/shipments/{shipment_id}.

You do not need to add authentication headers manually — the Freightview API's Authorization header (HTTP Basic Auth) is added automatically based on your Freightview credential.

Enabling the response webhook option is particularly useful for Freightview destinations, since it allows you to capture the shipment ID assigned to a newly booked LTL shipment or the bill of lading number generated by Freightview after each API call.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Freightview endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to Freightview until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.