Migration Guides

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

Show Before / After

# Before (deprecated)
GET /posts_by_category/100/

# After
GET /posts/?categories.id__eq=100

Posts by Tag

Show Before / After

# Before (deprecated)
GET /posts_by_tag/500/

# After
GET /posts/?tags.id__eq=500

Posts by Author

Show Before / After

# Before (deprecated)
GET /posts_by_author/1/

# After
GET /posts/?contributors.id__eq=1

Latest Posts by Type

Show Before / After

# Before (deprecated)
GET /latest-posts/Article/

# After
GET /posts/?type__eq=Article&sort_by=created_at&sort_order=desc

Homepage

Show Before / After

# Before (deprecated)
GET /homepage/

# After
GET /posts/?limit=20&sort_by=created_at&sort_order=desc

Search

Show Before / After

# Before (deprecated)
GET /search/?q=budget

# After
GET /posts/?title__contains=budget

Post by Slug

Show Before / After

# Before (deprecated)
GET /posts_by_slug/my-article-slug/

# After
GET /post/my-article-slug/

Show Before / After

# Before (deprecated)
GET /related-posts/12345/

# After (filter by same primary category)
GET /posts/?primary_category.id__eq=100&limit=5

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"
  }'

Overview

Content Delivery API

Content Management API

SDKs

Reference

Deprecated

Migrating from Deprecated CDS Endpoints

Posts by Category

Posts by Tag

Posts by Author

Latest Posts by Type

Homepage

Search

Post by Slug

Benefits of Migration

Migration Checklist

Content Migration Strategies

Backdated Publishing

​Migrating from Deprecated CDS Endpoints

​Posts by Category

​Posts by Tag

​Posts by Author

​Latest Posts by Type

​Homepage

​Search

​Post by Slug

​Related Posts

​Benefits of Migration

​Migration Checklist

​Content Migration Strategies

​Backdated Publishing

Migrating from Deprecated CDS Endpoints

Posts by Category

Posts by Tag

Posts by Author

Latest Posts by Type

Homepage

Search

Post by Slug

Related Posts

Benefits of Migration

Migration Checklist

Content Migration Strategies

Backdated Publishing