MCP: API Demo
Security Token: https://api.mycarrierpackets.com/token (Post call/grant_type: password)
Requires customer integration username and password. Admin can manage credentials by going to:
https://mycarrierpackets.com/IntegrationTools
Postman can be used for testing.
Response Format: By default, the response format from the apis will be JSON. To receive the api response in XML format, add an "Accept" header with the value "text/xml" to the request.
1.
intellivite invite the carriers to complete packets either by:
1.1
RECOMMENDED: Create an invite screen in the TMS that allows users to enter a carrier DOT and the carrier’s email (preload intellivite approved carrier email addresses and other data with the preview API 1.1.2.1 below) to call our invite API (Post call/Token required):
1.2
Or add an intellivite link in a TMS generate email example:
Note:
Customers can find the basic intellivite link in the integration tools page available to admins. Users can access their intellivite links under their profile in MyCarrierPackets.
1.3
Or use a URL to MCP to invite the carrier:
2.1
Check for completed carrier packets either by:
2.3
Add a “View Carrier” Button for each carrier profile in the TMS with either URL (to view MyCarrierPacket and/or Assure Advantage data):
3.
Assure Advantage Carrier Monitoring:
3.1
Initial and Periodic Full Carrier Sync
3.1.1
Get Monitored List from MCP:
3.1.2
Compare MCP/TMS carrier lists:
3.1.3
Update Carrier list:
3.3
Request Certificates of Insurance
3.4
Update carrier now button: Pulls carrier data in real-time (section 2.2 above).
3.5
Pull image of Certificate of insurance (see 4.1 below).
3.6.1.1
Body: DOTNumber, DocketNumber, and/or IntrastateNumber
3.6.2.1
Body: DOTNumber, DocketNumber, and/or IntrastateNumber
4.
Pull Carrier Packet and Assure Advantage Images:
4.1.1
If testing in Postman, click Save Response to download.
4.2.1
Requires a user to be logged in.
4.3.2
If testing in Postman, click Save Response to download.
Integration Notes:
1.
When mapping data fields, if a carrier is set to monitor, and no data is sent from The Descartes Systems Group, Inc., the fields should be blank.
2.
When mapping data fields, the fields should be locked not allowing users to type information in unless the carrier is unchecked for monitoring. This way, the system always whose data is being viewed.
3.
Initial sync and periodic update process:
a.
The user should be able to run a report of all carriers monitored within the TMS.
b.
Customers can upload their list of monitored carriers in the Upload page of MyCarrierPackets.
c.
The TMS should clear all mapped monitoring fields in the TMS, and pull an update on all carriers using the GetCarrierData API in section 2.2 above.