Skip to main content

Migrating from Deprecated CDS Endpoints

Several single-purpose CDS endpoints have been deprecated in favor of the unified Post Listing endpoint with query filters.

Posts by Category

Posts by Tag

Posts by Author

Latest Posts by Type

Homepage

Post by Slug

Benefits of Migration

The new /posts/ endpoint provides:
  • Advanced filtering with operators (__eq, __contains, __in, __gte, __lte)
  • Sorting with sort_by and sort_order parameters
  • Combined filters for complex queries
  • Consistent pagination across all queries
  • Cache-Tags for CDN integration

Migration Checklist

  • Identify all deprecated endpoint calls in your codebase
  • Replace each with the equivalent /posts/ query
  • Test that response data matches expected format
  • Update any response parsing (field names are consistent)
  • Monitor for deprecation warnings in API responses

Content Migration Strategies

Backdated Publishing

When migrating historical content from legacy systems, you must preserve the original publication dates instead of using the time of import. You can accomplish this by directly updating the post with the custom_published_at property:
curl -X PATCH \
  'https://cms.thepublive.com/publisher/<PUBLISHER_ID>/post/<POST_ID>/' \
  -H 'Authorization: Basic <BASE64_AUTH_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{
    "status": "Published",
    "custom_published_at": "2025-12-15T10:00:00Z"
  }'
Last modified on April 17, 2026