Overview

As Trimble markets API products as part of its Connect & Scale strategy, its customers expect a unified experience of its APIs. To provide a world-class developer experience, Trimble’s APIs must follow a consistent standard. This document represents Trimble’s API standard governing all published HTTP APIs.

The Trimble API Standard is a living standard with named releases. If there is an API design element that is not covered here, you have proposed changes or additions, or need to diverge from the standard, please start a Github Discussion.

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

For more information on the goals behind the API Standard, please see Philosophy behind the Trimble API Standard in the Appendix.