Saia REST Onboarding Requirements and Configuration Guides [Information]

Last updated: September 29, 2026

This article serves as the central hub for integrating Saia REST with techSHIP. It details the necessary credentials for onboarding, explains the configuration hierarchy required to start shipping, and outlines operational constraints specific to this carrier.

   

   

   

  

To review all supported carriers and their specific requirements, see: techSHIP supported Carriers - Master List [Guides List].

   

   

TABLE OF CONTENTS



Onboarding Requirements



Before configuring Saia REST in techSHIP, you must gather specific credentials and verify account settings. 



Information to be Provided



The following credentials and data points are required to begin the setup:

     

DATA ELEMENT

SOURCE (HOW TO OBTAIN)

Ocp-Apim-Subscription-Key

Provided by Saia REST for API access

RQ Key

Provided by Saia REST for rating API usage

Sender Address

The origin warehouse / induction address used for the carrier account

   

Settings to be Verified



The following account configurations must be validated before setup:

   

FEATURE/SETTING

VALIDATION ACTION

Carrier Credentials

Confirm the Saia-provided Ocp-Apim-Subscription-Key and RQ Key have been received before starting the connection setup

Origin Address

Verify the sender / induction address is complete and matches the location that will be used for shipping

   





WARNING: Missing carrier credentials or an incomplete sender address will prevent the Saia REST connection from being configured correctly.

 

Configuration Hierarchy and Guides



To establish a valid connection and start shipping, you must complete the mandatory levels in the following order: 



Gather Onboarding Requirements  ➔

Carrier Baseline Account ➔

Client (Billing) Account 



Use the table below to access the detailed configuration guides for each level, by clicking in the blue icons:

   

LEVEL

COMPONENT

MANDATORY

SCOPE

DESCRIPTION

CONFIGURATION GUIDE

1

Onboarding Requirements

Requirements

You are here.

2

Baseline Account

Carrier

Establishes the core technical connection. Must be created first.

3

(Billing) Account

Client

Connects a specific client to the Baseline. At least one is required to ship.

4

Order Settings

   

Transaction

Defines advanced service options.

   

Carrier Specifications and Constraints



This section outlines specific operational behaviors and data limitations inherent to the Saia REST integration. 



Labels



The following table summarizes BOL and label support specific to this carrier:

    

ITEM

SUPPORTED

Label

Supported

References

Not supported

BOL

Supported

   

The table below summarizes the confirmed label reference behavior for Saia REST:

   

CONSTRAINT TYPE

LIMIT/REQUIREMENT

Label References

4

   

   

   

  

For a comprehensive guide on how to use label references, see: Using order References in your labels [Step-by-Step guide].

   

   

Operational Constraints



This section details specific operational rules and limitations imposed by Saia REST. These constraints are enforced by the carrier or by the current integration behavior and must be considered when planning your shipping workflow:

  • Only PDF label output is supported.

  • For Collect shipments, include the Destination Account code in the Billing Account.

  • For Third Party shipments, include the Third party Account code in the Billing Account.

  • Broker Address is required for Mexico shipments.