---
title: "Retrieve content by ID, inode, query, or related content"
method: GET
path: "/api/content/{params}"
tags: ["Content Delivery"]
---

# Retrieve content by ID, inode, query, or related content

`GET /api/content/{params}`

Retrieves contentlets using various lookup strategies. Parameters use a slash-delimited key:value format in the URL path (e.g., /api/content/inode:abc123/live:true/language:1). Supported parameters include: id (identifier), inode, query (Lucene query), type (json or xml), orderby, limit, offset, language, live, depth (0-3 for relationship traversal), render (true to render widgets), related (ContentType.Field:identifier format), and allCategoriesInfo. When 'depth' is set: 0 returns related content identifiers, 1 returns full related content objects, 2 returns related content with their related identifiers, 3 returns related content with their fully hydrated related content.

## Path parameters

- `params` string, required

## Response `200`

Content retrieved successfully

- object — Content data in the requested format

## Other responses

- `400` — Invalid parameters or malformed query
- `401` — Unauthorized access
- `403` — Forbidden - insufficient permissions
- `404` — Content not found
- `500` — Internal server error

---

[API](https://skmtc.dev/jostens/apis/dotcms-rest-api.md) · [All operations](https://skmtc.dev/jostens/apis/dotcms-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/jostens/dotcms-rest-api/revisions/a088fe9f515c/schema)