> For the complete documentation index, see [llms.txt](https://motorweb.gitbook.io/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://motorweb.gitbook.io/product-documentation/our-au-products/builder-api.md).

# Builder API

## Data Your Way

How MotorWeb gets data to its clients is just as important as what data we supply.

MotorWeb recognises that customers require diverse data access methods. Our multi-option data delivery strategy includes:

* Data Packs
* Single APIs
* Portal Reports
* Bulk Data
* Bespoke

Expanding on this is our Builder API which enables you to define your own API.

This will build off our data pack work and will allow you to get the data you need for your specific use case without needing MotorWeb to build anything.

Often businesses looking for vehicle data are confronted with the need to conform to large pre-defined APIs.  Additionally businesses find that they need to utilise multiple large APIs to get the data they want.

That's not sustainable and is something we're going to fix.

As Australia's vehicle data aggregator, our builder API will allow you to pick small building blocks off the shelf and build them into an API of your design.  No need to wait for a bespoke API, no need to pay for API bloat.

## So how does this work?

At the core of this new service is the builder API.  This provides a basic set of NEVDIS data and forms the foundations of the API you're building.

Next you select the building blocks you want, for your use case, from our pre-defined (and growing)  list.  Just specify these in the body of the API.  Boom!  You've got yourself your own API.

Let's look at a scenario for a vehicle you're interested in:

> You need to view the specifications of the vehicle and really understand when it was built?
>
> * `Builder API + specs building block + build date`
>
> OK, it's a car you're interested in, but does it have a dodgy past?
>
> * `Builder API + NEVDIS WoVR + NEVDIS Stolen`
>
> The car is clean, but it's a Land Rover Defender and will likely have factory fitted options that will impact the value of the vehicle.  Does it have options?
>
> * `Builder API + factory options flag`
>
> No options fitted, so what's the vehicle worth?
>
> * `Builder API + market valuation`

What does this show?  You've got four APIs in one and you're getting only the incremental data you need based on your specific use case.  No API bloat.

We're building this functionality now and will be adding more and more small building blocks over time - so watch this space.