Tasks API

Increase user engagement with your tasks by including them in the Tasks tab of Fourth Engage.


Hourglass icon

Accelerate interactions

Whether it's onboarding, ordering, or organizational, get employee onto your tasks faster.

Hand with plant icon

Grow together

Increase the partnership with your customers by being part of a unified presence in Fourth Engage.

Address card icon

Simplify your contacts

Send task notifications and reminders without needing user email addresses.

What is it?

Fourth arrow

The Tasks API is intended for partners with a connected app in Fourth Engage, to complement and expand the user experience. It enables you to add tasks for your connected app into the Tasks tab of Engage, so that they show alongside tasks from the Fourth Platform.

Once integrated, you can add, update, or delete tasks as required; update the status for a task; and create expiry and cut-off times. And you can do this all without knowing the users' email address or phone number, as users are identified through their Fourth ID.

To further engage with users while adding or updating tasks, you can include push notifications as part of the API request.

Why use it?

Any service that needs users to respond to events in a timely manner will benefit from using this API. For example, you can make sure users:

  • Complete training
  • Confirm purchase orders
  • Fill-in employee surveys

Incorporating your tasks into Fourth Engage improves both the timeliness and overall responses by users. The number and frequency of reminders sent through other channels drops — as millennial workers are more responsive to notifications on apps than to emails. And including your tasks in the Tasks tab further unifies the experience between Engage and your connected app, which in turn can help cement the partnership with your customers.

Developer typing

Getting Started

  1. Get in touch

    Contact Fourth and talk to one of our experienced Implementation Consultants.

  2. Develop and test

    We'll provide you with a set of credentials to access the API and a test environment against which you can develop your application.

  3. Go live!

    Transition from the test environment to live!