# Set Podcast Style

Pick a storytelling format such as `deep dive`, `brief`, `critique`, or `debate`. The style adjusts pacing and host banter.

```bash
curl -X POST "https://api.autocontentapi.com/content/Create" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "outputType": "audio",
    "resources": [
      { "type": "text", "content": "The latest product launch generated strong community feedback..." }
    ],
    "text": "Turn this update into an engaging episode intro.",
    "style": "brief"
  }'
```

**Key fields**

* `style`: Choose from the supported presets (`deep dive`, `brief`, `critique`, `debate`).
* `resources`: Any mix is allowed; this example uses raw text.
* `text`: Guide the output by describing your goals or audience.

## Try it in code

* [C#](/code-samples/podcasts/csharp/set-style.md)
* [Node.js](/code-samples/podcasts/nodejs/set-style.md)
* [Java](/code-samples/podcasts/java/set-style.md)
* [PHP](/code-samples/podcasts/php/set-style.md)
* [Python](/code-samples/podcasts/python/set-style.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.autocontentapi.com/quick-start/podcasts/set-style.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.