Logixboard's integration with Banyan supports all features outlined in the Trucking Visibility product article except Live Tracking.
The integration is facilitated via Banyan's Standard Export Service
webhooks and v3 APIs, providing near-real-time updates within Logixboard. Visit the Banyan Mapping Guide for more information on which fields are leveraged to drive the product experience.
FAQ:
Q: How does the integration work?
A: Logixboard integrates with Banyan through Banyan's native v3 APIs. Data is synced any time a status update is received via Banyan's Standard Export Service webhooks, so Logixboard remains up to date with key data from Banyan.
Q: Will the integration lead to additional fees from Banyan?
A: No. Our integration uses Banyan's public APIs and additional fees are not anticipated.
Q: How long will it take to configure the integration and what do I need to do?
A: The limiting factor is API key creation, which is needed to configure appropriate API communications. Once the LXB team has your Banyan API key, setup can be completed in just a day or two.
Q: What data is pulled from Banyan?
A: Please see our public mapping guide.
Q: I’m using an external data feed (e.g., MacroPoint, TruckerTools, direct carrier integrations) to update Loads in Banyan - will Logixboard pull in those updates?
A: Yes! As long as the data is covered in the mapping guide (linked above), external data feeds will also update LXB. This includes live tracking data and carrier milestones.
Q: Can LXB backfill data?
A: Yes! Logixboard can backfill load data by date range or using a simple CSV report generated from Banyan.
Q: Can the LXB Trucking experience include data from both CW1 and Banyan?
A: Yes! Dual data feeds are supported and data from both integrations can be used to populate the Trucking experience. Please keep in mind that the data / features supported by each integration will vary, and so the experience may be different for loads from CW1 versus those from Banyan.
Q: Can I use LXB for Banyan only (i.e., no international TMS integration?)
A: Not at this time, though we’d love to discuss this further!