content_series_get

# content_series_get

Find series and read their ordered episode links in article, photobook or resource apps.

Read the [shared content contract](../guides/content-apps.md) for authorization, app identity, result interpretation and recovery.

## Inputs

Require channelCode and pAppCode in B00001/B00005/B00012 or a supported installed alias. view defaults to list with page 1 and limit 15.

- `view.kind:list`: optional query.page, query.limit (1–100), search (up to 200 characters) and isPublished.
- `view.kind:detail`: required positive seriesId copied from that app's list.

## Results and identifiers

CONTENT_SERIES list returns serieses, pagination, nextPage, selectionRevision and completeInventory:false. Use selectionRevision for [content_series_apply](content_series_apply.md) creation. It binds the selected context, not a complete series inventory.

Detail returns series, episodes and revision for changes. Episode identity is the series connection's ID; postId identifies the original content. The bridge validates the complete linked order using prevId/nextId, rejects cycles, duplicates, foreign consumers and disconnected chains, and requires totals to match. The defensive read bound is 200 episodes. **The source writer permits only 100 linked posts per series**; the read bound does not increase that limit.

Use [content_posts_get](content_posts_get.md) to discover source posts before linking. Reading changes nothing and creates no task. The exact returned console destination opens the series list/detail.

## Input example

This is an input illustration, not a recorded call. Replace the channel, app, observed IDs and all-zero revision with values from the matching authorized read. A dry run does not save changes.

```json
{
  "channelCode": "selected-channel",
  "pAppCode": "B00001",
  "view": {
    "kind": "detail",
    "seriesId": 1
  }
}
```