Setup overview

Open the Saia carrier profile in Shipwell.
Create a new account under the carrier’s Accounts tab.
Enter the required credentials and account configuration details.
Save the account and validate with a live rating test.

In Shipwell, navigate to the relevant Carrier Profile for SAIA. If direct connectivity is supported, the profile will include an Accounts tab in the left navigation. Open that tab and click Add Account.

Account configuration

When creating the account, complete the following fields.

Field	Required	How to use it
Account Name	Yes	Enter a clear, meaningful name. This name appears in rate results beneath the carrier logo.
Account Credentials	Yes	Enter the User Name, Password, Account Number, Rating API Key, Tracking API Key, eBOL API Key, and Documents API Key.
Origins	No	Use when multiple accounts apply to different pickup locations, or if the account has location specific rates. Leave blank if one account should work for all origins.
Destinations	No	Use when multiple accounts apply to different delivery locations, or if the account has location specific rates. Leave blank if one account should work for all destinations.
Modes	Yes	Select the transportation mode supported by this account, typically LTL.
Bill To Terms	Conditional	Choose Blank, Prepaid, Collect, or 3rd Party. If not blank, all bill-to contact fields become required.
Is Rate Share Provider	No	Leave unchecked for a true direct carrier account.
Account Notes	No	Add internal guidance such as lane usage, billing constraints, or facility-specific instructions.

Recommended setup pattern

Create one account per billing or facility scenario if the customer uses multiple account numbers.
Use Origins and Destinations to control which account is selected automatically.
Name accounts in a way that makes selection obvious, such as Direct - Chicago or Direct - West Coast Prepaid.

Best practice
If a customer has multiple site-specific pricing accounts, create separate Shipwell accounts for each one and scope them with Origin and Destination rules instead of using a single generic setup.

Bill-to configuration guidance

Bill-to settings affect dispatch behavior and can also impact rating outcomes depending on how the carrier validates the request.

If Bill To Terms is not blank, complete all related bill-to fields.
If the shipment already has bill-to data before dispatch, Shipwell keeps the shipment’s existing bill-to information.
If the shipment bill-to is blank and the carrier account contains bill-to data, Shipwell applies the account’s bill-to details during dispatch.
If both shipment and carrier account bill-to data are blank, Shipwell falls back to the company profile bill-to information at dispatch time.

Validation steps

Save the account configuration.
Create or open a valid LTL shipment with complete origin, destination, class, weight, and pallet details.
Request rates and confirm that the direct account returns a quote.
Verify the configured Account Name appears under the carrier logo on the rate results page.
If dispatch is in scope, tender a test shipment and confirm whether a Pickup Number or PRO Number is assigned as expected.
If tracking is in scope, monitor the shipment after tender to confirm status updates are flowing correctly.

Getting your SAIA API Keys

SAIA Secure Account

If the user is a customer of Saia, the user should ask their sales representative to set up a Saia Secure account for them. In the event the customer does not have a Saia sales representative and needs to create a Saia Secure account, have the customer navigate to Saia.com and click the LOG IN button.

The user should then click on REGISTER and create their Saia Secure account.

· Once the account is created, have the user email saiasecuresupport@saia.com to expedite the account activation process.

· The Saia Secure account is used for Basic Authentication in the REST Tracking API and used to return customer specific pricing in the REST Rate Quote API.

· Once an account is created and the user is signed in, the user can subscribe to Saia’s APIs using the following steps.

Saia Developer’s Portal Account
The Developer’s Portal should NOT be used for documentation purposes. The Portal
should only be used to subscribe to applicable APIs and to procure API keys where
required.
The production Saia Developer’s Portal is located at
https://saiaprodapi.developer.azure-api.net/.
Once an account is created and the user is signed in, the user can subscribe to Saia’s
APIs using the following steps.

Click on the Products button.