Skip to main content
GET
/
v2
/
tasks
List tasks
curl --request GET \
  --url https://api.zenzap.co/v2/tasks \
  --header 'Authorization: Bearer <token>' \
  --header 'X-Signature: <api-key>'
{
  "tasks": [
    {
      "id": "880e8400-e29b-41d4-a716-446655440003",
      "topicId": "550e8400-e29b-41d4-a716-446655440000",
      "title": "Review documentation",
      "description": "Review and update all API documentation",
      "status": "Open",
      "assignee": "550e8400-e29b-41d4-a716-446655440001",
      "dueDate": 1699564800000,
      "isDueDateTimeSelected": false,
      "index": 1000000,
      "createdAt": 1699564800000,
      "updatedAt": 1699564801000
    }
  ],
  "nextCursor": "<string>",
  "hasMore": true
}

Authorizations

​
Authorization
string
header
required

Bearer token for the request. Two flavors:

  • Static API key — pass your API key (the value returned as apiKey when the bot was created). Must be paired with X-Signature + X-Timestamp (the hmacSignature scheme).
  • OAuth access token — pass the JWT returned by POST /oauth/token. No signature headers are required.
​
X-Signature
string
header
required

HMAC-SHA256 signature for request verification. Required only when authenticating with a static API key. Omit when using an OAuth access token.

Headers

​
X-Signature
string

HMAC signature of the request for authentication and replay protection.

Required only when authenticating with a static API key. If you are using an OAuth access token (issued by POST /oauth/token), omit this header — the JWT carries all the authentication and integrity guarantees.

Replay Protection: The signature includes a timestamp to prevent replay attacks. Requests with timestamps older than 5 minutes are rejected.

The signature payload differs by HTTP method:

  • POST/PUT/PATCH/DELETE: HMAC-SHA256 of {timestamp}.{body}
  • GET: HMAC-SHA256 of {timestamp}.{uri}

The signature is calculated as:

  1. Get the current Unix timestamp in milliseconds
  2. Determine the payload:
    • For POST/PUT/PATCH/DELETE: Use {timestamp}.{body} where body is the request body
    • For GET: Use {timestamp}.{uri} where uri is the full request URI (e.g., /v2/members?limit=10)
  3. Calculate HMAC-SHA256 of the combined payload using your API secret
  4. Hex-encode the output
  5. Include the timestamp in the X-Timestamp header

Example for GET request to /v2/members?limit=10:

timestamp = 1699564800000
payload = "1699564800000./v2/members?limit=10"
signature = HMAC-SHA256(secret, payload)
X-Signature: hex(signature)
X-Timestamp: 1699564800000

Example for POST request with body {"topicId":"123","text":"Hello"}:

timestamp = 1699564800000
payload = '1699564800000.{"topicId":"123","text":"Hello"}'
signature = HMAC-SHA256(secret, payload)
X-Signature: hex(signature)
X-Timestamp: 1699564800000

For multipart/form-data requests, sign the exact raw request body bytes (including boundaries and file bytes) as transmitted.

Pattern: ^[a-f0-9]{64}$
Example:

"a3d5f8e7c2b1d4f6a8e9c7b5d3f1a2e4b6c8d0f2e4a6b8c0d2e4f6a8b0c2d4e6"

​
X-Timestamp
integer<int64>

Unix timestamp in milliseconds when the request was created. Used for replay protection — requests older than 5 minutes are rejected.

Required only when authenticating with a static API key. Omit when using an OAuth access token.

Example:

1699564800000

Query Parameters

​
topicId
string<uuid>

Filter tasks by topic ID

​
status
enum<string>

Filter by task status

Available options:
Open,
Done
​
assignee
string

Filter by assignee profile ID (empty value filters unassigned tasks)

​
limit
integer
default:50

Maximum tasks to return (default 50, max 100)

Required range: 1 <= x <= 100
​
cursor
string

Opaque cursor from a previous nextCursor value.

Response

Tasks retrieved successfully

​
tasks
object[]

Tasks matching the provided filters

​
nextCursor
string

Cursor for the next page. Omitted when there are no more results.

​
hasMore
boolean

Whether there are more tasks available.