<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=2075975219360928&amp;ev=PageView&amp;noscript=1">

Blog

Written by vWork
on November 23, 2020

Now more than ever businesses need to deploy software quickly to drive digital transformation projects. And for businesses who are integrating vWork with their other business tools, we’ve just made this a lot quicker (and easier).

Introducing our new templated jobs API

With this API, you can integrate faster and at a lower cost. And your developers will be happier - with less testing, less debugging, and less rework needed than other APIs.

So how low-code is the new API?

Instead of defining the job when you POST it and laying out all the steps and fields in your XML, you now reference a template in vWork and map just a few values.

This means that what could have been over a 1,000 lines in XML in earlier integrations, can now be achieved with just a few lines. Here’s an example:

<job>
<template name>Delivery Job</template name>
<customer_name>John Smith</customer_name>
<cf_notes>Beware of the dog.<cf_notes>
</job>

This example selects a template called “Delivery Job” as well as a customer by name and then supplies some text that needs to be inserted into a custom field called notes.  

The API does everything else. It gets the customer’s address from the database and populates the right step. It supplies the rest of the steps and fields defined in the template. It sets a deadline and job duration based on the template settings. It will use whatever conditional logic is used by the template.

And if your template uses custom labels, hazards, tags, invoice line items, or price book settings, the API sets those up for the job as well.

What happens if my job templates change?

We know that things change – and that job templates change over time. For this reason, we’ve written the API so you can make changes to your templates and the integration will continue to work as before.

The only exception to this is if you change the name of a custom field that your API integration is writing data to. To support this, it would be a simple update to your integration to use the new field name.

Say goodbye to hours of rework for something that is now straightforward and even more flexible.

Will this low-code API impact my current jobs API?

All existing APIs continue to work as well as they always have as all of the current API routes are staying the same. So everything in production today will work as well as it did when you set it up.

Our new low-code API gives you an additional option – and it ramps up the speed of implementation, which is important to many businesses right now. And from our discussions with our existing customers’ tech teams, we know many of them are pretty excited about this.

More of our low-code API goodness

Using our new templated jobs API, we’ve also built new functionality that allows your customers to email us PDFs of job requests and we’ll automatically create the jobs in vWork. If you’re interested in streamlining job creation this way, get in touch and we’ll share the details.

And right now our Development team is working on a Zapier integration that will connect all your Zaps to vWork and create jobs automatically based on the output of your other software. And even better, we’re supporting JSON as well as XML for this new API!

You may also like:

New Features

vWork launches accurate mileage for job invoicing using EROAD telematics data

We’re excited to announce a new integration between vWork and EROAD, one of Australasia's leading telematics providers s...

New Features

vWork launches first to market three-way communication

Customers are the lifeblood of all businesses. And that’s why are delighted to launch three-way SMS messaging capability...

New Features

No-code processing of 3rd party bulk work orders

Recently we launched our low code API, which allows you to integrate your existing software stack faster with vWork. We’...