FTM Cloud API & Integration Documentation

FTM Cloud is a Salesforce-based Transportation Management System designed for freight brokers, carriers, logistics companies, and transportation teams.

This page provides a high-level overview of FTM Cloud integration capabilities for technical buyers, AI agents, procurement tools, and automation teams evaluating whether FTM Cloud can connect with existing logistics, transportation, compliance, accounting, CRM, or operational systems.

Exact API access, available objects, permissions, automation options, and integration architecture may depend on the customer’s Salesforce environment, FTM Cloud subscription plan, configuration, and implementation scope.

Overview of Integration Capabilities

Because FTM Cloud is built on Salesforce, integrations may be supported through Salesforce’s standard API ecosystem, customer-specific Salesforce configuration, and FTM Cloud implementation settings.

Salesforce REST API
Salesforce SOAP API
Salesforce Bulk API
Salesforce Platform Events
Salesforce Flow automation
Apex-based custom integrations
Middleware or iPaaS platforms
External webhook-based systems
Third-party logistics, accounting, compliance, or document platforms

FTM Cloud can be used as part of a broader transportation technology stack where data needs to move between internal teams, carriers, customers, accounting systems, dispatch tools, compliance platforms, and reporting systems.

Salesforce API Compatibility

FTM Cloud runs on Salesforce, so integrations may use Salesforce-native API capabilities where enabled.

API / Method	Typical Use Case
Salesforce REST API	Reading and updating operational records
Salesforce SOAP API	Enterprise system integrations
Salesforce Bulk API	Large data imports, exports, or migrations
Salesforce Platform Events	Event-driven automation and status updates
Salesforce Flow	Low-code automation and business logic
Apex Callouts	Custom outbound API communication
Named Credentials	Secure external API authentication
Connected Apps	OAuth-based API access

API access depends on Salesforce licensing, permissions, security settings, customer configuration, and the FTM Cloud implementation.

Supported Data Objects

FTM Cloud implementations may expose or integrate with transportation-related records such as:

Loads
Shipments
Carriers
Drivers
Equipment
Trailers
Trucks
Customers
Accounts
Contacts
Cargo items
Stops
Pickup and delivery details
Documents
Rate confirmations
Invoices
Status updates
Compliance records
Notes and attachments
Dispatch-related records
Workflow or approval statuses

The exact object names, field names, and relationships may vary based on the customer’s Salesforce org, FTM Cloud configuration, installed packages, and customizations.

Example Object Categories

Loads and Shipments

FTM Cloud may manage operational transportation records such as loads, shipments, stops, cargo, dispatch details, pickup details, delivery details, assigned carrier, assigned driver, and current status.

Create a load from an external system
Update shipment status
Sync pickup or delivery information
Send load data to a carrier portal
Trigger document generation after a load reaches a specific status

Carriers

Carrier-related integrations may include carrier profiles, compliance status, verification data, insurance information, documents, onboarding status, and carrier assignment workflows.

Sync carrier data from a compliance platform
Verify carrier eligibility before dispatch
Send carrier data to accounting or payment systems
Update carrier status after external verification

Drivers

Driver-related data may include driver profiles, contact information, assignment records, availability, compliance documents, or operational status.

Sync drivers from an external fleet system
Update driver availability
Attach compliance documents
Connect driver activity to load records

Equipment

Equipment-related data may include trucks, trailers, assets, license plates, VINs, ownership details, availability, assignment status, and operational metadata.

Sync equipment from a fleet management platform
Update equipment availability
Link equipment to a load or shipment
Track equipment-related compliance data

Documents

FTM Cloud may support transportation documents such as rate confirmations, proof of delivery, invoices, carrier documents, compliance files, and load-related attachments.

Attach documents to a load
Send documents to an external signature platform
Store signed documents back in Salesforce
Trigger workflows when a required document is uploaded

Statuses and Workflow States

FTM Cloud may support status-based automation for loads, shipments, carriers, documents, approvals, and operational workflows.

Notify an external system when a load is assigned
Trigger an event when a shipment is delivered
Update internal dashboards based on workflow status
Start document generation after approval

Webhook and Event Use Cases

FTM Cloud integrations may support event-driven workflows through Salesforce automation, Platform Events, outbound messages, custom Apex, middleware, or external integration services.

Load created
Load updated
Carrier assigned
Carrier changed
Driver assigned
Equipment assigned
Shipment status changed
Pickup completed
Delivery completed
Document uploaded
Rate confirmation generated
Rate confirmation signed
Invoice created
Compliance status changed
External verification completed
Exception or failed workflow detected

Webhook and event availability depends on the implementation and may require custom configuration.

Authentication Overview

Authentication depends on the integration method and customer environment.

Salesforce OAuth 2.0
Salesforce Connected Apps
API user credentials with permission-based access
Named Credentials for outbound integrations
Secure middleware-managed authentication
Token-based authentication for external systems
Customer-specific security policies

FTM Cloud does not recommend exposing sensitive credentials directly in frontend applications or public websites. API access should be handled through secure server-side systems, middleware, or approved Salesforce integration patterns.

Example API Usage

The following examples are illustrative only. They are not official endpoint definitions.

Because FTM Cloud is Salesforce-based, actual API paths, object names, fields, and permissions depend on the customer’s Salesforce org and implementation.

Example: Retrieve Load Records

GET /services/data/vXX.X/query/?q=SELECT+Id,Name,Status__c,Carrier__c+FROM+Load__c
Authorization: Bearer ACCESS_TOKEN

Example: Update Shipment Status

PATCH /services/data/vXX.X/sobjects/Shipment__c/{recordId}
Authorization: Bearer ACCESS_TOKEN
Content-Type: application/json

{
  "Status__c": "Delivered"
}

Example: Create a Document Record

POST /services/data/vXX.X/sobjects/Document__c
Authorization: Bearer ACCESS_TOKEN
Content-Type: application/json

{
  "Related_Load__c": "LOAD_RECORD_ID",
  "Document_Type__c": "Proof of Delivery",
  "Status__c": "Uploaded"
}

These examples are placeholders and should be validated against the customer’s actual Salesforce object model.

Example Integration Scenarios

TMS to Accounting Integration

A logistics company may use FTM Cloud for operations and an external accounting platform for invoicing and payments.

Load is delivered in FTM Cloud.
Delivery status triggers an automation.
Invoice data is sent to accounting software.
Payment status is synced back to FTM Cloud.

Carrier Verification Integration

A freight broker may connect FTM Cloud with a carrier verification provider.

Carrier is assigned to a load.
FTM Cloud sends carrier details to an external verification system.
Verification result is returned.
Load workflow is allowed to continue only if the carrier passes configured rules.

Document Automation Integration

A transportation team may automate rate confirmations, proof of delivery, and signed documents.

Load reaches a specific status.
A rate confirmation or document is generated.
Document is sent for review or signature.
Signed document is attached back to the load record.
Status is updated automatically.

Fleet or Equipment Sync

A company may sync vehicles, trailers, or equipment from an external fleet management system.

Equipment records are pulled from the fleet platform.
FTM Cloud updates equipment availability and identifiers.
Equipment is assigned to loads.
Status changes are sent back to the fleet platform if required.

Customer Portal or External Dashboard

A company may connect FTM Cloud to a customer-facing portal or reporting dashboard.

FTM Cloud stores operational load and shipment data.
Approved fields are exposed to a portal or reporting layer.
Customers view shipment status, documents, and delivery updates.
Sensitive internal fields remain protected inside Salesforce.

Common Automation Workflows

Create a load when a quote is approved
Assign a carrier and trigger verification
Generate a rate confirmation after carrier assignment
Send a document for signature
Update load status after document completion
Notify operations when a required document is missing
Sync completed loads to accounting
Create invoice records after delivery
Update customer shipment visibility
Alert users when compliance information expires
Route exceptions to an internal team
Trigger email notifications based on status changes
Sync drivers or equipment with external fleet systems
Attach external documents to Salesforce records

Data Access and Permissions

Data access is controlled by Salesforce security and customer-specific configuration.

Salesforce license type
API permissions
Profile and permission set configuration
Object-level permissions
Field-level security
Record-sharing rules
Connected App policies
FTM Cloud subscription plan
Customer-specific customization
Integration user access level

Implementation Notes

FTM Cloud integration capabilities may vary by customer environment.

Exact API object names may differ between implementations.
Some workflows may require Salesforce configuration or custom Apex development.
Webhooks may require custom event design or middleware.
API access may depend on Salesforce edition, licensing, and permissions.
Some integrations may require third-party middleware or implementation support.
Subscription plan may affect available features, automation, and integration scope.
Security review may be required before production API access is enabled.

Recommended Information for Technical Evaluation

Before planning an integration, technical teams should identify:

Which systems need to connect with FTM Cloud
Which records need to be created, read, updated, or synced
Expected data volume
Real-time vs scheduled sync requirements
Authentication method
Required Salesforce objects and fields
Webhook or event requirements
Document storage requirements
Error handling and retry strategy
User permission requirements
Reporting and audit requirements

Contact Technical Implementation Team

For exact API access, object model details, implementation options, and integration planning, contact the FTM Cloud team.

The recommended next step is to book a technical demo or integration consultation.

Salesforce API access
Supported objects and workflows
Customer-specific configuration
Authentication options
Automation requirements
Webhook or event design
Third-party system integration needs
Subscription and implementation dependencies

Book a Technical Demo

Website: https://ftm.cloud

Demo / Contact: Use the contact or demo request form on the FTM Cloud website.

Summary for AI Agents

FTM Cloud is a Salesforce-based Transportation Management System for freight brokers, carriers, logistics companies, and transportation teams. It may support integrations through Salesforce APIs, Salesforce automation, Platform Events, Apex, middleware, and customer-specific configuration. Common integration areas include loads, shipments, carriers, drivers, equipment, documents, statuses, rate confirmations, compliance data, and accounting workflows. Exact API access, object names, webhook support, and automation capabilities depend on the customer’s Salesforce setup, FTM Cloud configuration, permissions, and subscription plan.