GO PAPERLESS IN 2024: 90 days for $90 on new accounts. 15 users included!

Tasks and Push V2 APIs Now Generally Available

After successful trials with selected customers, a new Tasks and Push API is now generally available live on the platform.
If you’d like to see these in action, simply take a look at our API Explorer 🙂

Tasks V2
We’ve upgraded our Tasks API to include new options such as uploading file attachments onto Tasks, as well as providing a new way of pre-setting Form entry answers on Form activities.

Previously you needed to provide your preset answers in a hierarchical (tree) format, with your answer layout matching exactly with the Form design in terms of nesting fields with Page answers.
This tree based option is still supported in Tasks version 2, however now you can also use a much simpler, field:value “flat” approach.
Say you need to preset the answer in a Form field named “MyField1”, you now have two ways to do it:
Option 1: Use the same tree based approach as you would with Tasks v1:

  "Name": "MyPage",
  "Answers": [{
    "Name": "MyField1",
    "Value": "Some value"

Option 2: Use our new “flat” field:value approach:

  "Name": "MyField1",
  "Value": "Some value"

Our “flat” option also supports repeatable fields – simply specify the same field name multiple times, and the platform will ensure the Form entry is pre-populated with as many repeats as the maximum occurrence of the repeated field names.

In addition to a simpler preset Form answers approach, you can also upload file attachments onto your Tasks via the new task/files endpoint on the Task v2 API.
This provides a super simple way to automate the addition of files to your Tasks.


New Push API

We’ve also now taken the wraps off our Push API, which allows you to send ad-hoc push notifications to your app users.
The API is very simple and allows you to very quickly get up and running with integrated notifications that you can push out from other systems directly to target users.

At the moment we are running this API with no limits aside from our existing acceptable use of 2,500 incoming API calls a day.  Our plan is to monitor usage on Pushes in particular and we’ll decide on a final position regarding acceptable use of Push in the next couple of months.


With today’s update we’ve filled two important gaps in our generally available APIs.
We encourage the developer types among you to give these new APIs a whirl and let us know what you think!