MercuryGate vs Descartes: Carrier API Access Compared

If you're an integration engineer evaluating MercuryGate vs Descartes API access for a European freight build, the honest answer is that you're comparing two different things. One vendor has no public developer API of its own. The other runs a documented REST portal with a live base URL you can hit today. That's not a minor DX footnote, it changes who you file a support ticket with when something breaks in production.

Why "carrier connectivity" means something different at each vendor

Most comparison pages (G2, Gartner Peer Insights, the usual RFP scorecards) rank MercuryGate and Descartes on UI polish, implementation reviews, and pricing tiers. None of them answer the question an integration team actually needs answered: whose endpoint do I end up coding against, and whose changelog do I need to watch? That's the gap this post fills, scoped specifically to teams building direct carrier connectivity for European freight, not parcel.

Criteria and why they matter for integration teams

Before the table, here's what we checked and why each item matters to someone who has to actually build and maintain the connection, not just demo it:

• Public developer portal / self-serve docs — can you read the API spec and get a sandbox key without booking a sales call first?
• Native carrier API vs. partner-routed connectivity — who owns the endpoint you call: the TMS vendor, or a third party they've bolted on?
• Protocol support — REST, SOAP, EDI, webhooks. This determines whether your existing tooling works out of the box.
• Visibility/tracking API specifics — auth method and payload format, because this is where most integration hours actually go.
• Sandbox/test environment availability — can you test before a contract is signed?
• Published pricing — is there a number anywhere, or do you need to get on a call?
• European carrier network depth — does the connectivity layer actually reach the LTL and groupage carriers you need in the EU?

These matter because the real cost of an integration isn't the API call itself, it's finding the docs, getting a working sandbox, and knowing who owns the bug when a partner API changes its schema without warning. That last one is the sleeper cost nobody puts in the RFP.

The comparison table

What "MercuryGate's API" actually is — a partner stack, not an endpoint

Dig past the marketing copy and MercuryGate's carrier connectivity is a federation of other companies' APIs stitched into the TMS UI. Banyan Technology supplies the LTL layer: MercuryGate has integrated Banyan's LIVE Connect™ API solution into its existing TMS to include comprehensive carrier options for its customers, saving them both time and money, a partnership that goes back to a 2021 extension announcement. SMC3 layers on top for rating: when MercuryGate customers combine direct-to-carrier APIs with industrial-strength, analytical APIs like RateWare® XL and CarrierConnect® XL, the SMC³ Platform delivers a range of unequaled API solutions that give users an array of options to address their specific LTL needs, per SMC3's own 2017 press release naming MercuryGate as launch partner.

Then there's LoadTap for app-less truckload tracking, where any company that has its own TMS can integrate with Loadtap through standard REST APIs, and Convoy, whose 2022 expansion gave MercuryGate customers API integrations that give MercuryGate's customers access to Convoy's nationwide carrier network. That's four separate API contracts, four separate rate limits, four separate places a breaking change can originate, all surfaced through one TMS login. Your integration team ends up debugging Banyan's error codes on a Tuesday and SMC3's on a Thursday, while MercuryGate support tells you to open a ticket with the partner. If you're building for European freight specifically, this matters even more: Banyan, SMC3, and Convoy are North American-first networks, and nothing in MercuryGate's own materials documents equivalent EU carrier depth.

What Descartes' API surface looks like in practice

Descartes gives you something concrete to test before you sign anything: a public portal and a documented tracking API for MacroPoint, with Base URL https://macropoint-lite.com/api/1.0/, Authentication: Basic, Content Type: application/xml, Response Format: XML. Read that again. Basic Auth and XML in 2026 is not what a REST-first shop wants to see, and it shows in independent grading: one API scorecard site puts MacroPoint at an F, noting that provisioning is not self-serve: an activations consultant issues credentials, meaning the docs are open but the keys still route through a human.

Zoom out from MacroPoint and Descartes' broader pitch is network reach, not raw API elegance: shippers can communicate across API, EDI and web portals/apps with universal standards via the Global Logistics Network, which also underlies Descartes' Aljex TMS integrations. For a European freight team, that breadth matters more than the auth scheme, provided you're prepared for an onboarding call before your first token works.

Sample checks — what an integrator can verify today

• Can you read the API spec without a sales call? Descartes: yes, docs are public at docs.macropoint.com. MercuryGate: no, per the SoftwareWorld listing stating plainly it does not offer an API.
• Is there a published base URL and auth scheme? Descartes MacroPoint: yes, Basic Auth over HTTPS with XML payloads. MercuryGate: no, only inherited from whichever partner (Banyan, SMC3, LoadTap, Convoy) handles that workflow.
• Can you get a working key without human intervention? Neither, fully. Descartes still requires an activations consultant to issue credentials even with public docs in hand.

This is also the part of the market where lighter-weight multi-carrier layers show up as an alternative to building against either vendor's stack directly. Platforms like Cargoson sit in the same space as project44, FourKites, and Banyan conceptually, offering a single documented API surface for shippers who'd rather not maintain four separate partner contracts to get carrier connectivity working.

Verdict, scoped

For a European freight integration team that needs to build and test something themselves, without a sales cycle gating step one, Descartes wins. You get a public portal and a real base URL to point a curl request at, even though Basic Auth and XML payloads are behind current REST norms and credential issuance still needs a human. MercuryGate is the right fit only if you're already committed to Banyan, SMC3, or project44 for carrier connectivity and specifically want those wired into MercuryGate's TMS execution screens. In that case, you're not evaluating MercuryGate's API at all, you're evaluating your partner's, and your due diligence should target Banyan's or SMC3's docs and support SLAs directly, not MercuryGate's.

Neither vendor publishes rate limits or uptime SLAs, so any latency or throughput claims from either side remain unverified from public sources. That's worth a dedicated benchmark run against the MacroPoint sandbox and whichever MercuryGate partner API you can get provisioned, logged against a real test rig rather than vendor copy.