> ## Documentation Index
> Fetch the complete documentation index at: https://www.conductor.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Content API Quick Start Guide

> How to string the Content API endpoints together end to end — what to call, and in what order, to research, create, analyze, and optimize a draft.

Conductor designed the Content API endpoints to be used together as a single content workflow. This guide walks through the typical order of operations for a simple content creation workflow, from researching a topic to iterating on an optimized draft.

<Tip>
  This is just one potential approach that uses only some of our potential tools. Review and the Content API endpoint reference articles and the API playground to see everything you can accomplish with the Content API.
</Tip>

## The content creation workflow at a glance

<Steps>
  <Step title="Research target keywords and competitor URLs">
    Call [Get SERP URLs](/api/content-api/endpoints/get-serp-urls) to research your topic and validate your target keywords and competitor URLs for which your draft will be optimized for. This is a pre-requisite for creating a draft: the results feed the `phrases` and `competitorUrls` fields in the next step.
  </Step>

  <Step title="Create a draft">
    Call [Create a draft](/api/content-api/endpoints/create-draft) with the keyword phrases and competitor URLs you selected. This returns a `draftId` used by every subsequent step.

    <Warning>
      Each time you create a draft using this endpoint, it consumes a draft from your Conductor Creator allotment. If you are running low on drafts, reach out to your Conductor team.
    </Warning>
  </Step>

  <Step title="Request content insights">
    Call [Request content insights](/api/content-api/endpoints/request-insights) to start generating insights for the draft. This kicks off an [**asynchronous**](/api/async-queries) process, so the request returns  immediately without the results.
  </Step>

  <Step title="Get content insights">
    Poll [Get content insights](/api/content-api/endpoints/get-insights) to check the status and retrieve the results of the insights generation request once it completes.
  </Step>

  <Step title="Generate a Content Score">
    Call [Generate content score](/api/content-api/endpoints/generate-content-score) to produce a score and detailed evaluation of the draft's content across intent alignment and topical coverage. Use this score to determine how close to publication-ready your draft is.
  </Step>

  <Step title="Validate content guidance">
    Call [Validate content guidance](/api/content-api/endpoints/validate-content-guidance) to check your draft's content against the generated insights and see how well it satisfies the recommendations.
  </Step>

  <Step title="Generate your draft">
    Call [Generate your content](/api/content-api/endpoints/create-content-generation) to generate content—outlines, drafts, meta descriptions, title tags, and more—that is aligned with the insights and content score for the draft.

    <Info>
      You can also write and revise your `bodyCopy` field manually—or pipe it in from wherever you draft content—with the [Update draft](/api/content-api/endpoints/update-draft) endpoint.
    </Info>
  </Step>

  <Step title="Update your draft and iterate">
    Update your draft's `bodyCopy` via [Update a draft](/api/content-api/endpoints/update-draft).
  </Step>

  <Step title="Iterate">
    As needed, re-request insights (step 3 and 4), regenerate the content score (step 5), re-validate (step 6), and integrate your updates into your draft (steps 7 and 8). Repeat until the draft is publication-ready.
  </Step>
</Steps>