> ## Documentation Index > Fetch the complete documentation index at: https://developers.semji.com/llms.txt > Use this file to discover all available pages before exploring further. # List content ideas of a search > Returns a paginated list of the content ideas produced by a completed search. Each idea carries its keyword, URL, search volume, keyword difficulty, estimated traffic, relevance and the workspace's own ranking on the keyword. Supports filtering (keyword, title, url, type, keywordBrand, and gte/lte ranges on searchVolume, keywordDifficulty, urlEstimatedTraffic, similarityScore) and sorting. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/content-idea-searches/{contentIdeaSearchId}/content-ideas openapi: 3.0.3 info: description: > The Semji API lets you integrate Semji's AI-powered Content Marketing platform into your own tools and workflows. Scale your organic and AI visibility programmatically. ## Authentication All endpoints require a Bearer API key. Generate one from **Settings > API Keys** in the Semji app. Each key is scoped to a single user and organization. ``` Authorization: Bearer sk_your_api_key_here ``` ## Rate Limiting Requests are rate-limited per API key: **1,000 requests per hour**. Rate limit headers are included in every response: - `X-RateLimit-Limit` — Maximum requests per window - `X-RateLimit-Remaining` — Requests remaining - `X-RateLimit-Reset` — Seconds until the window resets ## Response Format All responses return JSON. Collections use a standard envelope: ```json { "data": [...], "pagination": { "total": 42, "page": 1, "limit": 25, "hasMore": true } } ``` Errors follow a consistent format: ```json { "error": { "code": "not_found", "message": "The requested resource was not found." } } ``` ## Core Concepts - **Workspace** — A single website you track. Contains pages, contents, keywords, and all related analysis data. - **Page** — A URL on your website that Semji monitors. Pages are the anchor for keywords and content drafts. - **Content** — An SEO-optimized article linked to a page. Drafts evolve through workflow statuses toward publication. - **Content Score** — A 0–100 score measuring how well your content follows Semji's SEO recommendations. Aim for 75+ before publishing. - **Keyword** — A search term tracked for a page. Analyzing a keyword produces SERP-based recommendations (topics, questions, search intents, links). - **Prompt** — A question users ask AI engines (ChatGPT, Google AI Overviews). Analyzing a prompt reveals how to optimize your content for AI citations. - **Atomic Content** — AI-powered content generation that produces a complete SEO-optimized article in one step. title: Semji API version: 1.0.0 servers: [] security: - apiKey: [] tags: - description: >- Retrieve the authenticated user and their organization, including remaining credit balances. name: Me - description: >- List members of the organization linked to the API key, with their roles (Admin or Member). name: Users - description: >- A workspace represents a single website you track in Semji. Each workspace has its own pages, contents, keywords, folders, and workflow statuses. Use these endpoints to list workspaces, view members, and access workspace-level configuration. name: Workspaces - description: >- Organize your content into a hierarchical folder structure within a workspace. Folders are returned as a flat list — reconstruct the tree client-side using `parentFolderId`. name: Folders - description: >- Pages are URLs on your website that Semji tracks for SEO performance. Import a URL to start monitoring it, trigger a crawl to fetch its metadata, and associate keywords for analysis. Each page can have content drafts attached. name: Pages - description: >- Contents are SEO-optimized articles managed through Semji. Create drafts, update them with the built-in editor or via the API, track their Content Score (0–100), and publish them to your CMS. Use Atomic Content to generate a complete optimized article with AI. The `version` field enables optimistic locking for concurrent editing. name: Contents - description: >- Track the progress of Atomic Content AI generations. After launching a generation via `POST /v1/contents/:contentId/atomic`, poll the status here. When status reaches `review`, confirm to apply the generated content to your draft, or cancel to discard it. name: Content Generations - description: >- View the credit consumption history for your organization. Credits are consumed by keyword analyses, AI content generation, and content idea searches. Each entry details what was consumed, by whom, and in which workspace. name: Credit Usages - description: >- Keywords are search terms associated with your pages. Analyzing a keyword triggers a SERP analysis that produces actionable SEO recommendations: topics to cover, questions to answer, search intents to address, and links to add. Use the report endpoint to score any content against these recommendations. name: Keywords - description: >- Prompts represent questions that users ask AI engines (ChatGPT, Google AI Overviews). Analyzing a prompt reveals which sources and brands are cited in AI responses, and produces GEO recommendations to improve your content's visibility in AI-generated answers. name: Prompts - description: >- Brand Voices encode your editorial identity for AI-generated content. When configured, Atomic Content and AI features automatically adopt your writing style, tone, and brand guidelines. Select a brand voice ID in the `settings` of `POST /v1/contents/:contentId/atomic`. name: Brand Voices - description: >- Knowledge Documents are reference materials (text, URLs, or files) that enrich AI content generation with your expertise. When knowledge sources are enabled in Atomic Content settings, the AI draws from these documents to produce more accurate, brand-aligned content. name: Knowledge Documents paths: /v1/content-idea-searches/{contentIdeaSearchId}/content-ideas: get: tags: - Content Ideas summary: List content ideas of a search description: >- Returns a paginated list of the content ideas produced by a completed search. Each idea carries its keyword, URL, search volume, keyword difficulty, estimated traffic, relevance and the workspace's own ranking on the keyword. Supports filtering (keyword, title, url, type, keywordBrand, and gte/lte ranges on searchVolume, keywordDifficulty, urlEstimatedTraffic, similarityScore) and sorting. parameters: - schema: default: 25 type: integer minimum: 1 maximum: 100 in: query name: limit required: false - schema: default: 1 type: integer minimum: 1 in: query name: page required: false - schema: type: string in: query name: keyword required: false description: Filter by exact keyword. - schema: type: string in: query name: keyword[contains] required: false description: Filter by keyword substring. - schema: type: string in: query name: keywordBrand required: false description: Filter by keyword brandedness (exact). - schema: type: integer minimum: 0 maximum: 100 in: query name: keywordDifficulty[gte] required: false description: Keyword difficulty >= (0-100). - schema: type: integer minimum: 0 maximum: 100 in: query name: keywordDifficulty[lte] required: false description: Keyword difficulty <= (0-100). - schema: type: integer minimum: 0 in: query name: searchVolume[gte] required: false description: Monthly search volume >=. - schema: type: integer minimum: 0 in: query name: searchVolume[lte] required: false description: Monthly search volume <=. - schema: type: number in: query name: similarityScore[gte] required: false description: Similarity score >=. - schema: type: number in: query name: similarityScore[lte] required: false description: Similarity score <=. - schema: type: string enum: - searchVolume - '-searchVolume' - title - '-title' - type - '-type' - urlEstimatedTraffic - '-urlEstimatedTraffic' in: query name: sort required: false description: >- Sort field, prefix with - for descending. Default: by relevance (similarity score, descending). - schema: type: string in: query name: title required: false description: Filter by exact URL title. - schema: type: string in: query name: title[contains] required: false description: Filter by URL title substring. - schema: type: string enum: - related - broadmatch in: query name: type required: false description: Filter by idea type. - schema: type: string in: query name: url required: false description: Filter by exact URL. - schema: type: string in: query name: url[contains] required: false description: Filter by URL substring. - schema: type: integer minimum: 0 in: query name: urlEstimatedTraffic[gte] required: false description: URL estimated monthly traffic >=. - schema: type: integer minimum: 0 in: query name: urlEstimatedTraffic[lte] required: false description: URL estimated monthly traffic <=. - schema: type: string in: path name: contentIdeaSearchId required: true description: Content idea search ID. responses: '200': description: Default Response content: application/json: schema: type: object properties: data: type: array items: type: object properties: clusterIds: type: array items: type: string description: >- IDs of the topic clusters this idea belongs to (may be empty). id: type: string description: Unique identifier of the content idea. isQuestion: type: boolean description: Whether the keyword is phrased as a question. keyword: nullable: true description: Suggested keyword. type: string keywordBrand: nullable: true description: Branded nature of the keyword. type: string keywordDifficulty: nullable: true description: Keyword difficulty (0-100). type: number relevance: nullable: true description: Relevance of the idea (0-100). type: number searchVolume: nullable: true description: Monthly search volume of the keyword. type: number similarityScore: nullable: true description: Similarity score to the seed keyword. type: number title: nullable: true description: Title of the suggested URL. type: string type: nullable: true description: 'Idea type: ''related'' or ''broadmatch''.' type: string url: nullable: true description: Suggested URL. type: string urlCategory: nullable: true description: Category of the URL. type: string urlEstimatedTraffic: nullable: true description: Estimated monthly traffic of the URL. type: number urlWordsCount: nullable: true description: Word count of the ranked URL. type: number workspaceUrlPosition: nullable: true description: >- Position of the workspace's own URL ranking on this keyword. type: number workspaceUrlRanked: nullable: true description: >- The workspace's own URL ranking on this keyword, if any. type: string required: - clusterIds - id - isQuestion - keyword - keywordBrand - keywordDifficulty - relevance - searchVolume - similarityScore - title - type - url - urlCategory - urlEstimatedTraffic - urlWordsCount - workspaceUrlPosition - workspaceUrlRanked additionalProperties: false pagination: type: object properties: hasMore: type: boolean limit: type: integer page: type: integer total: type: integer required: - hasMore - limit - page - total additionalProperties: false required: - data - pagination additionalProperties: false components: securitySchemes: apiKey: bearerFormat: API Key description: API key starting with `sk_`. Generate one in **Settings > API Keys**. scheme: bearer type: http ````