Here at Onfleet, we're proud of the last-mile logistics software that we've built. We have the most sophisticated API on the market, utilize our own machine learning algorithms, offer incredibly powerful routing engines and make all of this work in 90+ countries around the world.
While we offer all of these tools out-of-the-box, we realize not all engineers have the time or the tools to get up to speed with our advanced system. In an effort to help our developer community, we've created powerful API wrappers to lower that barrier to entry. But first, let's have a quick 101 to explain why these API wrappers can be incredibly useful.
What is an API wrapper?
In layman's terms, API wrappers provide a condensed key to a complicated treasure map. Making requests directly to an API can be more complicated than some engineers are ready for. Enter API wrappers, which provide specific guidelines for performing actions without as much technical jargon.
Getting a bit more technical, API wrappers are language-specific packages that wrap sets of API calls into easy-to-use functions. The wrapper offers multiple API calls without the interaction of the user while also lowering engineering efforts to automate. Additionally, we standardize all requests made through the API wrapper which can provide more standardized transparency.
As a conclusion to our 101: API wrappers make it easier for engineers to build new applications by allowing them to focus on the build processes rather than learning new jargon.
Why should you use the Onfleet API wrappers?
- Simplifies work for developers that are building apps that utilizes the Onfleet API.
- Standardize API requests made to the Onfleet API, less trial and error when playing around with our API endpoints.
- Minimize efforts on developer support.
- Keep up-to-date with Onfleet engineering efforts with new feature releases and a continuous growing API.
What key features do our wrappers provide?
- A wrapper that makes it easier to interact with the Onfleet API without having to write too much code.
- Easy to show the full capabilities of integrating with the Onfleet API.
- Supports multiple popular languages.
- Supports all functionalities of the Onfleet API.
- Track and refrain users from abusing or misusing the Onfleet API.
What makes our API wrappers useful?
- Fully supported by Onfleet's Support team, with identifiers and customized error messages to facilitate troubleshooting.
- Easy to install, hosted on open-source and common library repositories.
- Lightweight and fast, very few dependencies.
- Easy to reconfigure and add/drop API features for change management.
- Fully tested by Onfleet Support.
- Support new technologies (i.e. ES2015 Promises & ES2017 Async/Await, etc...)
- Idiomatic consistency, smells like what it's written in.
What's an example of your API wrapper in action?
As we stated above, API wrappers can save time and allow engineers to focus on building the applications they have set out to build. As an example, take a look at a side by side comparison of the same request made via standard HTTP request and via the Onfleet wrapper:
List of our current API wrappers
Now that we're up to speed, it's our pleasure to present the newly released Onfleet API Wrappers for public consumption (updated as we release more):
We wish you luck and are always happy to answer any of your integration questions, firstname.lastname@example.org