Skip to main content

Your Implementation Required

These endpoints must be implemented on your server
Enginy creates tasks in your CRM when sequences trigger task actions. Your API must implement the following task endpoints.

Single Task Operations

Create Task

Creates a new task in your CRM.

Request Body

Example Request

Response

Return the created task with at least an id field:
The id field is required in the response. Enginy uses this to track the task.

Get Task

Retrieves a single task by ID.

Path Parameters

Response


Update Task (Complete)

Updates a task, typically to mark it as completed.

Path Parameters

Request Body

Example Request

Response

Return the updated task:

Batch Operations

Enginy uses batch endpoints to minimize API calls and improve performance. Instead of making individual requests for each task, Enginy will batch multiple operations into single requests.

Get Tasks Batch

Retrieves multiple tasks in a single request.

Request Body

Example Request

Response

Return an array of tasks. Tasks that don’t exist should be omitted from the response (don’t return errors for missing tasks).
If a task ID doesn’t exist, simply omit it from the response array rather than returning an error.

Complete Tasks Batch

Marks multiple tasks as completed in a single request.

Request Body

Example Request

Response

Return an array of the updated tasks:

Task Schema Reference


Testing Your Tasks API

Before connecting to Enginy, test your task endpoints:
1

Test Task Creation

2

Test Batch Get Tasks

3

Test Batch Complete Tasks