The API Report CardAPI Index
FarEye

FarEye API

Enterprise last-mile delivery management & logistics orchestration SaaS · fareye.com

FarEye has a REST API behind a thin developer portal at developer.fareyeconnect.com, with the OpenAPI spec gated behind a download. Keys are provisioned by the integration team rather than self-serve, auth is API-key only, and rate limits are set per contract.

Last verified: July 2026Logistics & Supply Chain
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistencePOORA REST API exists, but the public portal is a single thin page with the OpenAPI spec gated behind a download.
AccessPOORKeys come from FarEye's integration team at integration@fareye.com; there is no self-serve provisioning.
CoverageGOODDocumented APIs span rate shopping, labels, tracking with webhooks, cancellation, EDD, returns, and order creation.
AuthPOORStatic API keys shared as a private key per customer; no OAuth 2.0 flow for third-party app builders.
Docs & DXPOORPortal has no auth, rate limit, or versioning pages; the OpenAPI spec is gated behind a download and there are no SDKs.
StabilityMIXEDRate limits are unpublished and set per enterprise contract; reviews say new integrations take time to stabilize.
MORE FROM THE REPORT CARD
Supergood: FarEye has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

FarEye scores D+ on the API Report Card. FarEye has a REST API behind a thin developer portal at developer.fareyeconnect.com, with the OpenAPI spec gated behind a download. Keys are provisioned by the integration team rather than self-serve, auth is API-key only, and rate limits are set per contract.

Tried to integrate with FarEye?
SOURCES
Developer portal is thin, no public pages for authentication, rate limiting, versioning, or SDKs; OpenAPI spec is gated behind a download developer.fareyeconnect.com
API access is **gated through the FarEye integration team** (integration@fareye.com) rather than self-serve dashboard provisioning of keys developer.fareyeconnect.com
**No first-party SDKs** (Node/Python/Java/Go/Ruby), integrators must hand-roll HTTP clients against the OpenAPI spec developer.fareyeconnect.com
Auth is **API-key based**, with no OAuth 2.0 / SSO flow for third-party app builders helpcenter.gomotive.com
Rate limits are **not publicly published**, they are set per enterprise contract, making capacity planning for integrators opaque developer.fareyeconnect.com
Integration failures with customer systems are reported in user reviews; new integrations "take time to stabilize" capterra.com
ClickPost and other third-party aggregators position themselves as the recommended way to integrate with FarEye, implying friction in direct integration clickpost.ai
No GraphQL surface, all integrations are REST + webhook developer.fareyeconnect.com
Platform performance degrades at high data volumes, "FarEye can be slower at times because of its large scale" and server errors are reported under load g2.com
Tech support response "is not up to the mark"; less personalized than during implementation g2.com
Implementation timelines are long and technically complex, typical of enterprise logistics RFPs; significant learning curve for new teams locus.sh
Core search/lookup functionality is limited (e.g., no phone-number search criteria) capterra.com
Routing engine quality varies by geography (UAE specifically called out for poor results) capterra.com
Some workflows require manual intervention and not all parameters (speed changes, transaction pages) are configurable capterra.com
New requirements take a long time to stabilize after rollout; slow to adapt to evolving customer needs capterra.com
No publicly disclosed pricing, every deal is custom enterprise sales, slowing evaluation cycles locus.sh
Integration failures with customer software occasionally reported capterra.com