Pagination

Paginated list endpoints use 1-based page numbers (page) and a page size (limit), and return totals so you know when to stop. Smaller collections return everything in a single { "data": [...] } envelope.

Posts — GET /v0/posts

{
  "posts": [ /* ... */ ],
  "page": 1,
  "totalPages": 4,
  "total": 87
}

# First page
curl "https://api.schedulin.app/v0/posts?limit=25&page=1" \
  -H "x-api-key: $SCHEDULIN_API_KEY"

# Next page — increment `page` until it reaches `totalPages`
curl "https://api.schedulin.app/v0/posts?limit=25&page=2" \
  -H "x-api-key: $SCHEDULIN_API_KEY"

Combine pagination with filters like status, socialAccountIds, and tagIds to narrow results.

Media — GET /v0/media

Media is returned most recently updated first, under items:

{
  "items": [ /* ... */ ],
  "page": 1,
  "total": 42,
  "totalPages": 5
}

curl "https://api.schedulin.app/v0/media?page=2&limit=20&q=launch" \
  -H "x-api-key: $SCHEDULIN_API_KEY"

Webhook deliveries — GET /v0/webhooks/{id}/deliveries

Accepts page (default 1) and limit (default 25, max 100) and returns the page under data, newest first.

Unpaginated lists

These endpoints return the full collection wrapped in a data array, with no page or total fields:

{
  "data": [ /* ... */ ]
}