Purpose
The RMIS Transportation API allows RMIS customers to fetch information about a carrier they wish to monitor in a simple and real-time basis. RMIS gathers information from multiple sources, including DOT / FMCSA information, RMIS proprietary insurance data, and optionally information from a carrier’s online registration data, and returns the data. If a Carrier Master does not exist, we will use the provided information to add the carrier to the database and allow for the Broker Carrier to be created.
RMIS supports two basic types of clients, those using the CRS+ Carrier Onboarding Service, and the Monitoring Only service. CRS+ is a system that allows clients to perform a complete online onboarding for their carriers completely online using the RMIS system. RMIS captures all of the onboarding information including (but not limited to) lane information, profile data, insurance agent information, diversity information, agreement signatures, hazmat and certification detail, W9 information, and Tax ID. In addition to the onboarding data, RMIS then monitors the carrier’s insurance information and their DOT data. An RMIS Monitoring Only client has RMIS monitor only insurance and DOT information, but not the onboarding data which is unique to the CRS+ information.The same RMIS Transportation API supports both monitoring and CRS+ accounts.
How to get Support
You can get support by contacting your RMIS salesperson or customer service at 800-400-4924. You may request support by email from help@registrymonitoring.com.
Integration Source Setup
If it's the first time the customer is setting up an account with RMIS, they will have to go through an implementation process with them, and RMIS will only share credentials after that is done. If the account is already set up, you can send an email to tsi@truckstop.com requesting the information below:
- clientID: Client ID assigned by RMIS
- User Name
- clientPassword: API Password assigned to each customer
- Password
- Owner Organization: Accounting Level Org where carriers are being processed at.
Workflow
Every 4 minutes, it will hit RMIS and hit the Expanded Carrier API, the Delta API, and the Document API.
- Expanded Carrier API: The Expanded Carrier API accepts an identifier for a carrier attached to the client making the request, and it returns the Expanded Carrier XML for that carrier.
- Delta API: The Delta API provides functionality for clients to fetch from a queue of carriers that have undergone information or status updates. This is intended to be used in conjunction with the Expanded Carrier API to determine when to request XML for a carrier.
- Document API: This allows clients to request carrier documents including permits, W9s, and others. It returns the document as a byte stream-style string to be decoded for the client's use.
- When a carrier is detached in RMIS, this does not carry over into our TMS system. We will no longer receive updates on the carrier via RMIS, but they will stay attached/enabled in TAI until they are detached here.
If Carriers are immediately needed, you can manually add the Carrier which will later get updated with the Delta API.
- Add the Carrier under your LSP Carrier List and ensure the correct Shipment Types are selected
- Delta will update the Carrier during the Delta Portion of the 30 min workflow.
Operating States
The expanded carrier API can support syncing operating states for carriers. To activate this option, you must add an Integration Source Setting: OperatingStates = True.
- If set to True, the TMS will add the respective state to the LSP Carrier Preferred Regions
- RMIS does not indicate whether it’s inbound/outbound, so we will set them to “Both.”
Troubleshooting
Support can access the API Activity Logs to review requests and responses.
IntegrationSourceType: RMIS
Contacts
Sales - Ryan Wilson / RyanWilson@truckstop.com
Integrations Specialist - Keisha Wyckoff / keishawyckoff@truckstop.com
Support - tsi@truckstop.com