Midland Onboarding Requirements and Configuration Guides [Information]

Modified on Thu, 13 Aug at 9:30 AM


Onboarding and Configuration	Baseline Account	(Billing) Account
You are here

This article is the central hub for adding Midland with techSHIP. It summarizes onboarding requirements, links the related configuration guides, and lists confirmed carrier-specific constraints.

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

TABLE OF CONTENTS

Onboarding Requirements
- Information to be Provided
- Settings to be Verified
Setup Articles
Carrier Specifications and Constraints
- Labels
- Operational Details
Next Steps

Onboarding Requirements

Before configuring Midland in techSHIP, gather the required credentials and verify the required account settings.

Information to be Provided

The following credentials and data points are mandatory to establish the connection. Ensure you have these items available before starting the setup:

DATA ELEMENT	SOURCE (HOW TO OBTAIN)
Midland API Key	Provided by Midland.
Pickup API Key	Request from Midland Transport at productsolutions@midlandtransport.com.
Sender ID	Provided by Midland.
Induction Address	Confirm the induction address to use for the Midland account.

Settings to be Verified

The following account configurations must be validated to prevent errors during the connection setup or the shipping process:

FEATURE/SETTING	VALIDATION ACTION
Midland Credentials	Confirm the Midland API Key, Pickup API Key, and Sender ID were obtained from Midland before configuration.

Any missing or incorrect onboarding information can delay the Midland setup process.

Setup Articles

Use the setup articles below to complete the setup in order. Start with onboarding requirements, then configure the Baseline Account and Client (Billing) Account. Select an article number to open the corresponding guide:


COMPONENT	ONBOARDING REQUIREMENTS	BASELINE ACCOUNT	(BILLING) ACCOUNT
Mandatory
Scope	Requirements	Carrier	Client
Description	Identifies the required onboarding information and organizes the related setup guides for Midland.	Establishes the Midland carrier connection. Must be created first.	Connects a specific client to the Midland Baseline Account. At least one is required to ship.

Carrier Specifications and Constraints

This section outlines confirmed operational behaviors, document support, label support, and limitations specific to Midland.

Labels

The following table summarizes confirmed document and label support:

ITEM	SUPPORTED
Label	Supports PDF, PNG, and ZPL.

Operational Details

This section lists confirmed operational rules and limitations for Midland.

ZPL mode is available only for Courier Ground, Courier Air, Courier Speed Letter, and Courier Deferred Air.
Use PDF or PNG for the Midland LTL Baseline Account.
For Midland LTL shipments, techSHIP automatically sends a pickup request to Midland when the manifest is finalized.
Midland LTL pickup requests are submitted once per manifest finalization flow, not after each individual order is processed.
Pickup cancellation is not supported through this integration.

Next Steps

After reviewing the onboarding requirements, continue with the Reference Data: Midland Baseline Account Fields [Guide] article to configure the carrier connection in techSHIP.

	Go to

Onboarding and Configuration	Baseline Account	(Billing) Account

Name	Host	Duration	Description
_fw_crm_v	techdinamics.freshdesk.com	1 year	Freshchat/Freshworks cookie (Used to track Visitor/User identity and chat sessions performed by the User).
_x_w	techdinamics.freshdesk.com	Session	Contains the shard ID at which the account runs on.
_x_m	techdinamics.freshdesk.com	Session	Contains the state of the shard.
_helpkit_session	techdinamics.freshdesk.com	Session	Your secret key for verifying cookie session data integrity. If you change this key, all old sessions will become invalid!
helpdesk_node_session	techdinamics.freshdesk.com	Session	An encrypted hash that stores the secret key and id of the login attempt.
user_credentials	techdinamics.freshdesk.com	2 months	Used for user authentication.
wf_order	techdinamics.freshdesk.com	Session	Used to check in which the order the tickets are filtered for custom ticket filters eg: due_by, agent_responded_at, requester_responded_at, etc.
wf_order_type	techdinamics.freshdesk.com	Session	Used to check if the order is ascending or descending for custom ticket filters.
wf_filter	techdinamics.freshdesk.com	Session	Denotes which filter is applied for the tickets list.