Skip to main content

​
List follow-ups

​
page
integer
default:"1"
Page number
​
per_page
integer
default:"25"
Items per page (max 250)
​
sort
string
Sort field
​
order
string
default:"desc"
Sort order: asc or desc
​
contact_id
string
Filter by contact ID
​
deal_id
string
Filter by deal ID
​
status
string
Filter by status: pending or completed
​
type
string
Filter by type: call, email, meeting, or task
​
overdue
boolean
Show only overdue follow-ups
​
due
string
Filter by due date (YYYY-MM-DD)
GET /api/v1/follow-ups
Example
curl "https://api.mosscrm.com/api/v1/follow-ups?status=pending&overdue=true" \
  -H "X-API-Key: moss_k_..."

​
Get a follow-up

GET /api/v1/follow-ups/:id

​
Create a follow-up

POST /api/v1/follow-ups
​
contact_id
string
required
Contact ID (UUID)
​
type
string
required
Type: call, email, meeting, or task
​
deal_id
string
Associated deal ID (UUID)
​
description
string
Description
​
due_date
string
required
Due date (YYYY-MM-DD)
​
status
string
default:"pending"
Status: pending or completed
Example
curl -X POST https://api.mosscrm.com/api/v1/follow-ups \
  -H "X-API-Key: moss_k_..." \
  -H "Content-Type: application/json" \
  -d '{
    "contact_id": "cnt_abc123",
    "type": "call",
    "description": "Follow up on proposal",
    "due_date": "2026-02-15"
  }'

​
Update a follow-up

PATCH /api/v1/follow-ups/:id
​
type
string
Type
​
description
string
Description
​
due_date
string
Due date (YYYY-MM-DD)
​
status
string
Status: pending or completed

​
Delete a follow-up

DELETE /api/v1/follow-ups/:id

​
Complete a follow-up

Mark a follow-up as completed. 
PATCH /api/v1/follow-ups/:id/complete
No request body required. Returns the updated follow-up.

​
Bulk complete

Complete multiple follow-ups at once. 
PATCH /api/v1/follow-ups/bulk-complete
​
followup_ids
string[]
required
Array of follow-up IDs (max 100)