---
title: "List Follow Ups"
method: GET
path: "/v2/follow-ups"
tags: ["external", "external-v2"]
---

# List Follow Ups

`GET /v2/follow-ups`

## Request

- Base URL: `https://api.mem.ai`
- URL: `https://api.mem.ai/v2/follow-ups`
- Auth: HTTP bearer

List follow-ups for the authenticated caller's assistant with cursor pagination.
Results are ordered by `order_by` and return `next_page` when additional rows are available.
Use the optional `status`, `task_id`, and `project_id` filters to narrow the result set.

## Query parameters

- `limit` integer, nullable: Maximum number of follow-ups in this page. Default is 50; valid range is 1 to 100.
- `page` string, nullable: Opaque cursor from a previous list response. Omit for the first page. IMPORTANT: Reuse with the same `order_by`, `status`, `task_id`, and `project_id` values.
- `order_by` 'created_at' | 'updated_at' | 'scheduled_for' | 'created_at_asc' | 'updated_at_asc' | 'scheduled_for_asc': Sort key for pagination boundaries. Use `scheduled_for` (default) for latest-scheduled-first follow-up feeds, `scheduled_for_asc` for soonest-scheduled-first pending sweeps, `updated_at` or `updated_at_asc` for recency/staleness feeds, and `created_at` or `created_at_asc` for creation-order views.
- `status` 'pending' | 'fired' | 'completed' | 'canceled'
- `task_id` string, uuid, nullable: Optional filter to follow-ups associated with a single task.
- `project_id` string, uuid, nullable: Optional filter to follow-ups associated with a single project.

## Response `200`

OK

- FollowUpListResponseSchema
  - `next_page` string, nullable: Opaque cursor for the next page of follow-up results. `null` when there are no more results.
  - `request_id` string, required: Identifier for this API request. Useful for tracing and support.
  - `results` FollowUpResponseItemSchema[], required: Page of follow-up results matching the requested filters and sort.
    - `commitment_kind` string, nullable, required: Commitment kind, if set (`due` or `deadline`).
    - `completed_at` string, date-time, nullable, required: Timestamp when the follow-up was marked completed, if any.
    - `content` string, required: Current content/description of the follow-up.
    - `created_at` string, date-time, required: Creation timestamp for the follow-up in ISO 8601 format.
    - `deadline_at` string, date-time, nullable, required: Hard deadline, if any.
    - `due_at` string, date-time, nullable, required: Soft due date, if any.
    - `fired_at` string, date-time, nullable, required: Timestamp when the follow-up fired, if it has fired.
    - `id` string, uuid, required: UUID of the follow-up.
    - `project_id` string, uuid, nullable, required: Parent project UUID, if any.
    - `scheduled_for` string, date-time, required: When the follow-up is scheduled to fire.
    - `source_context_id` string, uuid, nullable, required: Identifier linking this follow-up to the agent run that created it, when applicable.
    - `status` string, required: Current follow-up status (`pending`, `fired`, `completed`, or `canceled`).
    - `task_id` string, uuid, nullable, required: Parent task UUID, if any.
    - `trigger_not_after` string, date-time, nullable, required: Latest trigger time (for `time_window` triggers).
    - `trigger_not_before` string, date-time, nullable, required: Earliest trigger time (for `time_window` triggers).
    - `trigger_type` string, nullable, required: Trigger type for the follow-up, if set.
    - `updated_at` string, date-time, required: Last modification timestamp for the follow-up in ISO 8601 format.
  - `total` integer, required: Total number of matching follow-ups before pagination is applied.

## Changes

- **2026-11-03** `503bb357d07c`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/mem/apis/mem-public-client-api/changes/v2/follow-ups/get.md)

---

[API](https://skmtc.dev/mem/apis/mem-public-client-api.md) - [All operations](https://skmtc.dev/mem/apis/mem-public-client-api/llms.txt) - [OpenAPI document](https://skmtc.dev/mem/apis/mem-public-client-api/revisions/503bb357d07c?raw)